Zach "earboxer" DeCook @zachdecook@librem.one

New #LEGO build: a plugin for my #olkb #planck keyboard-case to hold a #pinephone (or any smartphone).

I would say it works well, but TBH it needs a counterweight to be a usable lap-top device.

Actually, updating #nextcloud to #postgresql on #alpine was pretty easy
1. php occ db:convert-type pgsql nextcloud localhost nextcloud
2. (Disable some apps until that command worked)
3. ssh $OLD_SERVER pg_dump nextcloud | psql nextcloud
4. rsync data dir onto new server
5. Mess around with some config stuff
6. Update https://wiki.alpinelinux.org/wiki/Nextcloud wiki page to be slightly more up-to-date

Watched #freeGuy last night: the movie about an #NPC going off-script against a massive studio... maybe I should get (back?) into #gamedev. I don't play many single-player games, as coding is just more fun.

Migrating a #laravel site to #postgresql from mysql/mariadb

1. Run migrations to create db structure
2. Remove single quotes from the database (and newlines/control characters, because why not). This allows mysqldump files to be imported into postgresql.
3. mysqldump --compatible=postgres --no-create-info --skip-add-locks $DB | psql $DB
4. Fix increments `ALTER sequence song_id_seq RESTART 12345;` (current versions of laravel use old-fashioned postgres increments)

I thought a fun thing to do would be to switch my main VPS to #alpinelinux for more frequent updates (compared to ubuntu). (I run #nextcloud, a custom #laravel site, and some other simpler stuff) So far, I've started using #linode, and also have been learning that migrating from mysql/mariadb to #postgresql may have been too ambitious an idea.

Hey fediverse! I'm called Zach, and yes, I love technology. Started coding as a kid writing #nds games using #PAlib, got into programming #microcontrollers. Spent several years doing #fullstack web development and some #devOps, looking to expand my skills and gain new experience.

Technology should (at least) do one thing well, and (necessarily) be there when you need it.

#introduction

anyone have an idea how #phosh could be modified to fade out the currently running app, so we could see our wallpaper?

#postmarketostweaks background setting gave performance issues, so I'm thinking this approach will be better.
So far, I have

*{background-color:unset}

in gtk.css

I needed to `sudo modprobe uinput`. This is really promising, I bet someone running #sxmo would be able to get it running faster because that supports splitscreen and #phosh doesn't.

I tried out #node-virtual-gamepads (https://github.com/jehervy/node-virtual-gamepads
).

#ioctl syscall crashes with #ENOTTY after I select 'gamepad'.

but we'll call this 'promising'. probably will be easier to add #gamepad support to #uxnemu than to try to wade through the levels of complexity to get #squeekboard to behave nicer under #SDL (it tells me unknown keyboard layout sometimes at compile)

With the recent talk about #gamepad support for some big #uxn apps, I wonder if there are any soft-gamepads that could work with #varvara #uxnemu on a #mobileLinux device.

Any leads?

apparently it's also important to delete the old records... and also that the new records are correct.

Installed a new home router, and I guess it decided to get us a new IP address, so my gemini capsule is down while the new A record propagates.

today I added a script to my #gemini capsule to allow me to add to my /bookmarks.gmi file *using gemini*.

Seems like some of the browser experience could be done out in geminispace itself... less requirement for client authors, though that means more things "in the cloud".

. @wholesomedonut wants to see technology as it is: "a miraculous, marvelous invention whose original intents have long been uprooted by a society full of greed and indifference"
gemini://soviet.circumlunar.space/wholesomedonut/gemlog/my-return-to-tech-exile.gmi
I hope you're able to get free from the vitriol and set your mind on higher things. (Unfollowing negative accounts helps, but maybe taking a break from the fediverse would be best).

starting to try to compile #organicMaps on a raspberry pi zero... it's armhf, so if the problem (running it on the pinephone) is architecture based, this will likely also fail.

Which got me thinking more about #usfm2gmi:
If I were to make a #bible gem-app, what feature options would be desired?
Would any of the following be useful, and how should they look in #gemtext?
* notes (currently in square brackets)
* cross-references (currently in parentheses)
* word references (I experimented once with putting Strong's references in superscript)
* red-lettering (ideologically, I disagree with this)
* section titles
* chapter divisions
* verse numbers