I'm kinda curious why none of the third party app developers considered selling Reddit requests as in-app purchases – just charge the rate Reddit charges.

Some of them are trying to figure something out.

https://www.reddit.com/r/RelayForReddit/comments/147152b/upd...

> There's no possibility to continue the free version of Relay; a monthly subscription price of $3 (or less) might be achievable.

And of that $3 the Developer says in that thread:

> Yes there should be a good amount in there for myself.

If 3rd party apps are so beloved, then $3/month to support a developer doing good work should not be a issue.

Paying a monthly subscription to only have access to half of Reddit (NSFW will not be available through third-party apps) sounds like a bad deal to me.

It's $3 today. What happens when Reddit triples the price with 30 day notice?

Don't forget that you alienate all those in poorer parts of the world unless you have regional prices.

Honestly $3 isn't bad, I'd gladly pay that to continue using my Reddit app.

I think so? PostgreSQL is very well written software AFACT.

I've run into version incompatibilities before, but it was my fault – they were expertly documented in the release notes and I just hadn't read them (or sufficiently tested the upgrade before the live performance of it).

Sure – and fail to meet their constraints

Is that even true? I don't think I've seen or read a direct apples-to-apples comparison of the two.

There could be all kinds of reasons why that is tho (if it is in fact the case).

I wouldn't think using "standalone" versus whatever would make much of a difference.

If you're using a hosted DB service, you're (probably) stuck in needing/wanting to rehearse using the hosted service (which is what the blog post describes).

If they were running the DB on 'regular server' cloud instances, it seems just as good to me to rehearse with other cloud server instances versus "standalone" servers.

I'd think using built-in replication (e.g. PostgreSQL 'logical replication') for 'dual writing' should mostly avoid inconsistencies between the two versions of the DB, no?

Yes, though I've only ever seen people use the term "dual writing" to refer to something at a higher-than-DB-level.

The way I've done this involves logical replication also: https://news.ycombinator.com/item?id=31087197

What's the structure that your custom DB uses?

I found your comment amusing!

Many!

I've found, repeatedly, tho that this is the best way to really understand the common pitfalls without just receiving them as 'holy writ'.