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

You are viewing a single thread.
View all comments View context
1 point

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.

permalink
report
parent
reply
1 point
*

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…

permalink
report
parent
reply

Lemmy

!lemmy@lemmy.ml

Create post

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

Community stats

  • 864

    Monthly active users

  • 1.1K

    Posts

  • 14K

    Comments

Community moderators