-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Look into content hosting options #632
Comments
I was having this conversation with Lizard the other day, and we were investigating https://glitch.com When you setup a site there it's uptime is limited based on your subscription tier (free apps time out after 5 minutes, paid tier gets you 5 always-on apps), however the file hosting is not affected by the container shutting down. I've verified this by creating a Glitch project and testing a direct link to a CSS file hours and even days after the last time it was accessed. Every time the file comes back immediately which tells me they're keeping static hosting around and only the container runtime is paused after the free-tier timeout. I just checked the URL again and it's been over a week since my last attempt. We could create a simple frontend that could also be hosted on Glitch that would allow a user to upload their files and receive a directory listing with direct links. |
I also agree glitch seems like a solid option to host simple stuff. There also used to be keybase but the html frontend of that appears to have been removed after its latest corporate merger. |
IPFS? runs away |
I've created a Glitch project that anyone can "remix" (copy) which provides a basic backend for uploading and managing files. Upon digging further I learned that Glitch made a change a while ago so now all static sites are always-on, this has the transient effect of any asset uploaded to glitch is always available even if the container application (node in this case) is not running. Glitch limits the total amount of space you can have per project, but you can create an infinite number of copies of this project. I have no idea if using their service in this way is a violation of the ToS |
From Discord discussion: Discord plans to make content links temporary, so discord won't be usable anymore as of 2024 |
From Discord discussion: |
New users are having problems hosting things like avatars.
Dropbox has been tried, but is not an ideal option.
We could use researching the options out there, the difficulty of using them, whether they're friendly towards serving content to people, and whether there are any associated problems (pricing, etc). The results should then be placed prominently in the documentation.
The text was updated successfully, but these errors were encountered: