190 karma · joined June 3, 2024
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.
- Usually hosted on shared VPSs where IP reputation is decimated (wonder how this will be affected by pure IPv6 hosts)
- Patching is often manual and forgotten about (n = 1)
- Backups are often an afterthought
This is really cool.
I'd be happy with a re-branded SearX/SearXNG, with a paid cloud hosted instance from Mozilla that uses a shared base index plus your own crawled pages or optionally contribute your crawls back to the shared index.
IMAP + CalDev + CardDev sat on-top of cPanel is getting a bit long in the tooth for companies that want exchange-like mail solutions outside of the big two. Unfortunately MS and Google run the "spam" filters as well, so you really need an established company that they can't afford to irritate to enter the space - see Mozilla - to reliably force acceptance of enterprise mail outside the Duopoly they have.
Zoho is trying their best also in this space - not sure how successful they have been on the trusted email provider and integration front.
- Mozilla SSL Certs - for corporations that don't want Let's Encrypt
- Mozilla Mail - a reliable Exchange/Google Mail alternative (desperately needed imo)
- Thunderbird for iOS - why is this not a thing yet?
- Mozilla Search - metasearch that isn't based on Bing/DDG/Google
- Mozilla HTTPS DNS - although Cloudflare will probably always do this better
All seemingly low-hanging fruit with brand alignment.
Surely video calls have a native capture method in Windows/macOS now where you can overlay the controls for fairly cheap resources, and file sharing only needs to consume RAM during the upload process.
What gives with these apps? Like seriously, is it the fact that they need to load a whole browser environment just to run 100mb of JS? If so, why bother shipping an app at all? Just encourage users to allow notifications in the browser for the site and be done with it. No apps to maintain, instant patching on refresh, where's the obvious downside I'm missing?
Honestly the whole process was incredibly smooth, loving the web management, native ZFS. Wouldn't consider anything else as a type 1 hypervisor at this stage - and really unless I needed live VM migrations I can't see a future where I'd need anything else.
Managed to get rid of a few docker cloud VPS servers and my TrueNAS box at the same time.
I'd prefer if it was BSD based, but I'm just getting picky now.
It’s clear to me it’s the best of the worst if you need to use Windows.
I daily macOS Sequoia - you don’t want my unfiltered thoughts on Tahoe.
They basically did all the work, and refuse to sell it.
The OS has a purpose to be efficient and pleasant - anything that interferes with either is not a matter of taste, but a matter of poor execution.
Sure we have preferences, but truly beautiful things are hard to consider they are only so due to a matter of preference, and not objectivity.
Throwing GNOME/KDE/xkfc/mate/whatever flavour it is this month really starts to make things complicated for UX. I'm sure yes you could centralise it, mass deploy, have a stable config, etc, but these are low level things that when go wrong really interfere with the day-to-day of non-technical employees.
What do you do about drivers, obscure one-use PDF converters they want, Excel macros? The tools they are familiar with are lucky to have a macOS alternative these days, let alone a Linux build that is compatible with the distro they are on. Supporting most users is questions like - "where was the button that was there yesterday?", "why are my emails sorted backwards?", "whats this virus I have? (clicked allow notifications in Edge)".
Linux/BSD has incredible merit and I would love to see the duopoly in the desktop market broken up, but it requires a directed approach to fixing UX, a single opinionated distro that has enough traction to warrant developers to create turn-key apps and builds for it, and users to feel familiar with the interface without it changing for a long time. I don't see this happening due to the inherent communal aspect of Linux where everyone wants to make their mark and has their own opinions on design not just at the OS level but at the application level also.