heybrendan
Joined 10 years ago
Joined 10 years ago
This seems to be posted once per year (at least); however, hardly a complaint as the discussion tends to be high quality.
My personal mantra is if it's over 10~20 lines, I should arguably be using another language, like Python (and perhaps correspondingly, subprocess [2], if I'm in a hurry).
[1] https://web.archive.org/web/20140523002853/http://redsymbol....
This comment [1] by icing (curl staff) sums up the risk:
> "This report and your other one seem like an attack on our resources to handle security issues."
Maintainers of widely deployed, popular software, including those whom have openly made a commitment to engineering excellence [2] and responsiveness [like the curl project AFAICT], can not afford to /not/ treat each submission with some level of preliminary attention and seriousness.
Submitting low quality, bogus reports generated by a hallucinating LLM, and then doubling down by being deliberately opaque and obtuse during the investigation and discussion, is disgraceful.
[1] https://hackerone.com/reports/3125832#activity-34389935
[2] https://curl.se/docs/bugs.html (Heading: "Who fixes the problems")
- https://github.com/SimpleMobileTools/General-Discussion/issu...
How are 'concurrent.futures' users impacted? What will I need to change moving forward?
Notwithstanding the naysayers that surface with peculiar predictability any time Matrix is discussed here, know there are people like me that are happy Synapse users (and operators, nearly 5 years now!) that are in your corner, rooting for you [and Matrix]. Keep fighting the good fight.
> Hyprland is an independent, highly customizable, dynamic tiling Wayland compositor that doesn't sacrifice on its looks. It provides the latest Wayland features, is highly customizable, has all the eyecandy, the most powerful plugins, easy IPC, much more QoL stuff than other compositors and more...
The yt-dlp application functions better alongside ffmpeg, so I recommend installing that too. If on Linux, whatever is available via one's package manager /should/ do the trick.
Note, the project does make mention there are issues [1] with "standard ffmpeg", and is therefore minting custom builds [2][3] of ffmpeg, with additional patches applied.
[1] https://github.com/yt-dlp/yt-dlp#dependencies
[2] https://github.com/yt-dlp/FFmpeg-Builds#ffmpeg-static-auto-b...
A user or two have characterized Gill's activity as a pump-and-dump. From the article:
> A common form of this fraud is a pump-and-dump scheme, where fraudsters "make false and misleading statements to create a buying frenzy, and then sell shares at the pumped-up price."
Gill took a significant position in Gamestop beginning in June 2019 [1], and has been steadily increasing his position over the years (AFAICT without selling).
How is the belief in the long-term recovery and turn around of what was then, a dysfunctional (and unprofitable) American retailer, anything but rather prescient and patriotic?
Even if we were to concede that Gill is now in a position of influence, the suggestion that enforcement agencies should suddenly jump in and that litigation should /begin/ with him, rather than TV personalities and elected officials, strikes me as laughable.
Notwithstanding the ethical and security implications of a brokerage publicly broadcasting that a customer has an account on their platform (I would be livid if this happened to me), if E-Trade were to close Gill's account, would that not be a concrete admission that his position has them vulnerable, thereby strengthening and supporting the underlying thesis?
[1] https://en.wikipedia.org/wiki/Keith_Gill#Position_on_GameSto...
Given the example of risk HN user /deified/ shared regarding suspicions of brokers clandestinely distributing IOUs without investor knowledge where they should, in fact, be purchasing real shares, DRS offers the ability to move shares from one's broker to the company's transfer agent.
In effect, what DRS seemingly provides is a far more robust chain of trust and custody, as well as a more concrete level of assurance that shares in one's account are, in fact, real (and not IOUs).
In this case, the 10-K filing provides direct evidence that investors are consistently moving their Gamestop shares out of their respective brokers, to Gamestop's transfer agent, a company called Computershare (or purchasing shares directly via Computershare).
A conclusion one could possibly draw from this is that hundreds of thousands of Gamestop investors have collectively agreed that they can no longer trust their brokers, they are fed up with the true reality [and limitations] of "beneficial ownership", and are instead registering their Gamestop shares with the transfer agent (Computershare). All to the tune now of 25% of the total outstanding shares. As far as I'm aware, behavior of this magnitude has never before occurred.
Should that percentage continue to climb, it will be interesting to see what effect (if any) it will have on Gamestop's share price, assuming true supply and demand and real price discovery is still a fundamental part of how our markets function.
Ian released a video [3] this past December 2023, related to this topic.
[1] https://www.computershare.com/ca/en/insync/summer-2016/about...
[2] https://content-assets.computershare.com/eh96rkuu9740/630fe9...
> "As of March 20, 2024 [...] approximately 75.3 million shares of our Class A common stock were held by registered holders with our transfer agent (or approximately 25% of our outstanding shares)."
I've never seen anything like this. It seems absolutely unprecedented.
Recently Ian Carroll posted an overview [2] on X where he attempts to untangle the mess of the chaos surrounding Gamestop and its stock. I'm not going to pretend to understand the (dys?)function of our financial markets or everything that he shared, but my eyes are peeled.
Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).
A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods (or better detail risks), rather than throwing the baby out with the bathwater.
[1] https://brew.sh/
[2] https://github.com/pi-hole/pi-hole
[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...
I'm vaguely aware that there are crates available in the Rust ecosystem for interrogating and manipulating sockets much more directly as well as high level abstractions for all things netlink (read: AF_NETLINK). Is wielding Rust's socket/netlink libraries unsuitable in some way, or was it merely deemed out of the design scope?
Very cool project, please keep going!
[1] https://github.com/grigio/network-monitor/blob/master/src/se...