Sharing Media Anywhere

Name
Email
Subject
Comment *
File	Select/drop/paste files here
Password	(Randomized for file and post deletion; you may also set your own.)
Archive	Archive [500 char limit]
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Voice recorder	Show voice recorder (the Stop button will be clickable 5 seconds after you press Record)
Options	Do not bump (you can also write sage in the email field)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, pdf Max filesize is 16 MB. Max image dimensions are 15000 x 15000. You may upload 5 per post.

File: 685b3812fef42cf⋯.png (135.48 KB, 1200x674, 600:337, webtorrent.png)

Sharing Media Anywhere Anonymous 02/07/21 (Sun) 01:16:12 bb372d No.12844763

I have an idea and I've been trying to collect some feedback on this idea before I sink 9000 hours into building it, but I think I'm going to anyway. It will all be open source. The idea was born here anyway.

Instead of sharing the content directly, you share a tag.

The Goal: During happenings, it's difficult to share media with the amount of censorship big tech has all over the place, and general limitations of places like 4chan, 8chan, etc. Sharing media directly on these sites also puts them on the hook legally. The goal, is to easily share content on any platform, even those which only support text. Here is the general concept:

user posts share tags

[multishare type=video protocol="http" src="https://file.mp4"] (including .onion)

[multishare type=image protocol="magnet" src="magnet://image.jpg"]

keep tags human readable to allow manually accessing content

browser side (extension/userscript) reads tags

send to external program to handle transfer

external program creates local api, browser hits local api to exchange data

replace tag with content from local api

sharing of content uses same api, browser extension / userscript

communicates with external program, which manages shared content based on

protocol

external program communicates with third party program to manage and assist sharing and generating tags: (host file directly / tor), retroshare, ipfs links, torrent clients, etc

The userscript would simply replace the tag with the content, and as far as the browser is concerned it came locally (localhost, maybe another server if you want to separate) How the content is shared would be up to the person sharing it, which protocol, etc, and the receiving user based on what they have set up and want to enable. (tor/ipfs/retroshare/etc). You could even steg an image or something and use that as a tag to further evade censorship, adding passwords/pgp to select which viewers you want to see the media share.

The entire system could be modular, and the extension/userscript and external program could be hosted on completely separate computers.

Is this worth building?

____________________________

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

Anonymous 02/07/21 (Sun) 04:24:40 e1e029 No.12846153

Have you heard of Hydrus Network?

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

Anonymous 02/07/21 (Sun) 04:25:17 e1e029 No.12846158

https://github.com/hydrusnetwork/hydrus

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

Anonymous 02/07/21 (Sun) 04:49:30 bb372d No.12846339

>>12846158

>>12846153

awesome thanks!,

It's pretty similar to what I'm trying to do, almost the same concept except for being modular, I don't want to actually create the server serving files or have a separate network, just have plugins or modules or something for each network (retroshare, torrents, straight http/https).

Now that I've seen this though it's definitely going to be a part of the equation, be able to integrate with their network atleast.

The difference here seems to be the requirement for a dedicated client, in the case of the system I'm working on here, the interaction would still happen within the browser, there would be a separate client/server in the background doing the data transfer, but it would essentially be command line driven, videos and media would just show up in place of the tag in the users browser; and even without the client/userscript you should be able to read the tag yourself to get the content.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

Anonymous 02/07/21 (Sun) 05:01:33 bb372d No.12846424

>>12846158

you wouldn't even need the userscript/external program component to share anything; just use a simple tag format wherever your posting.

as I'm thinking about the structure of this that's all the external program would be doing for the most part, generating a tag, and depending on what the network is and what client side api's they have, interacting with the third party program directly to help make it simple to share something.

If you uploaded a video to dropbox for example, you wouldn't have to do anything with the external program component except maybe have it help you to generate the tag, but the tag would simply be

[multshare type="video" protocol="http" src="dropbox.com/yourvideo.mp4"]

anyone with the userscript would see an option to display it instead of the raw tag.

the userscript would send "dropbox.com/yourvideo.mp4" to the external component, which would download it, and then send a link back to the userscript like "localhost:9999/yourvideo.mp4".

the userscript would then just replace the [multishare] tag with the video itself and display it.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.