Ah you’re right, I had assumed since it was a humbucker the two rows would be aligned straight, but now I see the coils are in line with the strings as they should be. Fascinating guitar OP. Nice work.
Ah, yes coil split makes sense. But doesn’t the angle screw with the humbucker when it’s in HB mode? I’ve always heard humbuckers shouldn’t be angled.
I’m curious why you went with the (reversed?) angle on the bridge humbucker pickup? I’ve never seen anything like it.
Ah I just noticed it’s a lefty. But yeah, why the angled humbucker?
What they really mean is: Polite to them, the people with the means of easily inflicting deadly violence upon others.
Gun ownership is just another expression of the deep selfishness ingrained in American culture.
It sometimes seems like there’s nothing good in this country congress won’t eventually destroy. The USPS was, and is, mostly an excellent organization. Only sabotage will bring it down.
The cruelty is the point.
“Practical Engineering” is a fantastic channel. I especially appreciate all the infrastructure failure analysis videos he has done. It let me (a non civil engineer) understand why certain infrastructure disasters like collapses, power outages, or dam breaches were able to occur.
Their first album indubitably is my favorite, obviously.
Most of the Koopa kids were named after musicians
Someone should tell Retsuko about this kind of service.
Not sure how unpopular it is, but “The Settlers 2: 10th Anniversary” is a great remaster of a game which I think is a bit forgotten now. It’s still a really fun and charming citybuilder with unique mechanics.
YunoHost “packages” are just scripts. In the case of Lemmy, Lemmy_ynh’s install script actually fetches the Lemmy Docker image and extracts the files (including pre-built binaries) from it. And then it writes the config files to use the system Psql instance instead of a containerized version.
FWIW I don’t care how YunoHost installs the apps. Whether it’s fetching and running containers, or building from source, or grabbing binaries. As long as the apps work and the reverse proxy gets wrangled it’s fine with me. Just in this case refusing to run the Docker images directly is, at least momentarily, a problem for updating the app.
Well it is “working” for me. I’m using a YunoHost Lemmy 0.16.7 to type this comment :). But I agree there should be some kind of warning on the project that it’s only really partially working, and very outdated (thanks to the recent flurry in activity and changes).
Mainly though I wish YunoHost would just support Docker idiomatically and install Lemmy “as intended”. Yeah Docker can be a bit of a pain and it uses more resources, but it also has many real advantages like siloing the apps from the host system…
Were you able to migrate your database from an outdated YunoHost installation to a v18 Lemmy running in Docker? I like YunoHost but I’m considering the same move, as this old Lemmy version has a lot of incompatibilities and other issues.
The main blocker, at least so far, was Lemmy is designed mainly to use use Docker containers to version itself and its main dependencies like Postgresql, while YunoHost runs on the bare system. And since YunoHost is still on Debian 11 it only has access to Postgresql 13 while Lemmy now wants 15. This unfortunately is hard to resolve. YunoHost doesn’t want to introduce Docker, and upgrading the entire platform to Debian 12 is slowly happening but it’s a lot of work.
“No one” in the US perhaps. Customers look down on retail workers, and feel free to abuse them, because they are so economically disempowered. A nation which pays retail workers a fair wage is also a nation where retail workers are treated (somewhat) better.
Because what Twitter really needs right now is less engagement.
If they really do shut off API access I’ll go into partial link aggregator withdrawal. My Lemmy instance still isn’t upgraded to the latest versions which are compatible with apps, so I don’t browse on my phone.
But do we need some kind of SSO layer with DID verification? All I need to prove my identity anywhere, technically, is my private+public keypair. As long as I hold on to this keypair, distribute it between apps/computers, back it up, I could log in anywhere on a federated platform and use it.
I hope we’re going to see key-based decentralized identity on ActivityPub at some point… Having accounts tied to instances is just not very robust or scalable.