Yeah one of my more… tech adventurous friends had the most insane series of security breaches (to out it mildly) potentially related to this and some other recent ridiculousness.

I think one of the more important things you can get across to him is this:

Porn is fine, but it’s fiction. It’s no more real or realistic than the latest superhero blockbuster, and should be thought of that way. It’s entertainment, not education.

There are sex ed channels on Youtube. Good ones. Sexplanations is one, but there are also others. Seek those out.

I know this is going to be a very awkward conversation, but you have to understand this: he will be finding and watching porn, and most likely already is at 14. Don’t shame him for that. In any way. Let him know that you know, and that it’s normal, but that it’s important to think of it like it’s just the movies. Cos that’s what it is.

I feel like probably the biggest UX improvement Lemmy, and the fediverse more widely, could do is to make user migration more seamless. I’m thinking federated SSO, basically, where once you have an account anywhere on the fediverse you should a) be able to use that account anywhere else in the fediverse and b) move where that account is hoeted to anywhere else in the fediverse.

I believe this is related to whatever the hell ActivityPod is doing? Feel free to correct me on that. Regardless, get something like this in place as well as better instance and services discovery (and maybe the ability to find your other connected services from you ‘account’ pages on whatever service you’re on) and I think people might start to think of fediverse as less ‘an alternative’ and more ‘the better one’.

Basically, we need standard protocols for user data management, transfer, credentials management, and service and instance discovery. I’m sure some of that exists, the important thing will be to streamline and standardise the actual UX.

If he gets caught (hope he doesn’t), I hope he gets prosecuted, pleads self defense, and wins.

Because let’s be honest, this is 100% a case of community self defense.

I may be wrong about the actual reason for this - as ‘double V’ is also quite common - and it may just end up being some kind of ‘well when the printing press came to England’ thing, but:

In the classical Latin alphabet, the letter ‘V’ was not actually representative of what we today recognise as the /u/ sound (or its variants). It was in fact the written form of the /u/ sound (and related variants). So when the W was introduced to the English alphabet, I guess it was indeed a ‘double /u/‘.

So I’m guessing it’s a combination of dun/den/tun etc being a common suffix in a lot of historical languages, and ‘ei’ being an extremely common diphthong worldwide just… leading to a lot of similar-sounding names that also converge in spelling in modern English?

I’m sorry, but ‘crash when pressing Ctrl+C’ is a hilarious bug.

I live in the UK, but am from Norway. I know a few librarians though, and I know that community libraries are usually (or at least often) interested in projects that can connect their communities and help them with outreach. Something like this certainly could do that, and with libraries existing in most communities there is a built in network for broader proliferation there.

I’m also just very keen on the idea of libraries having a central role to play in the future of the broader fediverse ecosystem.

Edit: It may be key to pitch this to them not as a platform, but as a decentralised community network.

Loving this concept. May I make a suggestion? Show this to and discuss this with your local library. That strikes me as a good potential partner, and a model that can be replicated in most places to potentially help with everything from hosting to community resources access.

Thing to keep in mind on this is that it’s a national regulatory decision based on an EU regulatory decision, and it is expected to be just the first of several more like it to come from it. Meaning, it is likely to spread and it is likely to escalate over time. And even if it’s just an added cost of doing business, it does impact the financial viability of Facebook surveillance-capitalistic model.

The technical challenges are vast, is the long and short of it. But it’s high time there’s a good discussion over how it should (or might) work, at least the kinds of properties such a system should have.

• Self hosting of federated credentials should be possible, but not required
• ‘Backwards tracking’ of federated credentials should only be possible with limited requests (e.g. ‘verify author of post’) and approval of the credential owner
• All data on the credentials instance should be properly encrypted
• All data on credentials instance should be fully and easily portable to other instances via common protocols

There are several issues involved here, beyond just ‘mere’ technology, that need addressing. Personally I think a good start might be to engage with public libraries here. They already keep simple identity records (library cards) and have public service purpose well-aligned with the concepts of the federation and public distribution of information and knowledge.