Comment on Plebbit Will Never Deliver, Apologies for the Hype, Lemmy's Where I’m Staying

usescomputer@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

• rinse@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  posts would be markdown files

  Seedit, which is a plebbit client actually parses posts as Markdown, try it on Seedit

  images would only be allowed as links to an image hosting platform It’s already this way with Plebbit, we only allow text.

  Having it be open source and every member with a fork (I don’t know if there’s a way to auto update forks) so we don’t risk losing everything if the host shuts down (I don’t use mastodon because apparently you can’t export posts)

  On Plebbit all clients are open source with GPL V2, they can also be self hosted easily with a single click. Check out seedit repository Seedit

  source
• sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

  I really don’t think that would scale at all. A reasonably popular community could have tons of simultaneous posts, and if everyone needs to sync before posting, that would suck. You could probably avoid the worst of it by having posts use uuids, but you’re going to have IO issues at scale. Also, would you need the full repo cloned? That can get big, and you generally only care about recent posts.

  Also, if you’re doing the UUID thing, you’d have sort everything every time locally. That’s fine if you only have a few thousand posts, but if you get into millions or billions, it’ll get bad, especially if you’re dealing with files.

  Databases solve these problems really well. Even a simple SQLite dB would be much better than a filesystem, like orders of magnitude better.

  source

  • usescomputer@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

    Agreed, I didn’t it through much, I just really like markdown

    source

    • sugar_in_your_tea@sh.itjust.works ⁨3⁩ ⁨weeks⁩ ago

      Yeah, Markdown is pretty rad, and most of these Reddit alternatives use it. I’m working on my own and Markdown is definitely what I’m using.

      source