(webdev Tory) @worldsendless@qoto.org

@avandeursen Those HN discussions are excellent! Many of them point to the problem of comparing it to modern Twitter, which has some excuses for its code size. I would point out what may be outside many developers awareness: the fact that we are talking about it, and that there is also a case to be made in defense (whether that case prevails or not), means that the title is a success, in the "click-bait" sense. It leading to such great discussions is extremely valuable. I also love the comment that points out that re-investigating the common architecture is valuable.

@mmisamore admittedly I haven't done much with metadata, but if you data is being persisted, wouldn't a clear solution to be to insert a "validated?" value on to the data, so that instead of checking for the ABSENCE of something, you are checking for the presence of it? This feels idiomatic to me, given the additive nature of lisp in general (eg the REPL)

@ericsfraga @freemo

Great tip! Does it break reverse compatibility?

@nickanderson The strange thing is the added external concept of "node" as opposed to the regular linking of the actual files on your disk.

@freemo

@freemo that would be the typical non-attachment simple link. With attachments, a randomly named directory is created adjacent, and the filename is encoded/nomalized. Then the org file gets an `attachment`key added which includes said generated encoding.

I guess the benefit is that it is independent of the original file which could be trashed, modified, or deleted. But the indirect refactoring is a little strange.

#emacs #orgmode #attachment #files are really cool; they can allow me, eg, to attach the wav file of that crazy voicemail from my son to my journal entry for the day. The moment you do that, however, you are introducing application lock-in to your org file; future readings of the plain text cannot recover that attachment unless they are using orgmode, likewise git. I am probably still going to do it, though. But this is annoying.

@pglpm@emacs.ch and emms integrates beautifully with #direh, already one of emacs #KillerApp

@petereisentraut @mkaatman not reserved in postgres... My install begs to disagree

@pglpm@emacs.ch emms makes it so quick

@petereisentraut @mkaatman I think the problem is shown here https://www.postgresql.org/docs/current/sql-keywords-appendix.html

@mkaatman no kidding. It's been three years since we designed the database, largely copying structure from a 15-year old MYSQL one, and because the domain needs billing addresses, we never stopped to think about the CS context. It seems that the newest Postgres versions have breaking changes in their handling of that word now.

ugh. It appears that #Postgres 15 changed the #ReservedKeywords, too, so I have project-wide issues needing a maybe-complex refactor of the word "state." Yeah, that one should have been obvious, but for years it worked for our US-serving program. It's Friday, and I'm sad.

Apparently I did an "upgrade all", as is recommended, and it bumped my #PostGresDB to 15, which has breaking changes. And this, my friends, is why upgrades are bad. https://stackoverflow.com/questions/74110708/postgres-15-permission-denied-for-schema-public

You know, playing #music in #emacs is surprisingly good. I thought it was janky and cumbersome at first, but the ability to pause, play, manipulate the audio and have integration with my whole system, including podcasts, is nice. Hence the recent thoughts about the old-fashioned solutions that predate DRM (should I be using Napster?)

@freemo @BenAveling @Elleaster @ErikUden

I suspect I disagree with @freemo on guns and policy, but I support the call for good-faith argument and legitimate discussion. I am not prepared to have that discussion right now, but I really enjoyed seeing the call for it.

I've found my old CD #music collection and have been ripping them. Serious question: is online (Spotify, Pandora, etc) more shareable than having the digital files on your machine?

Found it: `guix install opus-tools` which includes opusenc, which was the command I need for abcde to rip my audio to opus.

struggling to figure out how to encode #audio as #opus on #guix