So if the OP posts a follower-only post, all subsequent posts should be restricted to the followers of the OP, not the followers of the respondent.
-
So if the OP posts a follower-only post, all subsequent posts should be restricted to the followers of the OP, not the followers of the respondent.
(continues)
In addition, all of the subsequent posts, even posts that do not tag the OP, should be routed through the original poster’s instance.
(continues)
-
In addition, all of the subsequent posts, even posts that do not tag the OP, should be routed through the original poster’s instance.
(continues)
So... say, user UA on instance A writes a new post. User UB on instance B replies. User UC on instance C replies to UB’s post. User UD replies to UC’s post. UD’s post should reach instances C and B though A (D -> A -> C and D -> A -> B). Same with all other replies.
This may also give the OP the authority to delete any subsequent post in that thread.
(continues)
-
So... say, user UA on instance A writes a new post. User UB on instance B replies. User UC on instance C replies to UB’s post. User UD replies to UC’s post. UD’s post should reach instances C and B though A (D -> A -> C and D -> A -> B). Same with all other replies.
This may also give the OP the authority to delete any subsequent post in that thread.
(continues)
In other words, a new post should be treated somewhat like a blog, and every response and response-to-a-response should be treated somewhat like comments under a blog.
(continues)
-
In other words, a new post should be treated somewhat like a blog, and every response and response-to-a-response should be treated somewhat like comments under a blog.
(continues)
I think this will also eliminate the need to tag the users one is responding to, for them to receive notifications. That will save many characters which can be used for actual post content.
(The need to tag in Mastodon-like platforms is a headache. If there are too many people participating in a conversation, then a whole lot of characters are lost in tags. In addition, one also has to think of hashtags. So very few characters are left for the actual post.)
(continues)
-
I think this will also eliminate the need to tag the users one is responding to, for them to receive notifications. That will save many characters which can be used for actual post content.
(The need to tag in Mastodon-like platforms is a headache. If there are too many people participating in a conversation, then a whole lot of characters are lost in tags. In addition, one also has to think of hashtags. So very few characters are left for the actual post.)
(continues)
I believe Mike Macgirvin’s ActivityPub-based #Forte behaves in the fashion I have described above. So it may be worth checking out.
(continues)
-
I believe Mike Macgirvin’s ActivityPub-based #Forte behaves in the fashion I have described above. So it may be worth checking out.
(continues)
If Mike's pioneering work would be accepted by other developers (particularly Eugen), fedi would be in a much, much better shape. Alas...
@feralthoughts -
If Mike's pioneering work would be accepted by other developers (particularly Eugen), fedi would be in a much, much better shape. Alas...
@feralthoughtsAgreed.
Sadly, most of Fedi centered around microblogging, and microblogging centered around Mastodon.
It is what it is.
-
If Mike's pioneering work would be accepted by other developers (particularly Eugen), fedi would be in a much, much better shape. Alas...
@feralthoughtsI was wondering if #Forte is the only #ActivityPub software to implement Conversation Containers and Nomadic Identity. Do you know of any others?
-
I was wondering if #Forte is the only #ActivityPub software to implement Conversation Containers and Nomadic Identity. Do you know of any others?
I'm not an expert on the subject, but..
Oh, Zot! Nomadic Identity is Coming to ActivityPub
One of the Zot's most powerful concepts for identity management and remote access is being ported to work on ActivityPub. It could change the Fediverse.
We Distribute (wedistribute.org)
That is, to the best of my knowledge it's all Mike.
@feralthoughts -
I'm not an expert on the subject, but..
Oh, Zot! Nomadic Identity is Coming to ActivityPub
One of the Zot's most powerful concepts for identity management and remote access is being ported to work on ActivityPub. It could change the Fediverse.
We Distribute (wedistribute.org)
That is, to the best of my knowledge it's all Mike.
@feralthoughtsI know about Hubzilla and (streams), but they are both based on Nomad/Zot protocol. I was asking about software based on ActivityPub. I guess then Forte is the only ActivityPub-based software to implement Conversation Containers and Nomadic Identity.
-
I know about Hubzilla and (streams), but they are both based on Nomad/Zot protocol. I was asking about software based on ActivityPub. I guess then Forte is the only ActivityPub-based software to implement Conversation Containers and Nomadic Identity.
@feralthoughts @osma Conversation Containers are used by Forte, Streams, Hubzilla and Mitra. There is a list of known implementations at the end of FEP-171b:
>I know about Hubzilla and (streams), but they are both based on Nomad/Zot protocol.
Hubzilla and Streams support Nomad and ActivityPub.
Forte is ActivityPub-only. -
@feralthoughts @osma Conversation Containers are used by Forte, Streams, Hubzilla and Mitra. There is a list of known implementations at the end of FEP-171b:
>I know about Hubzilla and (streams), but they are both based on Nomad/Zot protocol.
Hubzilla and Streams support Nomad and ActivityPub.
Forte is ActivityPub-only.Thank you - I wasn't aware of Mitra supporting conversation containers and nomadic identity, happy to learn.
I have some questions about Mitra, I will ask them in a separate thread.
