Conversation

Notices

1. Embed this notice
   Kit Rhett Aultman (roadriverrail@signs.codes)'s status on Thursday, 31-Oct-2024 00:26:31 JST Kit Rhett Aultman

   in reply to

   • DJ Sundog - from the toot-lab

   @djsundog It all depends on what mode of access you're looking for, what flexibility in access you want, and what scale you're talking about. RDBMS took off in enterprise largely on the back of how they enabled extreme flexibility in their queries. If you don't mind having to co-design the data store and the way it's used, then you don't *need* RDBMS, but it can certainly help enable a more rapid development process too.

   • Embed this notice
     DJ Sundog - from the toot-lab (djsundog@toot-lab.reclaim.technology)'s status on Thursday, 31-Oct-2024 00:26:32 JST DJ Sundog - from the toot-lab

     in reply to

     I did a toy implementation of an activitypub server at one point a long while back that just used the filesystem as a database and honestly I don't remember why I stopped pursuing that, though I believe there are a couple of other similar implementations at this point.

     like, maybe we don't need third normal form relational data for our various stream of consciousness shitposts and rant threads?

   • Embed this notice
     DJ Sundog - from the toot-lab (djsundog@toot-lab.reclaim.technology)'s status on Thursday, 31-Oct-2024 00:26:33 JST DJ Sundog - from the toot-lab

     activitypub server that "freezes" posts made locally after a configurable interval (say, six months by default, or some such), removing them from the database and making the posts non-interactive, but rendering the frozen posts in html and json as flat files on disk, with a small script to check for authorization on a get request that passes the flat file through if authorization is successful, but not recording new favs, replies, boosts, etc, and returning a well-specified error response whenever a remote actor attempts to do so.