

Lemmy will change the way it handles DMs in 1.0 specifically for Masto compatibility.
Lemmy will change the way it handles DMs in 1.0 specifically for Masto compatibility.
I linked to a feddit.uk view of a post in !linux@lemmy.ml because I was being lazy.
I assume the second Lemmy link is suppose to go the .ml thread and not p.dev, as that comment section seems fine?
It ignores what happens if your PDS provider goes down. While currently Bluesky can repopulate a new PDS with your old data, I don’t see how that’s going to survive them adding stuff to the AT proto that isn’t public and therefore not kept persistently in Bkuesky’s servers (e.g. E2EE DMs).
I don’t have a Sharkey account to test (I really need to move my masto off .social one of these days) but it works in Mastodon
Here’s an example (you’ll need to look on Lemmy to see the image):
Does anyone on your instance follow the communities you’re interested in? Lemmy communities ‘boosts’ all comments it receives, so you should have them.
The labeling idea is pretty interesting, an email service with inbuilt proxy, but your website is pretty light on details. Stuff like pricing or custom domain support is absent.
Do you have any recommendations for someone who just uses them for email?
I didn’t explain what I meant very well. To scrape a website you don’t need to understand robots.txt, implementing robots.txt is something you do to be a good netizen. But to get like info from Lemmy, implementing ActivityPub is a requirement.
Now I’ll admit, it’s not a great system and I do wish we had something better, but I also don’t think “this isn’t a good way to communicate preferences” is a good reason to ignore them.
I didn’t say it was private, I said it wasn’t public, there’s a difference. If you asked me what number I was thinking of I’d tell you, but that’s not the same thing as the number I’m thinking of being public information. ActivityPub is, at its core, about consent. We have consented to having our data be sent to any person able to serve 200 responses on an inbox endpoint by using instances with open federation. We could, if that makes us uncomfortable, moved to a closed federation system where we only accept request from an allowlisted set of instances, with software that follows the spec’s public addressing system.
The comparison doesn’t work because both Lemmy and Mbin are implementing the same standard, while robots.txt is mostly an honour system.
You should assume voter data is fully public and fully open. It otherwise is in the federated ecosystem.
Information not being private isn’t the same thing as information being public.
Lemmy likes aren’t meant to be public, this is just other software failing to respect the privacy Lemmy indicates.
Damn, so this is how I find out we’re least trustworthy part of the commonwealth.
Has to be, no way SDF has 5 million comments.
Why did you link to a Mastodon post and not the actual article?
Tumblr is now on ActivityPub
Is it? I know it’s been moved to Wordpress, but I haven’t heard about this.
Ghost can apparently be used to manage multiple blogs under different subdomains. Might be worth looking into when their ActivityPub supports goes out of early access.
Non-Roman Romania
Congratulations infertile people, you are now officially sexless.