Kavin
Kavin
 Didn't use the format as it's self-explanatory.
Rename yotter-config.json to maybe yotter-config.json.sample and add yotter-config.json to the gitignore. This would fix all the merge conflicts instance owners have to do when updating their instance.
This way, we don't need to use RSS to fetch feeds (and hence avoiding the 6-7 second load time when loading feeds). The only drawback is that private instances can't...
Example URL: https://yotter.xyz/c/UCYEK6xds6eo-3tr4xRdflmQ 
Can we somehow cache requests to youtube and twitter? I found a python library to do so: https://pypi.org/project/requests-cache/ Ideally, we should cache for a small duration of time, let's say...
 Ideally, you should urlencode it and up it into a parameter instead of using hacks such as replacing `/` with `~`, etc. Also, what about using nginx for this?
Ideally, we'd want to do something like how invidio.us did, it was operated in with like 10 servers, 2 cores, 2 GB ram for each and with one larger server...
This definitely requires JavaScript, but is definitely a nice to have.
``` [2020-09-08 06:54:15,630] ERROR in app: Exception on /u/QuackityHQ [GET] Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app response = self.full_dispatch_request() File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request...
This requires JavaScript too, it's definitely a nice to have