Hi all, I've been working on a p2p media app that uses webtorrent basically in round table bubbles.
Its basically a Venn Diagram I figure you need peers for p2p and for social sites so why not put the two together. Yes its another group chat and yes its social media but its also webtorrent. It uses graphql which makes for some interesting data structures, and it has a livestream from webtorrent. Its quasi-live as in there is a delay and it posts in 8 second chunks that are assembled on the client side. Its called bubbleBASED because its bubbly & based.
I have about hopefully a week left until it is where I want it to be, any feedback I'll put into the app. The global UI isn't amazing right now but if you login its better but I figure having the public stuff is good for seo and discovery.
It has a cdn under it all but its creative with trying to use as much webtorrent as is reasonable/unreasonable. The app has been closed behind privacy walls for a while and I'be been building the public layers in this week.
The intent is to have social media that doesn't try to cram as much stuff in front of your eyes as is chosen by the algorithm. Like when you boot up this app you get your own home bubble and you can see public "bublic" and global bubbles. Global bubbles are what you see here, they exist outside the app. Private bubbles you will never see unless you are in one, and the 'bublic' bubbles are in app only. The stream follows suit in terms of you stream to a bubble and if you are in the bubble you see the stream.
I have some work to do with routing the livestreams (right now they all coalesce in one tab but I want them separated so you can share just one livestream and not see the entire bubble. Stuff like that but its graphql and its annoying lol.
Basically the key to this thing is that it shares the metadata quickly to users so they know where the magnetlinks are, and I run a tracker to connect seeders/feeders. There is no aws or s3 buckets or anything like that but there is mongodb and heroku and ipfs & piñata (cdn and pinning) and a lot of caching (and i have some backend caches i still need to reconnect). Also it uses the idbchunkstore its a webtorrent thing that stores torrent data in indexeddb to keep swarms going. I figure lets be the data center why not.
Its also an attempt to have a human algorithm (oh the humanity). And there is an option to submit a cj.com affiliate link if you want to add one to your profile the site picks at random and places them so its a community monetization thing. Its also an attempt to reconnect people to their actual social media communities so people aren't shadowbanned/throttled/promoted/excluded. There are more privacy controls on the way (bubble visibility etc). User can select public or private right now so even if they post in a global (web facing) bubble the site doesn't print those so no one will see. I want member lists to be the same way, stuff like that but you have to deal with the db a lot :). Private bubbles are invite only at the moment so you actively have to get people to your bubble (or join from an invite).
Anyways have a great week and thanks for checking it out.
Hi all, I've been working on a p2p media app that uses webtorrent basically in round table bubbles. Its basically a Venn Diagram I figure you need peers for p2p and for social sites so why not put the two together. Yes its another group chat and yes its social media but its also webtorrent. It uses graphql which makes for some interesting data structures, and it has a livestream from webtorrent. Its quasi-live as in there is a delay and it posts in 8 second chunks that are assembled on the client side. Its called bubbleBASED because its bubbly & based.
I have about hopefully a week left until it is where I want it to be, any feedback I'll put into the app. The global UI isn't amazing right now but if you login its better but I figure having the public stuff is good for seo and discovery.
It has a cdn under it all but its creative with trying to use as much webtorrent as is reasonable/unreasonable. The app has been closed behind privacy walls for a while and I'be been building the public layers in this week.
The intent is to have social media that doesn't try to cram as much stuff in front of your eyes as is chosen by the algorithm. Like when you boot up this app you get your own home bubble and you can see public "bublic" and global bubbles. Global bubbles are what you see here, they exist outside the app. Private bubbles you will never see unless you are in one, and the 'bublic' bubbles are in app only. The stream follows suit in terms of you stream to a bubble and if you are in the bubble you see the stream.
I have some work to do with routing the livestreams (right now they all coalesce in one tab but I want them separated so you can share just one livestream and not see the entire bubble. Stuff like that but its graphql and its annoying lol.
Basically the key to this thing is that it shares the metadata quickly to users so they know where the magnetlinks are, and I run a tracker to connect seeders/feeders. There is no aws or s3 buckets or anything like that but there is mongodb and heroku and ipfs & piñata (cdn and pinning) and a lot of caching (and i have some backend caches i still need to reconnect). Also it uses the idbchunkstore its a webtorrent thing that stores torrent data in indexeddb to keep swarms going. I figure lets be the data center why not.
Its also an attempt to have a human algorithm (oh the humanity). And there is an option to submit a cj.com affiliate link if you want to add one to your profile the site picks at random and places them so its a community monetization thing. Its also an attempt to reconnect people to their actual social media communities so people aren't shadowbanned/throttled/promoted/excluded. There are more privacy controls on the way (bubble visibility etc). User can select public or private right now so even if they post in a global (web facing) bubble the site doesn't print those so no one will see. I want member lists to be the same way, stuff like that but you have to deal with the db a lot :). Private bubbles are invite only at the moment so you actively have to get people to your bubble (or join from an invite).
Anyways have a great week and thanks for checking it out.