Relaxing treatment of non-notes by Mastodon
-
Erin π½β¨ Β π 38C3replied to Erin π½β¨ π 38C3 on last edited by@trwnh @hongminhee @julian @michael @mike @pfefferle @renchap @thisismissem if we got to do a clean slate do over, I'd commit to either full unification or separation of objects and activities, and also the "implicit collections" would not be reified as Objects (ideally we'd get structural addressing too: you'd be able to explicitly refer to a users followers - for example - without having to know the URL of the collection)
-
Erin π½β¨ Β π 38C3replied to infinite love β΄³ on last edited by
-
infinite love β΄³replied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @julian @mike @hongminhee @thisismissem @pfefferle @michael @renchap
This is why it should be simplified to βjust render the content/summary/nameβ for blogging-oriented apps. The combinatorial explosion is a consequence of hyperlinks. You canβt do away with it. Side effects should be progressive enhancements.
As a publisher, what you CAN do is decide not to put a `likes` collection on everything. This means that the Like of a Like has no side effects.
-
Jenniferplusplusreplied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @julian @mike @hongminhee @thisismissem @pfefferle @trwnh @michael @renchap
In that clean slate scenario, i would want to explore moving the information carried by activities into headers. -
infinite love β΄³replied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @darius I heavily dislike the firehose model and would be terrified if my email inbox submitted to the same philosophy.
-
Laurens Hofreplied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @darius @trwnh the fediverse in general could benefit from thinner servers and thicker clients, it would make all these interop discussions so much easier
-
Erin π½β¨ Β π 38C3replied to Laurens Hof on last edited by
-
Laurens Hofreplied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @darius @trwnh right, yeah, i meant this as a i'm-shouting-with-you-in-agreement-post
-
infinite love β΄³replied to Jenniferplusplus on last edited by
@jenniferplusplus @erincandescent @julian @mike @hongminhee @thisismissem @pfefferle @michael @renchap
We should go back to WebSub⦠and we should also go back to calling it PubSubHubbub
-
Erin π½β¨ Β π 38C3replied to infinite love β΄³ on last edited by@trwnh @darius I actually think this demonstrates a fundamental flaw in the email model
There are times you want to be able to do endpoint to endpoint but potentially automatic message exchanges, and email doesn't really have a mechanism for doing this
The straightforward example is my client noticing your S/MIME or GPG key is expiring and asking if there's a new one -
Evan Prodromoureplied to infinite love β΄³ on last edited by
@trwnh @thisismissem @pfefferle @hongminhee @julian @renchap @mike @michael icon, image can help too.
-
infinite love β΄³replied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @darius i think this could be solved by declaring specific endpoints for these things. no reason it should ever reach my inbox unless it's meant for my attention.
-
Erin π½β¨ Β π 38C3replied to infinite love β΄³ on last edited by
-
Evan Prodromoureplied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @julian @mike @hongminhee @thisismissem @pfefferle @trwnh @michael @renchap In pump.io, we divided the inbox stream between "major" (new content, new shares) which is shown in a home timeline interface and "minor" (everything else) streams which are shown like notifications. Your scrobbles should be notifications and should be silenceable by the recipient.
-
infinite love β΄³replied to Erin π½β¨ π 38C3 on last edited by
@erincandescent @darius if the actor represents me, then it is "my" inbox.
the correct solution imo is to spin up more bespoke actors. i'd really like to build upon the concept of "programmable actors", i.e., actors that are automated to act a certain way with activities they receive in their inbox. for example, a Relay could be defined as a programmable actor that Announces the object of any Create it receives, or Announces any activity it receives, or whatever. and it should be a JSON-LD type
-
Erin π½β¨ Β π 38C3replied to infinite love β΄³ on last edited by
-
Evan Prodromoureplied to infinite love β΄³ on last edited by
@trwnh @erincandescent @darius neat! The https://github.com/evanp/bots-rodeo/ platform is supposed to do just that.
-
Erin π½β¨ Β π 38C3replied to Erin π½β¨ π 38C3 on last edited by
-
Erin π½β¨ Β π 38C3replied to Erin π½β¨ π 38C3 on last edited by
-
Matthias Pfefferlereplied to infinite love β΄³ on last edited by
@trwnh @jenniferplusplus @erincandescent @julian @mike @hongminhee @thisismissem @michael @renchap
ActivityPubSubHubbub!
