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?
Max is probably right but that doesn't make Spa (my favorite track!) "safe". Two deaths in 4 years is very unusual for modern motor racing. Something needs to be done with Raidillon, like automatic instant yellow flags whenever a car leaves the track.
Or maybe a speed limit through Raidillon in the rain makes sense.
Meest Nederlandse nieuws titel die ik in lange tijd heb gelezen
Aren't there potential cost savings in running two teams? It seems lettings owners run two teams could help put more cars on the grid without making the sport even more expensive. I really don't know if this is the case but it seems like it could be a factor.
Having used both, while the market implications of NACS are still unclear it sure is the more ergonomic of the two standards. Those CCS2 DC connectors are just too large and unwieldy.
Hey Stux!
Yeah YunoHost is extremely awesome. I use it to host my Mastodon and Lemmy instances. It’s just a little unfortunate that until Debian 12 is supported, their supported Lemmy version is stuck at 0.16.7. So if you want to set up an Lemmy instance today YunoHost might not be ideal.
Hopefully they can get Debian 12 and latest Lemmy support working without any roadblocks.
There’s many different ways DID could be implemented on top of ActivityPub. I don’t think full content replication (what you’re mentioning) is likely as that’s a fundamentally different style of protocol.
But I can imagine signing in to a different instance with my ID, at which point I subscribe to all my communities from this instance and get notifications if someone replies to one of my comments etc. Just as if I had created an account on this instance and had posted from there. It just means “your” instance can go down and you can continue future interactions mostly uninterrupted from another instance.
And it’s more useful in the case of microblogging, where with DID you can publish posts from any instance and your followers will see them. No need for a manual account migration or anything.
Huh. Guess I won't be using Uber's apps then. Anytime I'm a paying customer I do not want to see ads shoved in my face. Good thing there's competition.
Both Breath of the Wild and Tears of the Kingdom have fantastic sound design. The environmental sounds of wind, water, trees and wildlife accompanied by that understated soundtrack makes you feel out in the wilds even though the graphics are minimal.
Sadly, I feel like the Fediverse, based on ActivityPub, was fundamentally designed wrong for scaling potential. I do like Fedi and I like ActivityPub, but I think instances should not have to be responsible for all of this:
- Owning user accounts
- Exclusively host communities
- Serving local and remote users webpages and media
- Never going down, as this results in users and content becoming unavailable
Because servers "own" the user accounts and communities it's not trivial for users to switch to a different instance, and as instances scale their costs go up slightly exponentially.
I wish the Fediverse from the beginning was a truly distributed content replication platform, usenet-style or Matrix-style, and every instance would add additional capacity to the network instead of hosting specific communities or users.
I guess it's a bit too late for a redesign now... Perhaps decentralized identifiers will take us there in some form in the future.
anji
0 post score0 comment score
The Song Remains the Same