3 ms·
The problem with public instances is that they're constantly overloaded. Your best bet is to run your own.
by Nextgrid 4y ago
The problem with public instances is that they're constantly overloaded. Your best bet is to run your own.
- ecliptik 4y agoI started running my own this week because the public instances are inconsistent. Performance is better overall, but some things are still sluggish (teddit) because you're usually the only fetching data and nothing is cached. Paired with Tailscale makes for a good combination too.
- 3np 4y agoTeddit specifically has this unfortunate behavior where every referenced subresource is loaded before a response is returned: https://codeberg.org/teddit/teddit/issues/248 https://codeberg.org/teddit/teddit/issues/248 Until that is resolved, libreddit (similarly self-hostable) performs much better.
- orblivion 4y agoWhich is what I figured is the point, since it's libre. On the other hand doesn't that defeat the purpose of the privacy thing? If every request for ~one user's worth of traffic is coming from one proxy you can sort of identify one person that way.
- Nextgrid 4y ago> On the other hand doesn't that defeat the purpose of the privacy thing? It depends - a lot of the privacy invasions go beyond just the IP address and also include browser fingerprints and on-page activity collected by malicious Javascript - these third-party frontends defeat that.