Discussion
Loading...

Discussion

Log in
  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
nelson
nelson
@nelson@shrimp.starlightnet.work  ·  activity timestamp 2 weeks ago

My main (and truly only issue) with #snac is it's overreliance on filesystem operations. it's very cool from a purely unix kind of standpoint where you can see the elegance of such a design, but in practice, it's just way too much overhead

Having it operate with sqlite instead, as a baseline, would already make it much more efficient than it is

I do like that people are engineering stuff like this though, having the entire program be a self contained repository of readable C, that implements the basic features of mastodon, is kind of dope!

  • Copy link
  • Flag this post
  • Block
Jack
Jack
@knapjack@gruntle.cc replied  ·  activity timestamp 2 weeks ago
@nelson@starlightnet.work A similarly-small service, #honk, was originally built on sqlite and eventually flipped over to using the filesystem as the default. Ted Unangst's domain is down, so can't research (or recall) why the change was made.
  • Copy link
  • Flag this comment
  • Block
khm
khm
@khm@hj.9fs.net replied  ·  activity timestamp 2 weeks ago

snac is already the most efficient fully-featured activitypub implementation I've ever seen; seems like a hat on a hat

besides, it makes incremental backups stupid simple (I am a big fan of stupid simple)

  • Copy link
  • Flag this comment
  • Block

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.2-alpha.7 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Members
  • Code of Conduct