I might give them a try. I already tried to do @planish@aiparadise.moe with planish@sh.itjust.works as an “email”, and that did not work even a little bit. So now I guess I need a new name over there unless you want to use your admin powers to clean up my bad life choices.

The threat model here is someone getting access to all the services databases through now-routine “data breaches”, and then being able to link what I do online and who I actually am, despite not having any sort of legitimate law-enforcement-type power.

Well Mx. Smith, I see you’re highly qualified for our busdriver position. However, it looks like, according to embarrassing-databse-dumps.info, on January 8th, 2033 one Jeremick Smith posted “i luv big butt” on !butt-enthusiasts@big.butt. Care to explain this?

I looked at them, and I think they would work, but also having multiple email addresses is touted as a feature of their premium plans, and I may or may not already use them. So if I want to be a fresh person I have to sort of cheat them, and they might not like it.

That’s a good point. My turbo-nerd values beep angrily when I find something I want can only be gotten by asking a real human nicely, and being likable enough to be accepted, and not, say, via a well-documented freely available API call. But sometimes that’s life.

I was looking into opening an account at aiparadise.moe, but https://aiparadise.moe/signup lists email as a required field. And if @admin@aiparadise.moe is hand-reviewing applications, an obvious circumvention of the required field might not be appreciated or approved.

*moot

This could be done technically, at least as long as the real hoster (redgifs here) isn’t trying to stop automated uploads and isn’t going to ban the intermediate server.

But you’d probably have to hack around in the Lemmy code a bit because I don’t think it knows how to do this already.

The German instance might need to check the flag on the content against the flag on the user before rendering the page for the federated content.

Can we do this in a way that handles:

• Accounts that were registered 18 years ago
• Control of accounts elsewhere that were registered 18 years ago
• Anybody who can sign something with an 18 year old key
• Anybody who some ordinary humans can vouch for
• Anybody who has a magic cookie from some kind of distributed system that does this
• Anybody whose browser thinks they are 18

Determining that people are a certain age shouldn’t be the magic power of enormous companies or government ID issuers.

You would probably always upload it to your own instance, but communities such as !nsfw@reddthat.com seem to be where people are putting it?

It looks like nothing in the sh.itjust.works rules would prohibit this, and for image synthesis specifically there is already a !nsfwai@aiparadise.moe

But I don’t think it’s just about which server wants to have the community. When I post stuff and upload images for the posts, they get URLs on my home server, which is who actually seems to hold the bits, even if I post the post in a community homed elsewhere.