386 karma · joined January 4, 2012
What I now have: ~B
What I really need: a way to stop long-running SSH connections from freezing
That aside, I've been wanting to play with this kind of music making via code, this is a useful write-up.
Beyond my ISP I'm virtually anonymous unless I log in. If it's blocked at the network level I cannot login. If it's not blocked by the network, then it doesn't know exactly which individual is using my network connection. Theoretically they could put an interstitial page to check credentials but we'd just end up sharing the login rather than sharing all our personal details in separate accounts, or more likely I'd just not bother and accept the 'child' experience.
If I lose access to social media so be it. All that will do is change the landscape as the diaspora find a new uncensored social media.
This all falls apart when it affects genuine work, then it's already too late. The only real option at this point is VPN.
Is this just a way to strong-arm non-cloudflarians into adopting their platform if you don't want your site crawled? It does sound like they are selling the solution to avoid their own content crawler.
That compulsion doesn't seem present in freeform building, and there's been zero interest in it in our household. I know that's not true for all, but it seems like a lost art. Maybe it's because the IP sets show how but not the why it's constructed in a certain way, so given a bag of Lego most wouldn't know the process of creating something they can see in their minds eye within the constraints of the available bricks.
That said, Nginx is also wrong and shouldn't do that.
The problems start when the space become not-for-children and identity validation is mandatory to use them, which will exclude people like me who categorically refuse to hand over personal secrets in order to have access. It does not warrant the inherent risk involved with granting access to personal details unrelated to the service offered. I reckon this will happen when someone decides it's better commercially to make a service adult-only than to moderate non-adult accounts. It's a slippery slope, and a predictable next step once adult have become accustomed to handing over papers for some services to have to do it for many, if not all.
However... the lack of Docker on BSD is a deal breaker for some of my uses, jumping through hoops is possible, and moving to Podman might work but looks complicated to set up.
On the other hand, Debian 14 will remove GTK2 which breaks other things.
There's always a compromise.
Forgive me for I am being sceptical. The might be some insight here I have not considered, but I'd feel a lot more comfortable if it was all self-hosted / self-collected data.
The second option is ignoring the verification request. Goodbye online-gaming-with-strangers on Xbox. (I see this as a positive). Same goes for Ubisoft who aggressively wanted my secret papers to verify my identity.
I've yet to come across anything I want or need outside banking or government use where age verification benefits me, or is so useful/important that I would willingly hand over critical secret documents. I've not even needed to use a VPN for anything. It doesn't mean it won't happen, but when it does, option #1 or #2 is going to cover everything.
Which circles back to the main point here - if I ignore it, then effectively I get identified as a non-adult. How does this protect anybody?
(UK-based, might not be the same everywhere)
It'll fail miserably at making it human-friendly though, and attempt to pilfer existing popular designs. If it builds a GUI, it's be a horrible mashup of Windows 7/8/10/11, various versions of OSX / MacOS, iOS, and Android. It won't 'get' the difference between desktop, laptop, mobile, or tablet. It might apply HIG rules, but that would end up with a clone at best.
In short, it would most likely make something technically passable but nightmareish to use.