Archibald is anti-AI. 70+% of his public statements have demonstrated that.
He is more or less aligned with the current most common sentiment in the west which is largely publicly against AI.
But realistically it's just slow adaptation, network effects, etc.
To give an example, before the MLB rolled out the Automated Ball Strike system this year, last year maybe 65+% of the sentiment in discussions about it was negative or in some cases just neutral.
Now that it has rolled out, 95% of the sentiment online about ABS is positive. The main comment by far is, why didn't they do this before, and why don't they do it automatically on all pitches now.
There are certain cognitive and informational flow limitations in society that will cause this to be delayed, just like all major technological advancements.
But once it rolls out, the perspective you hear online will be about digital sovereignty/personal data autonomy, now we aren't required to send our data to an external provider for AI, why wasn't this available before. People will probably assume it was blocked because it reduced a major source of data for advertising or something.
And overall AI and robotics in the future will be seen as the greatest enabling factor for increased equality in society.
It's really just this underlying dislike of and disrespect for technology that much of the western public has. Which may turn out to be one of the reasons that we lose our de facto leadership position in the world.
You're a politician. The sentiment leans anti in this cultural context at this time and so do your statements overall, such as if we look at this one and the rest and tally each one as positive or negative. Underlying you are more anti-AI than neutral. So your reply may have been technically true but it was deliberately misleading.
But you haven't really made a technical argument because your objection is not really technical. It's a type of politics.
It's obviously extremely extremely useful to have a simple API for accessing an LLM. It needs permissions like most things and the ability to limit download sizes/specific or maybe block use of external services if desired.
But anyway people will just fall back to a slightly worse alternative like a wrapper around WebLLM (that wraps WebGPU).
It's probably not politically feasible for you to take a different stance anyway.
>To give an example, before the MLB rolled out the Automated Ball Strike system this year, last year maybe 65+% of the sentiment in discussions about it was negative or in some cases just neutral.
MLB's ABS does not use AI for its ball tracking. And it has specific payoffs particular to its context from four years of testing and wiel defined limits on use cases that don't necessarily generalize to issues surrounding AI and it's tradeoffs.
They've been slowly replacing the flip-disc displays on the buses where I live with LEDs and LCD panels which has been such a shame. There is a beautiful mechanical satisfaction to a panel of flip-discs inverting and I genuinely find them easier to read.
The old panels had diode issues. It wasn’t the mechanism failing — the simplicity of electromagnets means they last an insanely long time, significantly longer than an LED. The diodes were just cheap and undersized. If you have a stuck disc on an old board, 99% chance you just need to replace the diode. If it still flips but gets stuck on one side, a pin has gotten sticky and needs graphite applied.
The Luminator MAX 3000 is an interesting hybrid between a flip dot display and an LED display. I find it very pleasing to the eye and easy to read, particularly at night.
In front of the flip dots is a frame that has a mini-LED that faces and front-lights each flip dot. This gives the appearance that each flip dot is glowing.
Yes, even the ones that have an LED behind each disk which are on in the dark. This display [1] is the same but in the dark [2] you see the LEDs instead.
The LED / LCD displays are probably lighter (less heavy), and someone figured they can save 0.001 gallons of diesel a year fleet wide if they replace displays.
You've confabulated a reason why they replaced them, linked it to initiative then complained about them doing it all in two sentences. A gold medal in mental gymnastics is warranted here!
I use mine for all sorts. I volunteer at a second-hand shop so use it to set up remotes for donated media devices, I've used it to run scripts to apply the same changes to many computers that aren't on a group policy via BadUSB, I've used it for toys-to-life games, and very much more. There are plenty of genuine uses if you're cluey.
The interface seemed to function as normal, but specifically the API was targeted, which left a lot of confused users who were seeing the interface peppered with errors. Watching as it unfolded, it seems it affected certain regions to begin with and then slowly spread worldwide.
Seems they might have failed to host the status page (https://status.bsky.app) separately as well, because that went down several times throughout the outage. They also weren't very active in updating the status page, and the notice that was there had a typo of 'reginos' and a description of 'null'.
A valuable approach is to aim for AAA WCAG conformance. Obviously it isn't a perfect way to go about it and there are other considerations here, but at level AAA you're more likely than not ensuring an extremely clear and usable interface.
Invidious' docs recommend restarting the service regularly[1]. I can only imagine that this means there is a serious memory leak somewhere. I notice the hardware requirements specifically note: '2GB of free RAM, as long as it is restarted regularly'
I built a little Jellyfin plugin for KOReader [1] so I can access my books from my Kindle. Jellyfin proved really nice to work with (though there was some poorly documented auth stuff they were in the process of deprecating).
If anyone has been thinking of building something in the Jellyfin ecosystem, I very much recommend it.
reply