Imagine a hypothetical conference about AP, a virtual CVQCon if you will, but now imagine the infrastructure. What do we need to spend money on? If we keep our commitment to open systems (and I don't see why we shouldn't), we certainly won't find ourselves paying eight dollars a head for video conferencing. The only real costs are hosting costs, a bit of sysadmin time, plus a few hundred on creative commons furry art (obviously, branding is clearly important)
I can't even begin to describe what the state of gaming on the Linux desktop is even like any more. When I started using Ubuntu back in 2005, Wine barely worked. Native commercial games were an absolute chore to get running.
Now, we're at a point where I can easily play loads of indie, retro, and AAA titles with great graphics and smooth be gameplay. My desktop plays Returnal like a PS5. My handheld can do something like 40 years worth of games, plus many current titles.
My roles right now are interesting.
- Coordinating small team of folks doing mostly technical writing and small scale web apps
- Making an open source HTTP server for proxying to p2p backends
- Coordinating a dev and myself for an HTTP API for p2p publishing with user management
- P2P database / indexing architecture consulting (managing a researcher, working with international groups)
And on top of that random fixes for Agregore when I have time.
Also got ny back touched up and boy howdy that hurts so much worse than my arm 😭 Hopefully my body doesn't reabsorb as much of the ink this time
reading Ford's "autonomous vehicles reposess themselves" patent and this is some grim, if completely expected stuff.
"Typically, the owner is uncooperative at this time and may attempt to impete the reposession operation. In some cases this can lead to confrontation. It is therefore desirable to provide a solution to address this issue."
They describe
- Escalating pressure, including disabling air conditioning/heating to "cause an additional level of discomfort to a driver and occupants of the vehicle"
- Emitting "an incessant and unpleasant sound every time the owner is present in the vehicle. The reposession system computer may also ensure that the owner is unable to turn off the sound without first making contact with the lending institution."
- Locking your car in a geofence so you can only use it to drive to work and get groceries, to not "adversely affecting a livelihood of the owner of the vehicle and hampering the owner's ability to make payments towards the vehicle."
- Yes, of course, the central component is that they want to be able to have your car drive itself to the tow lot and impound itself, but also "If the market value of the vehicle is below the pre-determined threashold price, the reposession computer may autonomously move the vehicle from the premises of the owner to a junkyard" - the logic of which is bog-typical **vile** for capitalism, they would rather it be scrapped than used by a poor person.
https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/20230055958
#AIHell #SurveillanceHell #InternetOfShit #AutonomousVehicles #CrushAllRadiosInCarsWithNeedlenosePliers
live tooting debugging: IPFS edition
Digging around some more I think it might be the #IPNS key resolution that's a bottleneck.
Right now most implementations rely on asking a bunch of DHT nodes for the "latest" record and checking them before letting the client know what CID to use. This can be super slow especially if results aren't getting cached agressively. The DHT is also generally slow with TCP connections for each request.
live tooting debugging: IPFS edition
We've got a working version of distributed.press deployed to our staging VMm but for some reason it's taking a long time to load anything (usually the first load times out). And gateways are having trouble loading published data at all.
My initial thought was that this was a firewall thing where incoming connections aren't happening.
After tweaking IPTables rules I'm not sure. Gotta get better logs.
Don't like strangers busting into your mentions to give unsolicited opinions?
This could be solved if the Fediverse had better comment controls.
You should be able to make a read-only post if you want.
And you should be able to make a public post that's only writeable to followers.
You should also be able to lock a thread if it becomes a vector for abuse.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.