Subscription models only make sense for an app/service that have recurring costs. In the case of Lemmy apps, the instances are the ones with recurring hosting costs, not the apps.
If an app doesn’t have recurring hosting costs, it only makes sense to have one up front payment and then maybe in app purchases to pay for new features going forward
It’s wild what lemmy.world has done. If your referrer is lemmy.world itself, a click off their web page, it loads the comment. But if you come from another lemmy instance or just put the link directly into your browser address bar, they reject it with ERR_INVALID_RESPONSE - I can’t recall having seen a website do this to try and prevent attacks.
I also have the same problem… BUT it happens if simply try to open a comment on a new window using the link.
several people have confirmed it… I haven’t seen them explain how exactly, but they seem convinced it is causing crashes so they blocked it. Lemmy is practically in the realm of voodoo PostgreSQL at this point. Since April or May it’s been scaling very poorly as data gets added.
Well, that’s what happens when you go for PostgreSQL without much experience I guess. But it works… mostly :) I don’t get it why the database would f* up the application itself in this case, its a simple “get by id” operation…