@wjmaggos@liberal.city that's true for Mastodon, but not for other servers with more of a community focused aspect, like NodeBB.

agreed, use syncthing (which I think @nutomic@lemmy.ml also works on!) and call it a day. @mariusor@metalhead.club @reiver@mastodon.social

@scott@loves.tech I have an OpenID login! I remember being terribly confused by it, and how to use it, and I think to this day it's only use is to log me into StackExchange

@silverpill@mitra.social when discussed with Nutomic about this, I made the case that 1b12 is excellent for synchronization. 7888 (and 171b, etc.) are good for backfill, in cases where there is no 1b12 implementation available.

@squinky@teh.entar.net in all seriousness it's entirely up to you which FEPs to support. Some FEPs have more adoption than others, so it would be wise to adopt them over time as well. Others deal with aspects of the protocol that may not even apply to your specific use case. There is no expectation that one should implement every FEP. Think of it this way: an FEP is a way to document in public (not in code!) how one or more implementations have approached a problem that the ActivityPub protocol spec did not cover. There may be a lot of them, they may be needlessly complicated, but it's better than having to dig through someone else's code base.

@altcode@social.vivaldi.net from what I can tell and from the people I've spoken to, the backend migration is the meat and potatoes of it all, and so the front-end would hopefully remain unchanged. It's one of those huge migrations where if everybody does everything perfectly, nobody will have known anything had happened at all

@projectmoon@forum.agnos.is yes, Lemmy has a local representation of this category, and sends the post here. I see that it's addressed to the category and automatically slot it in