I am not 😔 If I was though I would very quickly make sure there weren't any

This is tragic for the four people who use *copilot

soulseek is so fucking bad

How wealthy do you think I am

From a safety perspective, the most accel lab (with any chance of 'winning') getting crunched for time does not seem good!

feeling doomerish about bluesky pbc abandoning a potential “communities” primitive in favor of focusing on live events.

the “feeds” primitive sucks and is undercooked. it must be a few months of work to turn it into “communities”, but it kept getting kicked down the road, and i doubt it’ll happen

Would this trick work for some H100s maybe

Fwiw I (Claude did when she set this all up. Very responsible) set my library folder to share and it doesn't seem to do anything

But the feds :(

?

That laptop fucking sucked btw. It ran Warframe somehow though. Dual core AMD APU running at like 1.2ghz max

This game was crack for me back when all I had was a shitty Toshiba Satellite laptop and no credit card to buy games on steam

Slskd is... Okay... It would be cool if I get a user that just autodenies everything it could just auto switch to someone else with the same files? Also it seems ~impossible to automate the downloads sanely. The best option I found was soulsync, which has the worst UI ever and is very slow

No this is cooler and I can have like 20tb of music everywhere

The soulseek ecosystem is so incredibly dogshit my god. Jellyseerr etc have issues but soulseek makes it feel like fucking netflix by comparison.

Claude did write all of that so

The buddy system is great

it -> modulates it into 2.4GHz radio -> transmits from your phone's antenna -> your earbuds' antenna receives it -> Bluetooth SoC demodulates and decodes -> DAC converts the digital samples into a continuous analog voltage -> tiny amplifier drives the signal into the driver -> music!

-> carrier network stack -> Android/iOS network stack -> WireGuard decrypts the Tailscale tunnel -> Subsonic client app receives the HTTP response -> decodes the Opus back to PCM -> audio framework resamples it probably unnecessarily -> Bluetooth stack picks it up -> Bluetooth codec re-encodes

ISP's network (BGP routing through who knows how many autonomous systems) -> hits a Tailscale DERP relay server -> cell tower -> your carrier's backhaul network -> more routing -> another cell tower -> radio waves -> your phone's antenna receives them -> baseband processor demodulates the signal

ethernet cable -> switch -> ethernet cable -> MikroTik router -> MikroTik processes it through its routing table and firewall rules -> WireGuard (Tailscale) encrypts and encapsulates it into UDP packets -> routes it back out -> hits the ISP router -> NAT translation -> out your uplink ->

reverse the whole path back into the Navidrome container -> Navidrome transcodes the FLAC into Opus or whatever your client requested -> chunks it into HTTP response bodies -> back out through the container networking -> through the VM networking -> through proxmox's bridge -> physical NIC ->

lookup -> forwards to TrueNAS server via NFS -> that machine's NIC receives it -> TrueNAS's kernel's network stack processes it -> NFS server daemon handles the read -> filesystem driver fetches blocks off the ZFS pool -> DMA transfers data into memory -> NFS server sends the data back ->

-> Linux VFS layer resolves the NFS mount -> NFS client constructs an RPC call -> kernel sends NFS request back out through the network stack -> out the virtual bridge -> out the proxmox bridge -> out the physical NIC -> down the ethernet cable -> hits the switch -> switch does its MAC table

iptables/nftables rules evaluate it -> Docker's virtual bridge network (docker0/br-whatever) forwards it to the Navidrome container -> container's veth pair receives it -> Navidrome's Go HTTP server parses the request -> Navidrome queries its SQLite/MySQL database -> issues a read syscall

It's crazy that this works with how complex it all is. How did we ever figure this stuff out?

Server gets request for next audio segment -> proxmox hypervisor passes the request through its virtual bridge to the
NixOS VM -> VM's virtual NIC receives it -> Linux kernel network stack processes it ->

technology is so cool. I can use tailscale to access my local navidrome on my home network from anywhere in the world to stream music, for ~free

You are not paying for API access with the subscription. You are paying for claude.ai and claude code. If you want to use other things you can pay API rate like all other third party things? I agree that it's painful but Ant is totally justified in this