Not even a year. May as well hook the nix org up to a steam generator to make use of all the human resources they burn thru.
Reminds me of those old disruption tactics for occupied territories: drag everything through committees, micromanage and obstruct, make everyone's work just that much little bit harder than it needs to be...
It's doubly tough because I can see where a lot of people are coming from on some issues, but others feel like they shouldn't be issues at all. Mostly just a systemic failure, as they said. Good communication is hard to accomplish: boundaries and expectations and all that; even harder when the framework and environment works against you.
Sad to hear of more churn. Wishing them (and their future replacements) much good luck.
The real government waste isn't the social, research, or effective* environmental programs. It's the bloated loopholed taxcode, the MIC, the revolving doors, the thousand dollar trashcans, the no-bid contracts, the croissant-like layers of middlemen, the labyrinthine beauroccracy of means-testing that costs more than it saves, and the reluctance to directly employ and retain skilled labor for public projects.
Poor black brown and gay people aren't ruining your country. Monied interests are, and they're using you to do it. (dems also but not the subject of this post)
Step 1) attack a sovereign country 2) get your ass kicked non-stop for years 3) cry about it and blame the US for making you do it.
And 4) every other day: act like you have a reason to go to war with the US and rattle the saber.
Fine. You wanna fight the US so bad? Sure, why not. Do it. Bomb them coward. Years and years and years of Russian bullshit warmongering. Just get on with it.
Unencrypted by default (among other bad defaults), leaks metadata like it was built to do so, makes it surprisingly difficult to tell what's encrypted and what's not, filled to the brim with bugs and exploits, bad feature interop between most clients (most of which have known vulnerabilities or abandoned dependencies), defacto-standard "just use synapse/element if you want things to work properly" (and still doesn't), bad user communication about well everything but mainly teaching new users what all the things mean (session, verification, 1:1 vs jitsi, when you're using what,...), ton of federation issues and bugs, ...
And despite all that it somehow has a massive csam seeding problem, which really just makes me think the whole thing is a telegram-like fed psyop but one level higher on the tech competency ladder.
... Multi-device session chaining is a neat feature and surprisingly user-friendly (tho no one maintains their session list or verification; half pebkac admittedly), so that's something nice I can say about it... But almost nothing else.
Seriously, Signal is basically a joint three-letter-agency sigint project and I still think it's safer and easier to use than matrix for the vast vast vast majority of people
So youre suggesting they secretly have Einstein standing in the server rack, making loud fan noises with his mouth and just typing really fast?
Either the problems were solved or they weren't. If they were, then that's evidence enough; doesn't matter if they model isn't publicly available.
Having those sudden breakthroughs come from a person or even a large group of mathematicians, suddenly and all at once, would be more surprising than a well-harnessed LLM figuring it out.
With that said, I'm curious about peer review of the actual proofs. Just because Lean builds them doesn't mean they're materially valid. It could very well be that it's completely wrong and it just hallucinated well enough to fool OpenAI into publishing it, which would be a hilarious egg-on-face moment
As someone who uses matrix and runs a matrix server, matrix fucking suuuucks jfc why are so many privacy tools soooooo bad at what they do on so many levels like wtf the proto the servers the clients the ux the metadata issues like so much wrong
Edit: and if anyone tells me to use XMPP I'll slap them
I recently made a lua framework that constructs callable tables to be used as functions that take a table as a dictionary of named argument. The function declares a schema of parameters with associated required/default/optional policies that put their respective values through a transform and validation pipeline. A similar pipeline can also be put on the result to make explicit guarantees. Can also configure whether argument errors/violations should throw or return results,error shape
The wrapped function recieves a table of processed arguments in a known state, while keeping that noise separate from the business logic. Also configurable at runtime with introspection, and param pipelines are immutable so they can be composed.
If that sounds like it introduces a lot of overhead, you're right! But 1) it's Lua and 2) omg is it so worth it when used properly. The UX is great; the callsite ergonomics, maintainability, and self-documenting nature is always what I felt was missing. Ships with & plays pretty well with type annotations too.
Anyways, that all makes it really convenient to know what's responsible for what, and encourages pretty safe designs.
I look forward to playing it for free.