interesting. while annoying it seemed to help

Voyager seems to be OK after upgrade, Eternity however spits 404 errors on upvotes etc

can someone enlighten me what prompted those threats?

self-hosting is great but that still means datacenter someplace. I’ve been using GitLab for some time now and CodeBerg “feels weird” to me. But then it could be my biases and “muscle memory”. I’d say whatever feels right for you.

Unlike other big name Git hosting company who chose to use AI to “steal” from hosted projects other two did not stoop that low. So there’s that.

funny thing is: “Eternity” looks like it shows totals for my upvotes on posts/comments but not showing what those are

thanks for the tech details. It sucks that there’s no endpoint for upvotes (yet). I find favorites/saved and upvoted to be distinctly different at least the way I use it. Upvotes communicate to me (and others) that content is of value or that I agree with it. However Saved/Favorite may mean that I disagree with content but I’d like to keep reference for future times. That latter is a private info too so nobody benefits from me “saving” that content other than myself.

TLDR; I’d have to get used to hitting upvote and “save” buttons on content of interest and learn to filter through my “saved” stuff while devs are comming up with endpoints for upvotes.

thank you for such a detailed response. I would love to contribute however at the moment my capacities are rather limited but otherwise I’d be willing to add sqlite adapter. From your description it sounds like currently architecture is narrowly locked on PostgreSQL features. In my daily job I love PostgreSQL for big apps and stacks but I’m also aware how “hungry” PG can be, which is why I’m wondering whether it’s “too big of a hammer” for this particular problem. Also, setting up single service is easier to novices vs maintaining several. Docker compose is nice but it has it’s limitations.

@mgdigital, first thing I’be noticed: reliance on “heavier” database stack (pg + redis), at least from the first glance at docker-compose. My suggestion would be to have an option for minimalist setup with sqlite and without redis if possible. That would work better for those of us flying with minimal hardware (rpi, old PC and such).