@trwnh@mastodon.social but why must a separate account be made? Account fragmentation is yet another unsolved problem because the new user on account B is functionally useless: no followers, etc. and the content isn't automatically available to the followers of the user on instance A.

@evan@cosocial.ca hmm. I agree in the sense that any combination of recipients can be addressed, but the specific term "follower only" (to the exclusion of the public pseudo-user) isn't AP specific... could be wrong on that one. Either way I do think it's a good courtesy to assume equal or narrower visibility when replying to any post. The specific issue you outlined in OP seems to be a Mastodon bug for sure.

@mastodonmigration@mastodon.online while this is a known workaround, I don't think it's a tenable long-term solution. You can have "real decentralization" without the quirks, too.

@willi@social.tchncs.de a VPS can be had from DigitalOcean or Vultr quite economically (although I know that isn't always the case in some countries) You can also use our referral link for an account credit too!

NodeBB is gearing up for a major release this month that brings full two way federation and content discoverability to forums as well! We've been working on it all last year! @activitypub

Kommt echt an Ich bin verblüfft LOL

Angus, while I haven't made the appropriate changes to NodeBB's implementation yet, I did draft an FEP including the changes we discussed. https://github.com/julianlam/feps/blob/main/fep/15c5/fep-15c5.md It is not PR'd upstream yet, but I will do so in the coming days unless there are some concerns.

Good lord @liaizon@social.wake.st did you just necro a 3 year old topic