Cross-compiling doesn't work because you're not defining your dependencies correctly and relying on the existence of things like system libraries and libc. Use `zig cc` with Go which will let you compile against a stub Glibc, or go all the way and use a hermetic build system (you should do this always anyhow).
For the GC it sounds like they don’t have generations which means copying long-lived objects needlessly due to the generational hypothesis. Interesting idea with the mailbox allocator, but how do these two allocators interact? Is the heap non-regional, or are they allocating into separate regions?
But they only collect tiny actors spaces, no big consecutive heaps as usual. Anyway, you can always add a minor collection later, and benchmark it. She didn't write it, a friend did.
I would very much like for him not to ignore the negativity, given that, you know, they are breaking the entire fucking Internet every time something like this happens.
This is the kind of comment I wish he would ignore.
You can be angry - but that doesn't help anyone.
They fucked up, yes, they admitted it and they provided plans on how to address that.
I don't think they do these things on purpose. Of course given their good market penetration they end up disrupting a lot of customers - and they should focus on slow rollouts - but I also believe that in a DDOS protection system (or WAF) you don't want or have the luxury to wait for days until your rule is applied.
I hope he doesn't ignore it, the internet has been forgiving enough toward cloudflares string of failures..its getting pretty old, and creates a ton of choas. I work with life saving devices, being impacted in any way in data monitoring has a huge impact in many ways. "sorry ma'am we can't give your child t1d readings on your follow app because our provider decided to break everything in the pursuit of some react bug." has a great ring to it
Cloudflare and other cloud infra providers are only providing primitives to use, in this case WAF. They have target uptimes and it's never 100%. It's up to the people actually making end user services (like your medical devices) to judge whether that is enough and if not to design your service around it.
(and also, rolling your own version of WAF is probably not the right answer if you need better uptime. It's exceedingly unlikely a medical devices company will beat CF at this game.)
Most hospital and healthcare IT teams are extremely under funded, undertrained, overworked, and the software, configurations and platforms are normally not the most resilient things.
I have a friend at one in the North East right now going through a hell of a security breach for multiple months now and I'm flabbergasted no one is dead yet.
When it comes to tech, I get the impression most organizations are not very "healthy" in the durability of systems.
Rogue browser extensions are very rare these days. When people get redirected to malicious sites, it's almost always either due to the site having an infected WordPress installation or using a sketchy ad network.
>When people get redirected to malicious sites, it's almost always either due to the site having an infected WordPress installation or using a sketchy ad network.
That's often true. However, in this case when visiting the linked page[0] I am able to connect and view the article without issue.
Some details:
Location: USA
Browser: Firefox 128.14.0esr
Ublock Origin running with mostly default settings
Perhaps there's a location blocking issue and/or malware that targets certain locations/browser types?
A lot of claims about being "privacy first", but is there any way to actually verify these claims? For example they claim "no logs", but unless I log into their servers and personally check there is no way I can be sure, right? Is there something I'm missing?
They have shared IP address information before [1]. They have also shared information about the owner of a Proton Mail account with the FBI before.
In my opinion, Proton glows. If you're a nobody, they will protect your privacy, but if you matter then it seems they won't stand up for you. I still use Proton, but it's mostly for registering on sites for which I don't want to burn a Gmail account. I wouldn't do anything sketchy on it.
> They have shared IP address information before [1]. They have also shared information about the owner of a Proton Mail account with the FBI before.
Any other mail provider can, and most certainly has, done the same thing when forced by a court order.
No one is going to go to prison for you because of your $5.
> In my opinion, Proton glows. If you're a nobody, they will protect your privacy, but if you matter then it seems they won't stand up for you.
How does this differ from any other SaaS service? Unless you specifically target "bulletproof" services, that are oftentimes blocked anyway due to facilitating fraud, scams, and other illegal tranactions (since the whole point is them not obeying the law while operating, until they inevitability get shut down).
They've been audited by external organizations and had at least one legal request for log information where court was satisfied they couldn't comply due to their no log policy.
reply