Home | Notifications | New Note | Local | Federated | Search | Logout

Greg Slepak@taoeffect@crib.social

@okturtles - @groupincome - @espionage

Homepage: https://fixingtao.com
X: https://x.com/taoeffect
Keybase: greg
Joined: 2026-03-30 03:28:34
6 notes, 0 following, 0 followers

Reply to @silverpill@mitra.social
Greg Slepak@taoeffect@crib.social (2026-04-23 07:46:43)
@silverpill Why implement a totally separate project for this btw? Why not add nomadic identities to Mitra?

Reply to @taoeffect@crib.social
Greg Slepak@taoeffect@crib.social (2026-04-02 04:55:58)
@silverpill Does mitra not suffer from this? @phnt was saying in the issue:Yes, this is a problem for any database running on PostgreSQL that is constantly being written to. Database growing in size and database bloat are unavoidable facts of running a database.

Reply to @taoeffect@crib.social
Greg Slepak@taoeffect@crib.social (2026-04-02 03:08:53)
Here are the hoops I have to jump through: https://git.pleroma.social/pleroma/pleroma/issues/2338#issuecomment-115204

Greg Slepak@taoeffect@crib.social (2026-04-02 01:18:26)
I definitely don't recommend #pleroma. The database just keeps growing and figuring out how to keep it manageable is a huge hassle.

Fediverse instances should never require manual database admin.

Reply to @silverpill@mitra.social
Greg Slepak@taoeffect@crib.social (2026-03-30 07:10:58)
@silverpill Awesome! Would be awesome if you could update the README with details on which ones thos are!

Reply to @silverpill@mitra.social
Greg Slepak@taoeffect@crib.social (2026-03-30 02:42:01)
@silverpill cool! What is this useful for that mitra and other things aren't good for?