Piefed users can set flairs for lemmy comms
Piefed users can set flairs for lemmy comms
11 comments
-
-
Yesterday I found that when a Mastodon user does a toot with @ a PieFed community the toot appears in PieFed but when it's federated onwards only other PieFed instances accept it - Lemmy does not.
So many possible combinations.
-
Maybe it was from a Mastodon server that requires 'authorized fetch' or whatever they call it? Last time I was tinkering with something related, Lemmy wasn't doing the required signed GET request for the user, so couldn't show the post.
-
Signed/authorised fetch is a site setting that's off by default in Lemmy. I thinks it's on by default in 1.0 though for private comms.
-
-
nice
-
-
For this particular case, it's more an instance of the software not interacting (in the sense of not changing things they don't understand).
If Lemmy doesn't implement flairs, then community updates from them won't over-write flairs set on PieFed's copy of those comms. Also, when a PieFed user sends a comment to a Lemmy community, it will just attach an 'Announce' header to it and send it out to all followers. It would be against their own spec to change the content of anything they're Announcing, so followers who receive the comment and happen to be on PieFed instances will interpret it fully, whereas Lemmy will just ignore any fields in the JSON that it doesn't have a use for.
-
comms
So Fetch.
11 comments
I love exploring this lol, even when it's totally nonsensical. Like, what does a Mobillizon event look like from PeerTube? Does it show up? If I have an image embedded in a WriteFreely article, how/where does that image appear when viewing the article from WAFRN?
It's neat stuff, I don't even mind the jank at all, kinda gives the whole thing a quirky sort of appeal. The only scenario I don't love is when 2 of them are totally inoperable and can't see each other at all.