Forum Federato

Okay, a Doom-like written in…SQL?

https://cedardb.com/blog/doomql/

my brain hurts.

@neil shouldn't be a particularly big deal. I have repos on multiple machines, and you can set multiple push URLs so with one `git push` from your dev machine, it gets pushed to all the repos in one go.

@joel

I'd considered making a mini CLI-oriented podcast but this concern was part of why I have very little audio of my voice online.

@stefano

reading over @Edent's recent post¹ about the conflict between giving users control over their own devices vs locking down phones to a blessed app-store, a piece of me wants to make app-permission-granting exceptionally onerous.
▁▁▁▁▁▁▁▁▁▁▁▁▁
Allow this application:
⎺̲) to edit SMS or MMS messages
⎺̲) to read SMS or MMS messages
⎺̲) to receive SMS messages
(⎺̲ to know your coarse (network-based) location
⎺̲) to know your fine (GPS-based) location
to create Bluetooth connections
⎺̲) full internet access
⎺̲) to modify/delete SD card contents
⎺̲) to make phone calls
⎺̲) to answer phone calls
[Okay] [Cancel]
▔▔▔▔▔▔▔▔▔▔▔▔▔
Would it suck to install an application that requires permission overreach because you'd have to manually grant every requested permission? You betcha. Would it make devs have to think about how much pain they want to inflict on possible users? One would hope.

But frankly, I'd love to have this level of permission-granularity at install time. You're a freakin' barcode management application for my library cards. You don't need to access my files or to make internet connections or overlay on other running applications. You just need to show the barcode on the screen, adjust screen-brightness, and possibly use the camera to scan existing barcodes. (not that I have particularly bitter experiences with barcode apps in particular)

⸻
¹ https://shkspr.mobi/blog/2025/08/is-it-possible-to-allow-sideloading-and-keep-users-safe/

@stefano lovely picture of you two! Glad you're getting to enjoy rejuvinative time together!

Beware of this git(1) gotcha:

If you do

$ git log --oneline file.txt

you'll get your list of commits on file.txt. If you

$ git log --oneline -1 file.txt

you'll get just the first (most recent) one.

If you reverse your initial output

$ git log --oneline --reverse file.txt

you get things in the opposite order. But if you want the first one of those (the oldest modification of the file), you can't use -1 like

$ git log --oneline --reverse -1 file.txt

because as the man-page says, "Note that these [filtering criteria like `-1`] are applied **before** commit ordering and formatting options, such as --reverse" [emphasis mine]

So instead you need to use

$ git log --oneline --reverse file.txt | head -1

"I didn't see myself going up to 3 VPS instances"

But here were are, @elena …

That said, I'm thankful you keep us apprised of your adventures because they're sure fun to follow!

@elena whoops, meant to do a Reply, but apparently just did a raw post without replying 🤪

https://mastodon.bsd.cafe/@gumnos/115056136697247596