progbits
Joined 5 years ago
Joined 5 years ago
2. JXL is waaay more complex than Brotli so the risk of vulnerable implementation is also higher.
They should have demanded more rigor from the Brotli library, same for countless other dependencies chromium has. But there's no irony.
Source: enterprise cloud customer, it's broken all the time.
There is GHES onprem which indeed doesn't get affected by these outages, but it's shit.
https://us.githubstatus.com/posts/details/P7VGB7I
https://au.githubstatus.com/posts/details/PO54BK8
https://eu.githubstatus.com/posts/details/PRESCZY
https://jp.githubstatus.com/posts/details/P0N7ZG5
What's the point of (supposedly) separate and isolated data residency deployments if they all have single point of failure?
You can actually split the road into multiple segments and answer each separately if you don't mind the extra effort. I think there should be something like "differs along the way" button which then asks you to pick a point where to cut.
Imagine a photo with some blacked out rectangles, and a ZK proof that confirms it comes from an attested "real" photo + adding those rectangles, but no other modification.
Right... Except the whole thing being generated by a model derived from everyone's code.
I'm not even sure I'm against licensing it as MIT but maybe stop with the ridiculous claims on top of that?
This one is great for filling in some of the gaps in official docs.
https://quantum.cloud.ibm.com/computers?system=ibm_phoenix
Does this mean they literally have a single one? (Or at least a single one they offer publicly)
I've been slowly trying to stop my spotify usage and replace it with owned audio files.
Mostly I try to use Bandcamp but many artists are not there. Sometimes I just rip the audio from youtube but would prefer a way to buy that gives most of the money to the artist.
Seems like you put a lot of thought and effort into it which is awesome, so the LLM readme was ruining first impressions. It's a shame but given the explosion in low effort projects it's important to stand out I think.
I'm willing to use (semi-)vibecoded projects under certain circumstances, but I like to know up front what I'm getting. The github contributors list makes that easy to see as long as people don't try to hide it.
Reasoning: inaccessible to HN users. OP should find another source or mirror.
Contact info: Don't.