I use either aom for trying to make "optimized" encodes of things to get quality at the smallest file size or svt for fast encodes that aren't really any more efficient than h265, just with the better codec.
I just transcoded some movies with vmaf of 98% from 4k hdr blurays this last week. Takes about two days of mostly single core work with cpu-used=4 on a 5950x but they get average bitrates of around 4400 kbps. Which is like, really, really good for hitting that quality target.
The trick is that since its mostly single core I just do 16 movies at a time, or 24 on my server.
It feels like newfound indignity and the realization is that most of us are actually victims - capitalist exploitation of the working class is codified into the societies we live in, it just took people taking a break from the grind, a step back to see what they were subjected to, to realize what the exploitation is and what it feels like.
Its not popular on HN but most of the libertarian tenants that belay picking yourself up by your bootstraps are not applicable to a supermajority of labor. There is no change of attitude within the framing of the economic system as it exists that individual actors take on a collective scale to suddenly stop being exploited systemically.
If XMPP and Matrix were based on the same protocol stack arguments to keeping XMPP this whole time would have made sense.
But they aren't. Matrix is http and json while XMPP is tcp and xml. Protocol extensions to xmpp have added http transports - but thats just wrapping non-http requests in http and making processing harder.
I think a good comparison is X11 vs Wayland. X11 was retrofitted with all the functionality Wayland has natively - "why switch" is a legitimate question. But we will see in the next 20-30 years how the maintenance burden of X protocol legacy means we will see any new development using Wayland because its so much easier to do. In the same sense, chat apps will probably favor Matrix over XMPP because of the protocol maintenance burden - even when drop in libraries exist that implement XMPP, the inherent complexity makes them buggier, slower, and requires a lot of developer nuance to get right and its all due to legacy cruft you have to accommodate on an old standard.
Its also like how more modern kernels stopped trying to be Unix compatible. Trying to meet the POSIX standard in the 21st century is kinda a waste of effort when a lot of it is unnecessary. The model is sound, its just adhering strictly to the eccentricities of it is just unnecessary headache.
I was impressed at how easy it is to work with the matrix protocol. While playing around I was doing it all interactively in bash using curl. Want to read the latest messages? Curl the sync url. Want to send a new message? Post a small json object.
It’s actually easier to use by hand than IRC which requires holding an open connection and quickly responding to pings.
It becomes a little harder when end to end encryption is on but you just import the library they supply for almost every language and then e2e becomes transparent.
I've tried to set up some Matrix projects. The Client-Server API is easy to work with, but as soon as encryption is involved, things start getting messy. Many libraries have a hard time working right with E2EE enabled, because suddenly you need to keep track of all manner of things that aren't always documented well.
I tried to hack E2EE in by using Pantalaimon [0] but running that on a server with the necessary management capabilities is very tricky and doesn't do cross signing, so I've come to the conclusion that it's effectively useless for my use cases.
Every now and then I check back on the current state of E2EE in libraries and it does seem to be improving. Hopefully the entire process becomes easier next time I get the time to work on my proof of concept code.
> I was impressed at how easy it is to work with the matrix protocol
I think you were interacting with Synapse, the Matrix homeserver implementation, which is why you had an easy time. But I can't imagine the work done by Synapse to sync up with other servers is easy - and that's what I would consider the real protocol.
There are two protocols. The Server-Server protocol, and the Client-Server protocol. Both are "real". I was using the Client-Server protocol which synapse implements but other servers would implement exactly the same HTTP protocol.
Its still really convenient. It is really starting to pick up - I can use my phone to pay fares in a lot of metros now, have real time transit tracking, and use it for navigation even when walking.
Its definitely, imo, to the point where it is becoming a responsibility of societies to provide its citizens access to these technologies because of their utility. That means subsidized / free phones and service, imo. Everyone really should have a baseline of digital access as a fundamental right, hopefully this decade. The COVID relief free cell service in the US I think has been an eye opener for me.
Portland like mentioned about European cities and towns is also incredibly homogenous culturally and racially by most American standards . Lived there for 6 years as a brown person and glad to have gotten out.
I definitely think doing openid logins is way easier than any home rolled auth scheme.
Delegate responsibility where you can, which includes use authentication. It sucks that Persona died all those years ago because web browsers really could use an identity system for users to authenticate themselves against sites with their browser accounts.
The problem is then ofc getting browsers to cooperatively allow cross sign in. If messengers are anything to go by, siloed products really do not want to interoperate, particularly I imagine Edge and Safari.
You can use GPL code commercially. You just have to publish source on anything it touches. It that makes your business model nonviable, the amount of good you were doing is... questionable.
I disagree with "have to publish source on anything it touches" . Electronic Arts used WebKit in multiple games and they only had to share changes they did to it, not the source codes for all their games.
As a side effect they had to publish their incomplete implementation of STL that was adopted by multiple other studios as it was so much faster and less memory fragmenting than alternatives.
WebKit is LGPL though, not GPL, and it was built as a specially maintained dynamic library specifically to avoid having to publish the source code for the whole game.
Have you ever actually had someone on medicare navigate healthcare?
Its only partial coverage and the supplemental plans also are partial. Retirees regularly rake up thousands a year in medical expenses on medicare.
If anything we need medicaid for all. Its a total mess with the piecemeal systems that exist, but in PA at least (where I live) medicaid recipients pay like a dollar for basically any service. None of the copay nickle and diming (to the tune of $30 a pop) my grandmother is hounded with constantly.
And even that is a bitter pill. Its giving private insurance companies all the money and power still. The single payer has strong negotiating power but they still have to get someone to insure the citizenry and the cartel of insurers that exist can predate off that and do so eagerly.
Medicare For All is not just an extension of the existing Medicare. It expands it to everyone and fixes some of those holes. Medicaid would still be there for services outside MFA like senior long term care.
Unfortunately Matrix still has the issue of key sharing between clients. If you want to read previously sent messages when you log into a new client for the first time you have to do the key sharing dance with one of your existing clients.
For me it's a little annoying, but I find it an acceptable tradeoff. However I could easily see how for many people this would be a dealbreaker.
Key backup makes this a lot easier, assuming you've saved the recovery key in your password manager. But it's still one of those frustrating points where it defeats the purpose of the exercise for the provider to be able to recover an account (or at least the content and trust within an account) for someone who's locked out.
Its intentional sabotage by Apple at this point on behalf of MPEG-LA, it seems.