You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow users to upload images, or enter URLs which the application then fetches, and store them "locally". On Heroku, that would probably mean in S3; if we switch to a VPS, then we could store them on the filesystem (this might be the issue that causes us to switch away from Heroku; see also #11).
This is valuable because some image hosts, such as Twitter, are automatically blocked in Firefox - see their article about tracking protection.
Thanks to @ihross for helping to discover this issue!
The text was updated successfully, but these errors were encountered:
This is closely related to #26, but whereas #26 could be solved by accepting URLs to images hosted elsewhere, this would involve hosting the images directly.
Allow users to upload images, or enter URLs which the application then fetches, and store them "locally". On Heroku, that would probably mean in S3; if we switch to a VPS, then we could store them on the filesystem (this might be the issue that causes us to switch away from Heroku; see also #11).
This is valuable because some image hosts, such as Twitter, are automatically blocked in Firefox - see their article about tracking protection.
Thanks to @ihross for helping to discover this issue!
The text was updated successfully, but these errors were encountered: