RexSystem1 voteoriginally by @Jonesyandbeast on GitHub1 reply
What if we also had an option in settings to have select file saving on the users computer. This may cause issues with storage, so we could spread media storage across members of the server. If a user's limit passes an arbitrary limit(say 5 gb) we could then start expiring media. This could work especially well if the most recent percent(5-10% of allocated storage) was duplicated across all users storage for offline access with the rest being selectively allocated among users.
Let me know if there are any flaws in this logic or if anyone else has ideas for this type of storage solution.
RexSystem1 voteoriginally by @lexifuzzpup on GitHub OP
I think a decentralized storage system would be interesting, but not necessarily something that should be worked on right now. It would be a fun serverless implementation of the storage issue, but from my experience, they take a long time to implement and can be unreliable.
I see some flaws and implementation detail issues with this idea:
It doesn't necessarily solve the file deletion issue, since they'll still be deleted above a threshold.
Fluxer has users who access the app using various devices, and not all devices are created equal. Some people might be running beefy computers, while some might be using a mobile phone from 2011, so how should media sharing be decided?
If a user is offline who holds media, how is that file retrieved?
Decentralization adds to the turbidity and uncertainty of communities; some files may be unavailable at times or may get corrupted. For example, someone being the sole possessor of a piece of media allows them to manipulate (albeit solvable with crypto signatures) or delete the original file without the author's knowledge.
However, I do see some pros over the Docker image idea:
Fluxer doesn't have to store media on the server, for users who have decentralized media buckets enabled.
If a torrent approach is used, then media can be delivered a lot faster to retrievers.
Users don't have to set up and administrate a Docker container.
Thread
Comment by @Jonesyandbeast
Comment by @lexifuzzpup
- It doesn't necessarily solve the file deletion issue, since they'll still be deleted above a threshold.
- Fluxer has users who access the app using various devices, and not all devices are created equal. Some people might be running beefy computers, while some might be using a mobile phone from 2011, so how should media sharing be decided?
- If a user is offline who holds media, how is that file retrieved?
- Decentralization adds to the turbidity and uncertainty of communities; some files may be unavailable at times or may get corrupted. For example, someone being the sole possessor of a piece of media allows them to manipulate (albeit solvable with crypto signatures) or delete the original file without the author's knowledge.
However, I do see some pros over the Docker image idea: