You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I may be just a bit dumb, but I've been wondering if a social timeline could be built, peer-to-peer, from each user out to their contacts? And while I don't pretend to understand the code (arduino hack, me), the principles look like they could be adapted to a packet-by-packet timeline, looking like any microblogging platform.
Essentially, each copy of this kind of app would be a platform to post to, download others timeline posts (each post a single datagram packet, packets from others would be read-only when public key decrypted) and each copy of this app could run its own room, for live chat sessions or do straight 2 party conversations, too.
I left Facebook last year and joined a Mastodon instance early this year, but now there's Threads hoovering up all the masto-posts to be included in their ongoing giant human population manipulation experiment. I figure that there must be better coders than me who could create something like this.
From what I can gather from your code, you'd only need to create message types, say: post_message for timeline contributions attach_message for media attachments, dm_message for person to person, room_message for chat groups. Users would only be able to share post_messages if they'd exchanged public key tokens via dm_message. No user would be able to see a friend of a friend's posts that were selected to a non-public permissions level. The idea is like Manyverse, but with a room server built into the app and using UDP instead of a custom protocol. Just add encryption and on-boarding is like it is in real life, know somebody? Swap contact details, in this case, press a button to swap public keys.
I know, this is way bigger than a humble bug report, but I think you're sitting on code that is potentially the next big wave in social media, not the fediverse, not the manyverse, but the few. Social networks that grow from each user, peer-to-peer, outwards, and the social part happens where friend/family/work/club/community groups overlap.
I know my limitations, I know I don't have enough life or brain to learn what's needed in time to complete something. But it looks to me like you do have the basic framework for what could be humanity's saviour from being "enslaved" to big data. You might be able to turn the antisocial back into social.
The text was updated successfully, but these errors were encountered:
So, I may be just a bit dumb, but I've been wondering if a social timeline could be built, peer-to-peer, from each user out to their contacts? And while I don't pretend to understand the code (arduino hack, me), the principles look like they could be adapted to a packet-by-packet timeline, looking like any microblogging platform.
Essentially, each copy of this kind of app would be a platform to post to, download others timeline posts (each post a single datagram packet, packets from others would be read-only when public key decrypted) and each copy of this app could run its own room, for live chat sessions or do straight 2 party conversations, too.
I left Facebook last year and joined a Mastodon instance early this year, but now there's Threads hoovering up all the masto-posts to be included in their ongoing giant human population manipulation experiment. I figure that there must be better coders than me who could create something like this.
From what I can gather from your code, you'd only need to create message types, say: post_message for timeline contributions attach_message for media attachments, dm_message for person to person, room_message for chat groups. Users would only be able to share post_messages if they'd exchanged public key tokens via dm_message. No user would be able to see a friend of a friend's posts that were selected to a non-public permissions level. The idea is like Manyverse, but with a room server built into the app and using UDP instead of a custom protocol. Just add encryption and on-boarding is like it is in real life, know somebody? Swap contact details, in this case, press a button to swap public keys.
I know, this is way bigger than a humble bug report, but I think you're sitting on code that is potentially the next big wave in social media, not the fediverse, not the manyverse, but the few. Social networks that grow from each user, peer-to-peer, outwards, and the social part happens where friend/family/work/club/community groups overlap.
I know my limitations, I know I don't have enough life or brain to learn what's needed in time to complete something. But it looks to me like you do have the basic framework for what could be humanity's saviour from being "enslaved" to big data. You might be able to turn the antisocial back into social.
The text was updated successfully, but these errors were encountered: