912 karma · joined June 23, 2021
I think it's more about abstraction. If someone is standing on the street corner taking down your plate number, you know they're likely up to no good. If there's a camera on the street corner, it may bother me, but the vast majority of people just go "eh".
Let's ignore the "massification" of democracy (by which I mean entrenched power gaining leverage over the "demos" by targeting propaganda at the low-agency portion of the population, but this may be controversial?). Population scale has changed but Dunbar's number hasn't, and if the 0.1% of the population that is deeply invested in a topic manages to organize, there's a high likelihood that they can get critical reach. However, population scale has changed and Dunbar's number hasn't, so the first step of actually organizing 0.1% of the total population becomes a lot more difficult with scale.
Arguably, my distrust of modern democracy doesn't help, but I have no idea how anyone could manage to find and fish out 20k specific individuals from a pool of 20M people. And that's what needs to be done, IMO, not signing petitions (and in Canada, there's already a little bit of debanking-based chilling effect re: out-of-band political organization).
Asserting that you will not play a game ever if you haven't played it in the 5 years following its release is ludicrous.
Strange sentiment, which is well past the massification and gamesjournalismification of video games. By then, cover shooters were just a bad memory and most serious hobbyists had for a long time embraced both indies (Braid, in 2009) and older titles (Braid, in 2015, when the article was published).
I have to assume that this is the work of some contractor (Intracom?). Every cookie could be removed (analytics, etc.; and does europa.eu really need to embed a dozen of American services instead of just using <video>?), and the necessary ones could be consented to at the point of creation without any general interruption ("[ ] Remember Me (stores a 30-day cookie)" during the login flow).
This wasn't great, but then I started catching myself writing "It's not Y" responses to colleagues on Teams. I'm pretty sure I've caught all of these and never actually sent them (I did go and review a few chat logs recently and found no such sent message), but my point is that despite my relatively light LLM usage, I am "LLM-conditioned." The abyss stares back. There could be a lot of deeply "LLM-brained" people out there.
As for the zone file based workflow requiring zone deletion/recreation, perhaps a report/discussion would have led to something, but I was in the middle of testing managed DNS providers to get rid of my BIND servers and I didn't have any investment in deSEC, so it didn't occur to me to take the time. My initial post on here was less lamentation and more conveying personal experience to (possibly) save someone else some time.
In any case, none of these things were showstoppers for me (I went to another (paid) provider because I need very short TTL on some records for testing purposes), but I'm glad you took the time to look into the parser; it almost certainly will benefit others.
I'm all for ending copyright, but does any of that really need to be linked with the Wayback Machine? Huge chunks of the Web have been displaced or snuffed by social media and gen AI, making Wayback a unique(ly valuable) source of information and history. It's not my call, but it seems strange to risk it as a motte for the bailey of copyright abolition activism. What happens when some stick-up-the-ass company—whose stuff is probably in hundreds of different collections—decides it really wants a payday?
Logging back into deSEC right now, it seems like the parser does work better than it used to, but TTL inheritance is still spotty. As an extreme example, the following input:
@ 7777 IN SOA x. x. 1 9999 9999 9999 9999
A 203.0.113.1
4444 AAAA 2001:db8::1
www A 203.0.113.1
... correctly gets parsed by BIND (with the addition of a dummy NS record) as: @ 7777 IN A 203.0.113.1
@ 4444 IN AAAA 2001:db8::1
www 4444 IN A 203.0.113.1
... but deSEC parses: @ 9999 IN A 203.0.113.1
@ 4444 IN AAAA 2001:db8::1
www 9999 IN A 203.0.113.1
... where 9999 is a $TTL value from a different zone file, from a different domain, that I'd imported in a completely different session. The value is permanently (?) stuck to the entire account. This is ultimately almost a squabble since there's simple workarounds, but it did affect me when I used deSEC, and it's the sort of problem that I constantly run into with other managed DNS services too.Hopefully this helps in some way.
As an aside (though this certainly applies to deSEC) it's strange to me how so many DNS services (free or paid) struggle to import simple Bind zone files, often either giving a vague error ("one or more records could not be imported"), mangling records, or even just silently omitting records. Parsing a zone file has some gotchas, but it doesn't seem like it should be that hard.