GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Rich Felker (dalias@hachyderm.io)'s status on Thursday, 11-Sep-2025 22:12:51 JST Rich Felker Rich Felker
    in reply to
    • Ben Zanin
    • Eniko Fox

    @eniko @gnomon I'm not by any means discouraging you to go for this, but on top of that, anyone with such a server really needs proper frequent backups. It probably also makes sense to ensure whatever system you pick is compatible with making incremental backups so they can be done continuously rather than at long intervals.

    In conversation about 5 months ago from hachyderm.io permalink
    • Embed this notice
      Eniko Fox (eniko@mastodon.gamedev.place)'s status on Thursday, 11-Sep-2025 22:12:53 JST Eniko Fox Eniko Fox
      in reply to
      • Ben Zanin

      @gnomon yeah, this is why i extremely don't want to reinvent this particular wheel. acid compliance is extremely finicky in the details and just as hard to get right and i just don't have the time to do a proper job of that

      and i don't want to be the cause of a community server's save file going corrupt after people collectively put in a 1000 hours of play

      In conversation about 5 months ago permalink
    • Embed this notice
      Ben Zanin (gnomon@mastodon.social)'s status on Thursday, 11-Sep-2025 22:12:54 JST Ben Zanin Ben Zanin
      in reply to
      • Dan Luu
      • Eniko Fox

      @eniko those articles by @danluu lay out how difficult it is for filesystems to get robustness guarantees correct while maintaining performance, and as kind of a footnote they also mention how sqlite3 works so hard so maintain robustness that it can sometimes eclipse the guarantees of the underlying filesystem - that is, its coping strategies can be more effective than the FS implementation. (Which feels counterintuitive at first, but makes sense after some pondering.)

      2/2

      In conversation about 5 months ago permalink
    • Embed this notice
      Ben Zanin (gnomon@mastodon.social)'s status on Thursday, 11-Sep-2025 22:12:55 JST Ben Zanin Ben Zanin
      in reply to
      • Eniko Fox

      @eniko oh hello and welcome to the sqlite3 fan club

      edit: OK, no, sorry, I can be helpful instead of flippant. Beg your pardon there.

      Sqlite3 does offer ACID compliance, but its key value proposition is that it does so with minimal additional complexity. The use case it tries to fill is making it easier to be ACID-compliant than to not be: https://www.sqlite.org/whentouse.html#:~:text=Sqlite%20does%20not,fopen%28%29

      And by golly it has succeeded wildly, cf.:

      https://danluu.com/file-consistency/

      https://danluu.com/deconstruct-files/#:~:text=except%20for%20sqlite,at%20least%20one%20bug

      1/2

      In conversation about 5 months ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Appropriate Uses For SQLite
    • Embed this notice
      Eniko Fox (eniko@mastodon.gamedev.place)'s status on Thursday, 11-Sep-2025 22:12:56 JST Eniko Fox Eniko Fox

      hey fedi programmer folks, this isn't urgent but i'm going to have to store my block game's world data in some kind of acid compliant database at some point. do you have any recommendations? it must be a file-based database, obviously. and game data doesn't usually neatly conform to the boring numbered rows with named columns table design of traditional databases for websites and stuff

      i think ideally i'd just be able to store raw binary data

      In conversation about 5 months ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.