This one isn't actually inevitable in the near term. Lethal robots policing the streets isn't something that can just sneak up on us[0] - it's a pretty clear-cut civic issue affecting everyone, so excepting hardcore autocracies with no vertical accountability[1], the public can push such ideas back indefinitely[2].
It's hard to "agency launder" a killer robot when it's physically patrolling a public square.
--
[0] - Except maybe through privatization of law enforcement, which could be more gradual - think police outsourcing more work to private security companies, which in turn decide to "pioneer innovative solutions to ensure personal safety" by giving weapons to mall security patrol robots and putting them out on the streets - but it'll still be pretty obvious what's happening.
[1] - Some cursory search suggests this is the correct term for the idea I'm thinking of, which is how much the people in power have to, in practice, take their subjects' reactions into account.
[2] - Well, at least until armed forces of multiple countries start using autonomous robots as ground infantry, and over the years, normalize this idea in the minds of civilians.
it’s in the discovery process with a deadline of February 23rd, at which time kellogg’s is to prepare their argument and motion for summary judgement. If that’s denied it tentatively goes to 3-4 day trial in July.
I never saw them again (and I host large food truck festivals here) so I just assumed they threw in the towel. I did not know they are still operating but apparently so.
I have to imagine they’ll spend more time and money fighting this suit than they did starting the food truck. I see no reason you wouldn’t just rebrand. The name is mid at best anyway.
But also, I’m kinda rooting for them. From a distance though.
I'm guessing (NAL) that would actually make it worse. Trademark violation revolves around brand confusion. If you actually serve their product you are making that _much_ more likely (in my uninformed opinion anyway).
Otherwise it's a standalone argument about a stupid pun applied to food in general.
Tailscale is definitely not one of that crowd. Their CEO had some very reasonable takes on AI and developers on LinkedIn / their blog (linked in a sibling comment).
I recently jumped into typst for creating a course syllabus to learn programming. The experience has been great, especially compared with the LaTeX memories from grad school.
The magic moment is importing your secret key into an alternate client and all your contacts, posts, and feed populate from the data stored in the relays.
Y'all, the more I think about ATProto, the more I think it's worth considering that it may be a VERY VERY bad idea.
Which is to say, all of the potentially intrusive human information gathering and spying that you can encounter on twitter, but now cryptographically signable and EASIER to move from place to place.
Perhaps the ability of your mastodons and emails to lose your info might be just as much a feature as a bug.
Is it practical for an individual with a $4 VPS to spin up a mastadon server + front end client for their own use and have it interact with existing servers? Curious how much friction there is that users end up in on someone else's machine
Mastodon is a fairly finicky beast, has a few dependencies that you also have to manage (redis, sidekiq, Postgres), and is surprisingly resource intensive.
So you can do it, but it’s not really designed for that use case.
I would be great if there were a full-featured single user ActivityPub server, but last time I looked, there wasn’t really.
Ah makes more sense thanks. iirc mastadon doesn't have much of an identity migration story, except for using domain control as proof of identity which is kinda neat. I still like DNS and TLDs as a pay-to-play distributed namespace if you're going to have a persistent identity that can travel from server to server, and change hands as property from one owner to another. (I think there is case law on domain names being property, somewhat unique in cyberspace)
The more nerds that get sniped by a simple-seeming protocol, the more likely it is to catch on. Hitting a 100 page spec doc full of XML and links to other specs is a big de-motivator to start hacking on the protocol.
NGL that's kind of been the appeal of atproto. Once you get into the weeds you start learning about all the many many many moving parts but at its face 99% of it is:
Hey here's some schema files we call lexicons. Every single interaction with the network is a JSON RPC call to the same domain (whatever your PDS is) with the lexicon's path appended to it.
The fact that it's trivial to hack on atproto via the devtools console or a curl prompt makes things so much more fun to play with.
reply