Sure, but end users as a group still have a significant amount of RAM.
Even on a low-specced machine you can afford to have the currently-active website tab consume a few hundreds of megabytes of RAM. It was mostly sitting idle anyways, so most people aren't even going to notice. Multiply that by a few thousand concurrent visitors and you're burning hundreds of gigabytes without anyone caring.
Some scraper being forced to install hundreds of gigabytes of extra RAM in their crawling node? They will notice having to go from a $0.50 / h instance to a $15.00 / h one, solely for the extra RAM requirement.
GrapheneOS allows you to deny network access per app pretty trivially. Google Play services make it a bit more difficult because the app might marshall the network request through that; I'm not sure how to verify that behavior when it happens.
Thanks for mentioning GrapheneOS. I'll just explain to others what "pretty trivially" means here. GrapheneOS adds a huge checkmark "Network access?" when you install an app. It's impossible to miss.
The problem is the yes/no options - I want to give access to specific endpoints - but now that’s “all of Cloudflare for everything” which means the web entire.
It used to be you could let Onkyo App™ access the five IPs for onkyo.com and be done with it.
I think Google Play Services will only marshal data to and from Google. This will bypass the permission if you're using it as a firewall, but won't let the app run a residential proxy.
Bluetooth autoconnect configuration is a Wayland issue? I honestly would have never guessed. I always figured it was the responsibility of the DE or bluez service.
I think the endgame is you go to Google or your favorite subscription based LLM for knowledge instead of visiting websites. Ads can continue living within LLM search results and it can even become a marketplace where you order within the LLM environment.
Let's say you have a dream where you hit yourself in the head with a hammer and pass out. Surely that won't lead you to believe that your consciousness arises from your dream brain.
I made the decision to leave Github a couple months ago when I retired and started heavily working on personal projects. I like the idea of radicle and used it for a while, but it's complicated to set up and maintain if you want to run your own seed node and pin your personal projects.
What I ended up with is a version of a static forge - Charm's soft-serve to host the repos and a forked version of the pico.sh pgit static site generator. I added git-bug integration to track issues in the repo and an alternative CLI to git-bug that works better when collaborating with agents.
A static forge site is very resilient to bot traffic because it only renders a limited number of commits, instead of pathologically allowing a near infinite number of URLs for bots to crawl.
Exactly this. Even though I don't use git-bug anymore, I'm still a sponsor. I desperately want an issue-tracker-in-.git to become a standard.
Issues and CI are the only lock-in. The latter is legitimate because you're using someone else's CPU, but every developer has the tooling to "git diff" and write comments if we could just agree on a format.
They can clone the repo, make changes, and then push. On the server, you can have a hook that checks if the commit only contains appropriate issue changes, and apply just those.
Sure, a little more complicated than “Create Issue”, but not that much for devs. We could even simplify the workflow with e.g. git-issue or something like that, similar to e.g. git-send-email.
git issue init “There is a problem”
git issue push
git issue get 6 # short for issue@{6}
Radicle is such a cool concept and seems to be working great. The only thing it needs is a better way to search through the projects hosted on each node.
I've been using my 2012 Paperwhite Kindle with Calibre and the experience is honestly great. The only thing I miss from the Amazon shut down is Wikipedia lookup and highlight/note syncing. Otherwise, I've steered clear of Amazon DRM for a long time so I didn't really care because I was already sideloading books with Calibre.
