@adam@kbin.pieho.me
@adam@kbin.pieho.me avatar

adam

@adam@kbin.pieho.me

A #PHP developer who, in his spare time, plays #Tabletop and #VideoGames; if the weathers nice I #Climb rocks, but mostly fall off of indoor #Bouldering ones.

Pronouns He/Him
Blog https://realmenweardress.es
Photos https://pixelfed.social/pieceofthepie
Keyoxide https://keyoxide.org/606B2E3C103A443663DA82716B37390F365AADAA

This profile is from a federated server and may be incomplete. Browse more on the original instance.

adam,
@adam@kbin.pieho.me avatar

The issue here is that Lemmy is federating out it's content with the pre blocks containing rendered code fit for some sort of code display plugin/CSS - which KBin doesn't have.

It would ideally send out the blocks html encoded and would let downstream implementations like KBin or others figure out how to display it themselves. I don't know how we would fix this.

adam,
@adam@kbin.pieho.me avatar

This is actually due to the way these platforms work. When a user comments on a comment or post on their instance it will be shown on their instance. It's then sent on to the owning instance of that comment or post. That owning instance then forwards it on to all interested parties (magazine instance, commenters instance).

Any instance in that chain can refuse to forward or broadcast that message due to a block, but the users own instance will likely always show that post. Ideally they would not do that and would be made aware of a block but that is a bit of a grey area in ActivityPub implementations.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • meta
  • Macbeth
  • All magazines