rook
For VPNs, at least, I can offer some suggestions. If you wanted to securely access a specific box or network of yours, tailscale is pretty great and very painless to use. If you wanted to do stuff without various folk noticing then that’s a bit trickier but I’ve been happy using mullvad… they’re not the cheapest, though they have some splendid anonymous payment mechanisms (you can literally mail them a wad of banknotes with a magic code on a bit of paper… you don’t even need to muck about with bitcoin).
In further bluesky news, the team have a bit of an elon moment and forget how public they made everything.
https://bsky.app/profile/miriambo.bsky.social/post/3ldq2c7lu6c25 (only readable if you are logged in to bluesky)
Bluesky’s approach to using domain names to mean identity is now showing cracks that everyone can see: https://tedium.co/2024/12/17/bluesky-impersonation-risks/
(it was always shaky, but mostly only shown by infosec folks who signed up as amazon s3, etc)
TL;DR: scammer buys .com domain for journalist’s name, registers it on bluesky, demands money to hand it over or face reputational damage, uses other fake accounts with plausible names and backgrounds to encourage the mark to pay up. Fun stuff. The best bit is when the sockpuppets got one of the real people they were pretending to be banned from bluesky.
Nvidia doing their part to help consumers associate AI with unwanted useless bloatware that’s foisted upon them.
I will find someone who I consider better than me in relevant ways,
Lemme guess, rich, white, asshole? (now I write this, I realise it could be about the author of the blog post too, and not just the bull he’s seeking).
These people continue to be so utterly delusional about the nature of success. The desperate need to believe that genetics is destiny, and that the ultra-wealthy got that way because they are also ultra-competent instead of merely being ultra-lucky and/or ultra-rapacious.
I guess the future is a race to see what comes first… the ultra-wealthy habsburging themselves into oblivion, the oceans boiling, or a resurgence in the construction of hand-built artisanal tumbrels.
I’m aware he isn’t there now, but it bears remembering that he was there at the beginning when these goals were being shaped, and as we have seen with twitter there’s nothing to stop him coming back, even if nostr is his new best friend for now.
I read that posts on BlueSky are permanently stored in a blockchain,
So, this is complex and hard to find concrete information on, but:
- Bluesky use a merkle tree based things. Don’t call em blockchain… that’s the sort of thing cryptocurrency boosters want so as to present their technologies are useful.
- Posts are stored in a merkle search tree, but attachments are stored separately. Attached blobs (like images) can be (and are) deleted independently of the tree nodes which reference them.
- The merkle trees are independent and can be modified without having to rewrite the whole history of every post on bluesky, because there isn’t one central official ledger of all posts.
From bluesky’s own (non technical) blurb on the subject,
it takes a bit longer for the text content of a post to be fully deleted in storage. The text content is stored in a non-readable form, but it is possible to query the data via the API. We will periodically perform back-end deletes to entirely wipe this data.
The merkle trees are per-user, which makes history-modifying operations like rebasing practical… this facility apparently landed last summer, eg. Intention to remove repository history. Flagging tree nodes as deleted, and then actually destroying them in a series of later operations (rebase, then garbage collection) would explain the front end respecting deletions but lower-level protocols showing older state for a little while.
Interesting post and corresponding mastodon thread on the non-decentralised-ness of bluesky by cwebber.
https://dustycloud.org/blog/how-decentralized-is-bluesky/
https://social.coop/@cwebber/113527462572885698
The author is keen about this particular “vision statement”:
Preparing for the organization as a future adversary.
The assumption being, stuff gets enshittified and how might you guard your product against the future stupid and awful whims of management and investors?
Of course, they don’t consider that it cuts both ways, and Jack Dorsey’s personal grumbles about Twitter. The risk from his point of view was the company he founded doing evil unthinkable things like, uh, banning nazis. He’s keen for that sort of thing to never happen again on his platforms.
It’s a long read, but a good one (though not a nice one).
- learn about how all the people who actually make decisions in c++ world are complete assholes!
- liking go (the programming language) correlated with brain damage!
- in c++ world, it is ok to throw an arbitrary number of highly competent non-bros out of the window in order to keep a bro on board, even if said bro drugged and raped a minor!
- the c++ module system is like a gunshot wound to the ass!
- c++ leadership is delusional about memory safety!
- even more assholes!
Someone on mastodon (can’t remember who right now) joked that they were expecting the c++ committee to publicly support trump, in the hopes he would retract the usg memory safety requirements. I can now believe that they might have considered that, and are probably hoping he’ll come down in their favour now that he’s coming in.