Michael 🇺🇦

@silverpill @julian

"A" could periodically re-fetch the thread.

Well, information like that should always be pushed, not pulled, because otherwise you create a lot of unneccessary load on the systems.

@mariusor @silverpill @julian I'd loved it, if AP had followed more the way that the Diaspora protocol pursuits. There every comment, every "like", whatsover is always only transmitted to the thread starter. And the thread starter then redistributes it. And you also can send a command to be included in this distrivution, although you never participated.

This would had solved a lot of problems, especially when it comes to non public posts.

@silverpill @julian Well, in my example B haven't removed C's comment. The banning had been done by C's server. So C's server have send an activity - that would reach B but not A.

And the problem still exists anyway, when A doesn't follow B, but simply fetched that thread. Then neither B nor C will perform any updates in the direction of A.

@silverpill @julian When A follows B and C comments in a thread from A, but on the server from B no one follows C, how will then A be notified by comments or edits from C? And what happens when C got banned for spam. How does this information reach A? On C's server you can see where the now banned contact wrote comments. But you don't see, that comments from C where distributed (or fetched) from A.

And it gets worse, when you simply fetch messages, that hadn't been pushed to you. Then you won't get any updates, except when you would pull it from time to time.

And of course some "give me all posts with that specific hashtag but only in these languages" will not work quite well, when you are on a stand alone server.

@julian To which point do you refer? For my first mentioned one we have got a special document at .well-known/x-social-relay that every Friendica server publishes that contains information about the subscribed hash tags.

And concerning the second point, I imagine some relay service that does not simply forward everything, but that knows which content you you are interested in. So when you subscribed to user A and user B posted something in a thread that user A started, then the relay would forward it to you, although you never subscribed to B. And when then the account B got deleted or blocked, then of course you would be notified as well.

@evan At Friendica we have a third way. When configured, we distribute posts to other servers that subscribed to the hashtags that the item contains.

But anyway: I would like to have got something like the AppView in the Atmosphere. Means: not a dumb relay but something like tags.pub, but much more sophisticated.

@evan I will try to keep it on my mind, when we eventuall have got a release. We included it in our upcoming release.

BTW: I saw that tags.pub is working with it, so our implementation doesn't seem completely wrong here 😀

@silverpill @julian Like at least has got the advantage to use the existing vocabulary. At Friendica we currently process both but we can't send - exactly because of the problem that we're still undecided which way to go.

A problem is that you could send a negative emoji - that would be received as a like (which is normally interpretet as positive) for example on Mastodon. And this can be confusing.

@rysiek @anominominominous I guess that you are mixing up relays with the AppView. Relays aren't very cost intensive. There are some independant out there, have for example a look here: firehose.stream/ and status.vayumandala.com/

AppView is cost intensive.