#dev 2025-03-28
2025-03-28 UTC
[KevinMarks], sebbu2, box464, barnaby, alephalpha0, SylvatiCodes, rrix, doesnm, bterry1 and NaomiAmethyst8 joined the channel
# 
Kolev I've been posting directly to Mastodon instead of POSSEing. 🙁
glacier and doesnm joined the channel
# 
Zegnat Next.js << [https://eduardoboucas.com/posts/2025-03-25-you-should-know-this-before-choosing-nextjs/ You should know this before choosing Next.js] - about the handling of a 9.1 out of 10 severity CVE, lock-in, and more
# 
Loqi ok, I added "[https://eduardoboucas.com/posts/2025-03-25-you-should-know-this-before-choosing-nextjs/ You should know this before choosing Next.js] - about the handling of a 9.1 out of 10 severity CVE, lock-in, and more" to the "See Also" section of /Next.js https://indieweb.org/wiki/index.php?diff=100611&oldid=88300
doesnm joined the channel; glacier left the channel
doesnm and [Murray] joined the channel
# Xe hi
# Xe oh don't worry
# Xe you're not cursing me for being a broken GPU driver, s' all good
# Xe is it intel?
# Xe because for some reason i'm quite aware that the intel GPU driver is kinda terrible
# Xe :P
# Xe oh you got the good one
# Xe i mean, it works until it doesn't
# Xe but that's par for the course with GPUs
# Xe but yes part of the main raison d'etre for anubis atm is to protect the small web
[schmarty], nemonical, ttybitnik, shoesNsocks and [manton] joined the channel
# Xe it truncates them and links to upstream
[manton] joined the channel
paotsaq joined the channel
[dave] joined the channel
# 
[artlung] (I made myself laugh by looking up the current MySpace limit). Also apparently Friendster is "back" https://friendster.com although. _Friendster Labs has no relation to or access to previous data hosted on http://friendster.com_
# [artlung] There are a few sites purporting to keep up with the limits. Though character counts in this context are very much "it depends" - how urls count, how a media upload counts against the limit, whether rich text works or not, how well multibyte characters work and whether they count against. All part of how the full stack processes stuff.
# [artlung] (one company I worked for had user messages with emojis getting eaten because of a database field that didn't allow it. the dba updated the mysql field to utf mb4 live but warned "there will be more to this" and indeed, it worked initially, but but multiple systems operated on those fields. backups and restores and replication and mimetypes and charsets and javascript libraries all needed tweaks and checks to "fix" it).
# 
[schmarty] "There will be more to this" is a good curse. Like "May you live in interesting times"
# Zegnat [artlung]: I always imagine that was why Mathias picked the pile of poo emoji for what I remember to be the main article about multibyte MySQL back in the days https://mathiasbynens.be/notes/mysql-utf8mb4
# [artlung] Developers are not systems. My experience is the developers do care. That systems have limits and have inertia California, as polyglot and multicultural a political entity as I can think of, only in the last year allows, diacritical marks, accents, and tildes on official documents for names.
# 
[tantek] There are two major problems (at least when devs are able to make decisions) : devs either (1) don't know how fragile databases are for storage, or (2) they deprioritize zero admin /longevity, or both
thegreekgeek and thegreekgeek_ joined the channel
# immibis if it's JSON-based, you can probably just add a new field for the expanded post
# immibis getting that standardized is more work, of course
# immibis All these db/encoding problems would be relatively moot if these systems relegated databases to a caching layer, not persistent storage <- then what is the persistent storage?
jonnybarnes and [snarfed] joined the channel
gRegor joined the channel
[aciccarello] joined the channel
# arekenaten I'm not really bought into the idea of the database antipattern. I understand conceptually that a DB isn't the right choice for certain implementations, but unless your use case is already well covered (e.g. Static file serving) the DB adds a standard format for dynamics.
# arekenaten Is there a similar "templating language" antipattern for when you need to adapt content dynamically. Or am I missing something?
# IWDiscord <arekenaten>
# [tantek] arekenaten, for templating there is such a broad spectrum of approaches that I don't know if any patterns have been well-identified, whether anti-* or good. There is a bunch of brainstorming also for improved approaches: https://indieweb.org/template
nemonical and nemonical1 joined the channel
# immibis S3 is a database. filesystems are databases. they're quite limited ones. why eschew the more capable database and force yourself to use the more limited one?
# immibis (performance is one reason, sometimes)
# immibis it's actually a common misconception that only SQL databases are databases databases
# immibis s/(databases) \1/\1/
# immibis things being databases has very little to do with "owning your data" and "ease of migration". database is to data as codebase is to code.
# immibis "database" is also often short for "database management system" or "database management software", such as mysql itself
# immibis postgresql or mariadb is database management software; software that is used to manage a base of data
# immibis this is the dev channel, and both SQL databases and filesystems, when used as the backend of websites, are dev-centric
# immibis the user of your website sees neither the SQL database nor the filesystem
# immibis no, i'm the primary developer. why would i need to make a website just to use it myself?
# Loqi A personal cloud is a software solution to administrate various cloud services, usually with a nice user interface, on servers you personally control https://indieweb.org/personal_cloud
# immibis so what was your point about storage vs caches (for dbs)?
# arekenaten Also just to jump in and say because something "works" doesn't make it standard. There's all sorts of tricky interop problems that come with file formats between operating systems. Until you run into one it doesn't matter, but in the niche case you do it's annoying to have to translate. Similarly to DB nuance between SQL implementations in my mind.
# arekenaten Line endings alone are enough to merit workarounds that I know of off the top of my head so I'm sure there are more.
# Zegnat I guess the interop thing is "a continuous line of bytes supposed to be parsed according to the unicode standard" ... and then it will still turn out that not everything can render all the code points to something visible. But that at least is getting better every day. (I guess then only endianess is still going to be a bother? Not sure the consortium does anything with that.)
# arekenaten Regardless, I feel like there's a whole lot of wiggle room in the "should I store everything as flat files" question. Antipattern is a strong word imo.
anon1 and gRegor joined the channel
barnaby, ttybitnik, [timothy_chambe], alephalpha0, gRegor and gRegorLove_ joined the channel