devnull ,
@devnull@crag.social avatar

At an in-office session with the team, talking

There are some hard questions to answer, such as:

  • how to scalably introduce the concept of ACL at the post/toot level.
  • how to educate about the in a user-friendly way
  • how to solve the "empty home feed" problem
  • how do we handle compliance when federating in and out?
  • how do we improve on "newest to oldest" without introducing a corruptible algorithm?

@nodebb is all in on fedi. Let's make it work.

tfardet ,
@tfardet@fediscience.org avatar

@devnull
> how to solve the "empty home feed problem"

Naive question: I thought nodebb was for forums, why would this be an issue in that context?

Regardless, I hope if you have anything similar to hashtags (topics?) you will be able to use some topic-following scheme it rather than recommending people, thus avoid the rich-get-richer type of dynamics.
@nodebb

0x1C3B00DA ,
@0x1C3B00DA@stereophonic.space avatar

@devnull @nodebb

how to scalably introduce the concept of ACL at the post/toot level.

Very interested to hear yall’s ideas on this.

how to educate about the in a user-friendly way

…and an accurate way. I think a lot of the blowups on the fediverse come from the way mastodon misrepresents the fediverse to ppl, notably that it’s privacy-focused.

how do we handle compliance when federating in and out?

I’d be interested to hear what yall come up with for this too. It seems like ActivityPub is strictly incompatible with GDPR. If a user asks to delete their data, you can comply on your server but never guarantee that it’s deleted from the network. And then there’s the permission requirement for sharing data, which seems to mean basic federation isn’t allowed without a user’s explicit permission.

devnull OP , (edited )
@devnull@crag.social avatar

@0x1C3B00DA Our working understanding right now will treat the "unlisted" visibility level as a Mastodon-only quirk that has no meaning in . Will update with more info re: post ACLs as we develop.

supports mentioned-only which is unintentionally leaky (one errant mention and the jig is up). We intend to fully de-couple mentions from the ACL, so you can mention anybody you want, but that doesn't change the ACL if you restrict visibility to certain people.

devnull OP ,
@devnull@crag.social avatar

@0x1C3B00DA we are honestly not entirely sure how to handle the aspect. We may have to put together a public working group (incl. lawyers) to discuss.

If your service processes Undo and Delete activities, you could argue that you adhere to Right to be Forgotten, but there is more to GDPR than just erasure/modification.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • fediverse
  • kamenrider
  • Rutgers
  • MidnightClan
  • Lexington
  • cragsand
  • mead
  • RetroGamingNetwork
  • mauerstrassenwetten
  • loren
  • xyz
  • PowerRangers
  • AnarchoCapitalism
  • WatchParties
  • itdept
  • supersentai
  • neondivide
  • space_engine
  • AgeRegression
  • WarhammerFantasy
  • Teensy
  • learnviet
  • bjj
  • khanate
  • electropalaeography
  • steinbach
  • jeremy
  • Mordhau
  • fandic
  • All magazines