Spent way too long last night trying to get

Spent way too long last night trying to get #Sway set up on my #PineTab2 because:

1. The Arch dependencies for some of the optional components were broken (wmenu requires dmenu, but the package didn’t say so).
2. The Arch documentation for Sway is out of date and sends you to AUR for just about everything.
3. The documents I found didn’t make it clear that key bindings are the only way to launch things unless you explicitly add some other kind of launcher that’s not in the sample config. Or what to expect when changing the menu config. Or what the menus are supposed to look like.
4. Because of the broken dependencies, even when I tried to use the keybinds, they failed silently. For a while I wasn’t even sure it was reading my config file.

And now I’m like…why did I go to all that trouble? All I wanted was to make sure I had all the prerequisites to run a basic Wayland session on something lighter than Plasma. I’m just going to switch back to LXQt.

I miss the days when #Linux seemed to actually run deterministically. When I could see what was breaking easily and fix it easily.

I don’t miss all the extra fiddling and trial and error just to get something functional.

Sure, I like tinkering. When I want to. I don’t like to have to.

Tried to POSSE a recent photo

Tried to POSSE a recent photo post on my blog to Bluesky and Flickr signage using the Syndication Links plugin and its built-in support for brid.gy.

It failed to reach Flickr because it went through as a note rather than a photo, and the Bluesky autopost only included the title and raw URL…and the URL wasn’t clickable.

For Flickr, it could just be that I didn’t include the u-photo class on the image.

I’m going to add that and retry.

And then take a look at whether it’s the plugin or the service that’s setting the content.

(next day)

Looks like I exceeded the retry limits or something. I’ll try again with my next photo post. And try to remember to check some logs tonight.

My new standalone @gotosocial@superseriousbusiness.org server is set up, and I’m getting ready to migrate over to @kelson@not…

My new standalone @gotosocial server is set up, and I’m getting ready to migrate over to @kelson

This one (keysmash.xyz) will stick around for a bit while I look through bookmarks and boosts and old posts. If I read the docs correctly, I should be able to mark this account as moved and still be able to go through my archives afterward.



“Taco Bell Programming” – sometimes you can just use different combinations of the same few Unix tools in a 10-line shell sc…

“Taco Bell Programming” – sometimes you can just use different combinations of the same few Unix tools in a 10-line shell script instead of building super complicated distributed apps with the lastest tech stack.

#programming #unix


GoToSocial Migration Plan

#GoToSocial hasn’t hit beta yet, but it has implemented support for migrating followers to new accounts. So I think I’m ready to set up my new Fediverse main on something like notes.kvibber.com. Weekend plans!

I’m not going to delete my Wandering.shop account, but I’ll probably mark it as moved. And I think I’ll keep this Snac2 server for now, for techie spitballing like this post.

As for my current GTS test server, I’ll keep running it for a while in parallel. But eventually I’ll be turning it off.

Maybe I’ll re-boost and re-post some things before I publicize the new account so it’s sorta backfilled without spamming anyone’s feeds. Though anything of mine that I actually want to re-post is probably better moved to my website.

Oh right, need to revisit compatibility.

It looks like I should be able to follow a #Lemmy user or community from #GoToSocial now that authorized fetch is implemented, but it doesn’t seem to be working, at least not from my server.

And it still can’t follow my #Postmarks server, but that’s almost certainly in part due to the Mastodon-specific hardcoded assumptions: https://github.com/ckolderup/postmarks/issues/77

I’ll have to gather some debug logs in GTS and Postmarks, see if I need to fix my config to talk to Lemmy, and then figure out which projects I need to post the debug log to.

And try out some possible code fixes on my own server to see if they work. Or at least get a new error.

Otherwise it seems to federate just fine with most of the other server types I use and/or have tried to follow.

I’ve been running this on a Raspberry Pi 3b for a

I’ve been running this on a Raspberry Pi 3b for a couple of years now — it was easier to install than Plex, doesn’t try to upsell me to a subscription when I listen to my own locally-hosted library, and runs fine over the LAN. The Jellyfin desktop apps work pretty well on Mac, Windows and Linux.

I only use it for audio, not video, so I don’t know if the Pi 3b and its relatively slow processor and network throughput would be enough to handle video. I reviewed it on my website a while back in case anyone’s interested: https://hyperborea.org/reviews/software/jellyfin/


And the most basic: Don’t park in the charging space…

And the most basic: Don’t park in the charging space if you’re not going to charge your car. Even if your car is electric.

I can’t count the number of times I’ve had to look for another charger because someone had parked in front of one without even plugging in.

Even if they had been charging earlier…if you can unplug it when you’re done, you can move the car too.

Helix Comics

comment left at Comics Worth Reading’s post, The Helix Titles That Live On; Time Breakers Crowdfunding

Interesting: I think Sheva’s War and The Dome: Ground Zero were the only ones I picked up at the time. I might even still have Sheva’s War in a box somewhere, though I don’t remember anything at all about The Dome.

I read Michael Moorcock’s Multiverse as a TPB, but I’m not sure what imprint it was by that time. Transmet, of course, I discovered after it moved to Vertigo.

Of the rest, only Cyberella rings a bell, but when I read about the Time Breakers collection, I immediately thought 2 things: “Why didn’t I notice this when it was new?” And “I have to buy it now!”

In retrospect, it’s weird to me that I skipped most of the Helix line. But I think I was still mostly reading superhero comics at the time.

I’m experimenting on my tech tips articles with

I’m experimenting on my tech tips articles with #ShareOpenly, a web app that acts as an intermediate layer between sites that want a share button and newer social media sites like #Mastodon instances.

The author describes it here: https://werd.io/2024/share-openly.

1. The publisher links to Share Openly with the URL and title or description of the page to share.
2. The reader clicks on it and tells SO what site they want to share on (pre-filled or type in a hostname, with the manually added ones remembered).
3. SO opens that site’s post form with the text pre-filled and ready to go.

It knows where to find the posting forms for several kinds of server software, and you can add a <link rel="share_url".../> template to your site to tell it where to look. I may do this for my Postmarks site.

But not everything has a post form that can be pre-filled. Heck, not everything has a front-end to begin with. So I can’t just put that link tag on my #GoToSocial instance and point to the post form, because there isn’t one. And it doesn’t look like Elk or Semaphore have a way to pre-fill a post either.

sigh Sometimes I really wish #WebIntents had taken off.

Anyway, here’s an article on my site with “Share This Page” linking to the webapp

I keep meaning to try out the LXQt+Wayland combo o

I keep meaning to try out the LXQt+Wayland combo on the PineTab2 (LXQt is so much faster than KDE on this thing), and I keep not getting around to it. Sounds like the 2.0 release will be a good time to try it.


It sounds like most of the remaining pieces have alternatives or workarounds.

Oh yeah… I’d forgotten about that. sigh

Oh yeah… I’d forgotten about that. sigh — I can only imagine Amazon was hoping to promote their store and Microsoft was trying to avoid sending more money to Google, and neither of them realized they’d be mutual albatrosses for it.

Apparently people have been able to run F-droid on it, though!

I don’t doubt the physics

I don’t doubt the physics of getting people there. Or at least objects with comparable mass to people.

I doubt he has anything resembling a workable plan for keeping large numbers of people alive for long periods of time on Mars.

Relevant: https://www.acityonmars.com/ looks into a lot of the engineering, biological, economic, social, political and legal issues involved in actually trying to build a settlement with actual people on another planet. And the recurring theme, over and over as they talked to experts in each field, was that the research is either too early or too sparse to be usable yet (or in some cases, just not being done).

(My review of the book: https://hyperborea.org/reviews/books/city-on-mars/ )

I think we might have had an Itanium box at Unitech

I think we might have had an Itanium box at Unitech, but then we had something like 15-20 various HP, Sun and other commercial Unix systems running different OS versions for building and QA. Though the IBM PowerPC was the last major box we added. Generally we all developed on Windows and would telnet into whatever arch/OS combo we needed. I do remember we had “the Vista box” and a couple other Windows workstations that were shared on an as-needed basis, and if we did have an Itanium, it would have been one of those.

Virtualization makes things so much easier!