Instead of dynamically lowering models based on volume, throttle compute speed! I would rather wait longer for the right answer, than have a faster wrong one! I'm about to cancel my subscriptions over this!
The notion that companies are blocking AI agents from interacting with them reminds me of the API wars of the early 2000's. That, and streaming services. "Cord cutting" is just as expensive now, if not more, than cable was. We are seeing the economic results for the streaming providers now.
Poop on your opponents in this chess variant, where pigeons have 1 square more range than knights. Pooped on pieces can be captured by any adjacent piece regardless of how it normally moves. chess.peer.ooo/pigeon @iwantcheckmate
Built on PeerPigeon using freertc (cloud+local) federated relays .. I plan to focus more on PeerPigeon since freertc is in much better shape now
chess.peer.ooo
Learned a fun limit of using a free tier tonight 🤣🤣
Docker showed it to me, wurl will fix it going forward...
Hmmm Docker is still pretty resource expensive. I think I will look into adapting curl to work with webrtc. I'll call it wurl
BAM
What I'm currently experimenting with/testing:
nat hole-punched freertc relay servers with cloudflare service worker coordination and cross-relay federation for peers.
This will let you easily deploy a cloudflare freertc relay via service worker, which serves as fallback for connecting peers on the mesh, and a local freertc relay server. Then peer A on cloudflare worker relay 1 can reach peer Z on freertc relay N regardless of which domain it began with.
Once I can do this, I am ready to test 1000 (containerized) peers on my MacBook Pro. Then I'll test as many as each machine can support (air, mini, iMac 1 & 2) on 3 different networks.
What I'm currently experimenting with/testing:
nat hole-punched freertc relay servers with cloudflare service worker coordination and cross-relay federation for peers.
This will let you easily deploy a cloudflare freertc relay via service worker, which serves as fallback for connecting peers on the mesh, and a local freertc relay server. Then peer A on cloudflare worker relay 1 can reach peer Z on freertc relay N regardless of which domain it began with.
Once I can do this, I am ready to test 1000 (containerized) peers on my MacBook Pro. Then I'll test as many as each machine can support (air, mini, iMac 1 & 2) on 3 different networks.
Several decades later, still no way to easily see/set a meeting reminder. WTF @Microsoft
Waiting for a package to show up...
Alexa: <notification noise>
Me: Alexa, what's my notification
Alexa: From Amazon Shopping. I found you savings on ...
😡😡😡😡😡😡😡😡😡😡😡😡
Keto English muffins are an excellent personal pizza crust, and Mexican chihuahua cheese is way better than mozzarella.
That is all.