tfm

@[email protected] It should work now.

However, there's a known issue when fetching communities by name if a user account exists with the same username. Lemmy uses the ! symbol for both usernames and communities, which causes ambiguity.

To avoid this problem, you should use the full community URL instead of the !name@instance format when searching. This ensures the server correctly interprets your request as targeting a community rather than a user.

Examples:

• [email protected] → https://sh.itjust.works/c/raining
• [email protected] → https://retrolemmy.com/c/pixelart
• [email protected] → https://pawb.social/c/Eevee

Using the URL format avoids confusion and ensures consistent results.

Yeah it's great. Especially for mods. It has some quite advanced features.

An sich bin ich auf jeden Fall dafür, dass die Altersgrenze erhöht wird. Praktisch aber schwierig umzusetzen.

It isn't E2EE if the server holds the keys

I'd also consider writing a script with AI, which you don't understand, as vibe coding. Basically if you wouldn't be able to do it on your own it's vibe coding.

In the US maybe but not in Germany, Austria and probably most countries in Europe.

I'm not a lawyer but I suppose it would depend on the ToS and if the user agrees to the recording and processing. But if it allows the extraction of the real identity of the user it's probably a GDPR issue.

@[email protected] I've created a bug report on the Lemmy GitHub project. I'll get back to you as soon as the issue is resolved!

Interesting. I'll investigate and get back to you.

Then again, you should always assume every image and link in an email from a company or service is designed to track you.

That's the reason why you should disable them by default.

A net failure

Peertube!