Need some help.
Need some help.
Hey everyone, I've had a project in the works for a bit now since all gestures broadly was obviously going to happen since november and watching how the powers that be continually try to punish those who speak out against the crimes of our governments.
But I need some help testing / verifying it and just got it to the point its semi usable. its called retrovibed and its a system for digital distribution via bittorrent but with a userspace VPN builtin, have plans for i2p in the far future (mostly there isnt a good golang library to integrate, if someone knows of a decent one that implements the stdlib interfaces it'd take me less than a morning to integrate).
the goal for the EOY is a completely distributed and anonymous way to publish data using peer ids to follow and push magnet url's. essentially it will let groups and communities publish reports/data without exposing themselves while being easy to use for the non-technically inclined.
Basically, its a torrenting system with a builtin media player, and userspace wireguard vpn, and support for natpmp. essentially it allows you to add a standard wireguard config which secures all bittorrent traffic within the application w/ natpmp support for automatic port forwarding.
Its not quite ready for widespread use as I havent streamlined the publishing aspects. I plan to add a couple small extensions to allow push/follow of infohashes from a dht id for mass distribution without any hosted servers.
but need a little help testing to ensure the traffic is properly secured.
anyone technically inclined (or even better not technically inclined) interested in helping out? its linux only right now, but macosx support would be easy to add. mostly just dont have bandwidth to manually test and write the distribution packaging code.
signal if you're interested.
You're viewing a single thread.
Can you explain a little bit more about how it will work. I get its a p2p torrent system, but it also looks like a media player? so like direct media sharing? is the plan to share it and store it in a library on the client side so they can watch it later and or share it later?
I could probably help you a bit in testing. I am a linux guy. I dont really know go (not enough to help you code, but enough to maybe trouble shoot). but I could help you test on the distant end.
Basically you can think of it as plex/jellyfin sans the trancoding with builtin distribution via torrenting, a social network for recommendations, and isnt limited to just movies/music.
The good news is its fairly straightforward to operate the readme has the commands to install the flatpak and we dont really need coding help, actually have a couple other developers willing to chip in once i get this off the ground. They're actually willing to help now but Im waiting until i can compensate them for their time or there is enough interest it makes sense.
Mostly atm testing, feedback, and spreading the word are the big gaps. Im still streamlining the ux but the bulk of the functionality is there. If you tap the signal link ill gladly walk you through it.
But here goes....
- torrenting
- media
- vpn
- archive cloud storage.
- rss feeds
Essentially it can integrate with your normal p2p swarms public or private. And directly index and play the resulting content. (Im integrating tmdb next week hopefully)
Beyond your standard distribution via torrents you have two modes (only one is implemented atm).
First is you can grant access to your library directly with family/friends by adding their public key to the application bypassing the p2p stuff for them. This is a little awkward atm, havent had time to clean it up.
Hopefully by the end of the year ill have a follower system that basically provides magnet links + metadata as recommendations, essentially you'll be tap your friends dht peer id and get anonymous recommendations based on what they watched/added/promoted/were recommended. This allows for the viral spread of content without needing a bunch of recommendation algorithms. Essentially your friends (and their network) are the recommendation algorithm.
The cloud storage piece is for communities to reduce the costs individually of archival storage without having to manage their own infrastructure. While encrypting everything so the service cant actually see the content. Essentially every user that pulls in the same content from the same feed will reduce the cost for everyone else from that feed. While the storage service only will know the mimetype of the encrypted data.
On top of that it can seamlessly recover the data from the archive on demand for either for consumption by the media player or distributing via torrents, so the local disk space requirements are much lower im pretty sure you can get away w/ ~128GB and have tens if not hundreds of tb archived and available to seed/watch. There are bandwidth limits here as that is the expensive bit, im hoping once the system reaches a critical mass of users ill be able to start decreasing the download limitations. ~12k subscriptions that enable the arch linux iso feed. ;)
The storage service provides the income for the services, the cost reduction is 80% per user at ~ 32 users of a file. Aka you have a 1 gigabyte file archived and you end up being charged 200mb of storage because of the other users. the subscription fee covers the initial storage limit (2tb), api servers, and payment processing fees.
Essentially the storage is useful for perseving content like we're seeing this administration try to wipe from the public sphere and provides the revenue so i can continue the work while saving everyone who uses it money. The storage for data only a single person has is charged at cost. (~0.2/gb + payment processing %age)
The vpn provides anonymity for what you're doing obv. Which allows whistleblowers and journalists to communicate without having any idea who the person is. For example tracking and documenting ice activities for others to act upon.
The longer term (and original) plan is to for this platform to also serve content creators by allowing them to directly share their content with their followers and get a direct cut of the revenue from the higher subscriptions and storage profits without having to shill ads or get nickled and dimed.on view counts.