It says it has 95% Lemmy compatible API here. I can try to add it with some minor modifications.
Any group federation compatible server should be able to use Lemmy Federate for federating their communities (not the other way around). The only problem is, there is no standard ActivityPub way to determine if a user is an admin and I haven’t worked this out yet.
I don’t think banning users by the keyword “88” or defederating from an instance because it has “peepo” logo and accusing them of being (possible) nazis is not that effective. Or at least prone to false-positives.
Though downvote statistics stuff looks good.
Yeah I don’t get this argument either. The user reports content and I can see it, no matter which instance they're using. Does Piefed have a fully automatic autobot that fights spammers and we don't know about it? :)
It's pretty easy to implement. In fact, I was working on it. But I got discouraged because of some absurd political decisions. Still open to PRs though.
If it does the same thing (unlikely), I would turn it off. If it's just discovering and not fetching new posts, I would keep it running.
I wish Lemmy had this feature natively. Because to be honest, Lemmy Federate is a bit of a mud solution.
I would prefer a structure where community data is pulled through relays before a user follows a community and then continues as it is currently after someone follows. That could've make things easier in terms of database size, network and load, but I'm not sure if this can be done with the current ActivityPub spec.
That’s why I said “IIRC” because I don’t remember either 🙂
IIRC WebTorrent support is removed. Is torrenting completely off the table?
Now that they're out, lemmy.zero?
Absolutely. Sometimes I can be hard to understand (since English is not my native language), thanks for the clarity :)
Interesting. I didn't realize my instance wasn't federated with Piefed. I'll contact the Piefed admins about this.
However, this issue is probably not related to Lemmy Federate because Piefed.social doesn't even use it.
I prefer simplicity and using the first example but I'd be happy to hear other options. Here's a few examples:
HTTP/1.1 403 POST /endpoint
{ "message": "Unauthorized access" }
HTTP/1.1 403 POST /endpoint
Unauthorized access (no json)
HTTP/1.1 403 POST /endpoint
{ "error": "Unauthorized access" }
HTTP/1.1 403 POST /endpoint
{
"code": "UNAUTHORIZED",
"message": "Unauthorized access",
}
HTTP/1.1 200 (🤡) POST /endpoint
{
"error": true,
"message": "Unauthorized access",
}
HTTP/1.1 403 POST /endpoint
{
"status": 403,
"code": "UNAUTHORIZED",
"message": "Unauthorized access",
}
Or your own example.
It doesn't seem like a great feature if it only moves the post history to the imported instance and not to any other instances.