I am by no means knowledgeable on the subject, so the suggestion might seems weird, but I would love it to be lass “arborescent” in its structure. I would love a single “child” item to have multiple “parents”. And that applies to :
User toward instances : a single user could be signed up in multiple instances that would mirror posts. As long as both instances allow it of course. That would allow to be present in multiple local timeline, and have some redundancy. That would also allow multiple peertube instances to host the same video, to help with the load when mutual seeding is missing.
Posts toward users. To allow multiple users to sign the same post would be great. It is to be quite different from a simple boost since there is no “OP”. Articles, music or even video can be made by multiple persons that don’t necessarily group up for a long time, so it does not justify the creation of a common identity like a music groups.
Combinaison of the two above : Post toward instances. A user belonging to two instances can either post to one, the other, or both. Then, this post is mirrored to both instances.
Comment/response toward post. This might seem weird. But being able make a single comment concerning multiple precedent posts can allow to make pertinent connection between subject and people.
In general, I think it is very difficult to think ahead about what uses people will find. So I think we should assume as little as possible and keep the uses as large as possible.
The things we refer to as “threads” are actually “branches of a tree”. […] It would be useful if a discussion branch was not only shaped like a thread, but also had the usefulness of one : sewing, or tying together different discussion topics.
This post was about the “Comment/response toward post.”. I also like your "Posts toward users. ". Coauthoring is definitely valuable ! Relatedly, one could imagine a channel (like on Peertube) owned by several users. Then the channel could publish their common work.
I am by no means knowledgeable on the subject, so the suggestion might seems weird, but I would love it to be lass “arborescent” in its structure. I would love a single “child” item to have multiple “parents”. And that applies to :
User toward instances : a single user could be signed up in multiple instances that would mirror posts. As long as both instances allow it of course. That would allow to be present in multiple local timeline, and have some redundancy. That would also allow multiple peertube instances to host the same video, to help with the load when mutual seeding is missing.
Posts toward users. To allow multiple users to sign the same post would be great. It is to be quite different from a simple boost since there is no “OP”. Articles, music or even video can be made by multiple persons that don’t necessarily group up for a long time, so it does not justify the creation of a common identity like a music groups.
Combinaison of the two above : Post toward instances. A user belonging to two instances can either post to one, the other, or both. Then, this post is mirrored to both instances.
Comment/response toward post. This might seem weird. But being able make a single comment concerning multiple precedent posts can allow to make pertinent connection between subject and people.
In general, I think it is very difficult to think ahead about what uses people will find. So I think we should assume as little as possible and keep the uses as large as possible.
Reminds me of this post where I said :
This post was about the “Comment/response toward post.”. I also like your "Posts toward users. ". Coauthoring is definitely valuable ! Relatedly, one could imagine a channel (like on Peertube) owned by several users. Then the channel could publish their common work.
Plume has this (for blogging). Also written in Rust.
All of that is possible with Activitypub. Its just that no one has implemented yet. Can you program?
No I can’t… But I should learn to, there is so much cool libre projects that I would like to help this way.