CuriousRose
Joined 2 years ago
Joined 2 years ago
It's a thicker port, single orientation and slower. Why you would still want this legacy port is beyond me and it should be a industry wide mandate by now. Very surprised to see it on the Mac Studio this year, just get an adapter/dongle.
I don't use local hosted models anymore due to hardware contstraints, but I do have some degree of search anonymisation attached to my OpenCode and OpenRouter connected open models.
On my Macbook I run OrbStack that has the following docker containers set to route through a Mullvad based gluetun.
- Firecrawl - fast web scraping
- SearxNG - metasearch
- CloakBrowser - tursile bypassing Playwright alternative
If you wanted to get fancy with the proxy rotation, you could setup numerous instances of Playwright each with their own Mullvad wireguard key in different locations.
Reusable rockets likely got the same ridicule, as did fast satellite internet, self driving and fully electric vehicles.
I can understand that Musk does not have the most palatable personality, but floating ideas and at least attempting innovation regardless of outcome over a long time is a net positive for society and should not be discouraged.
I've since taken to running a non-public Monero node, which will become public when I can ensure my network security as it's being run from my home.
In saying that, there is a lot of concern around the new Carrot changes. To preface, I don't understand it enough to have an opinion either way, but a good chunk of the vocal user base seems to be worried that making “optional” view keys show both incoming and outgoing transactions will force the hand of the remaining exchanges, and be a condition of adoption of new exchanges to support Monero.
I haven't really seen a dumbed down explanation from the core Monero team as to exactly what the change looks like, and what the theoretical implications could be. It would be nice if Monero had more accessible PR for non-technical users to encourage adoption and squash FUD when it arises or at least acknowledge it from a top level in a blog post or something so that the already hyper-paranoid user base doesn't unnecessarily drive a mass anti-Monero campaign.
If it gets particularly bad, I'm sure some impartial team will make another browser engine with Opus 5.5 but for now I can tolerate the minor inconveniences in Safari.