cross-posted from: lemmy.zip/post/34733394
Snac (AKA Snac2) is a minimal microblogging ActivityPub instance written in C.
Features (from its Codeberg repo):
- Lightweight, minimal dependencies
- Extensive support of ActivityPub operations, e.g. write public notes, follow users, be followed, reply to the notes of others, admire wonderful content (like or boost), write private messages…
- Multiuser
- Mastodon API support, so Mastodon-compatible apps can be used
- Simple but effective web interface
- Easily-accessed MUTE button to silence morons
- Tested interoperability with related software
- No database needed
- Totally JavaScript-free
- No cookies either
- Not much bullshit
atzanteol@sh.itjust.works 5 weeks ago
Bonkers that anyone would start a social media app in C in 2025. “No JavaScript” but you’re just one buffer overflow from arbitrary code execution.
sugoidogo@discuss.online 4 weeks ago
C is also faster than JavaScript, uses less memory, and memory safety isn’t impossible in C either. I wouldn’t consider a scripting language to even be a choice for writing a backend server if I can use a compiled language instead.
atzanteol@sh.itjust.works 4 weeks ago
In practice it is.
Neat.
jewbies@lemmynsfw.com 4 weeks ago
Id just like to point out that there is no such thing as “compiled” languages. The compiler or interpretor is the implementation of the spec. Did you know that there are interpreted versions of c?
eutampieri@feddit.it 4 weeks ago
I’m a rust fan, but may I remind you that the Linux kernel is mostly C?
56_@lemmy.ml 4 weeks ago
I feel like snac is social media made specifically for people who like C though. I’m sure most users of it are well aware of the implications.
z3r0_Geek@lemmy.zip 5 weeks ago
How is that?
atzanteol@sh.itjust.works 4 weeks ago
C is a “memory unsafe” language. There are whole categories of security vulnerabilities that simply aren’t possible in memory-safe languages that C allows. There is no good reason to continue using C anymore for new projects if you care at all about security.
www.cisa.gov/…/product-security-bad-practices