> It's not all that different from Mastodon instances. It's a community space, and the community gets to decide who they allow to use their resources. Personally, I have a group of friends who share a GitLab instance, for example.
I think it's a bad example since your private GitLab instance wasn't all over the HN earlier screaming "are you tired of Github outages and Microslop breaking it every day? Migrate all your shit to Codeberg, the good guys of the internet" only to later pull the rug like this.
Private stuff is cool and there's place for it. Codeberg was actively positioned as an indie almost drop-in Github alternative and it's currently failing miserably at this.
Yeah, I'm not interested in a service that makes their product decisions based on the political hot button issue of the day. Was it only yesterday when they decided to ban "vibecoded" projects? Nobody in comments had a clear idea on what exactly the definition of "vibecoded" is, so half of the discussion was just confusion.
Now it's this.
I want my code hosting to host my code and only consider removing something when there's a legal demand from authorities.
Otherwise you can't be sure that the code you host peacefully today won't fall out of political activists favor tomorrow and be deleted forcing you to scramble figuring out where to move to. Fuck this.
That's not the point. The point is that the title makes it seem like the Israeli's government is spying on you, while what the article really says is that US is buying Israel's tech to spy on its own citizens.
> Nope, this is demonstrably false because Rust has its own invariants around its types and the codebase is violating a lot of them.
I'm not sure I'm following what you're saying here. In the rewrite blog post it has been stated that the Rust port landed in a place where it passes 100% of the existing test suite and does so without some of the known memory leaks of the Zig version that they were aware of and didn't know how to address.
Sure, there's no guarantee that the port didn't introduce new bugs and most likely it did, but the 1.4 version has not been released yet, so I don't think a direct comparison of a long-time "stable" version and the just-landed full rewrite is meaningfully helpful.
> "Potential memory issue" can originate in unsafe blocks and safe code that are able to alternate the input condition of these unsafe blocks. Guess what? That still counts towards 100% in this code base, hence the abomination remark.
But that just means that once you get rid of the unsafe block, you're pretty much guaranteed by the Rust compiler to be memory-safe. This means that all your potential memory landmines are annotated in the code and once you disarm them all, you're memory-safe.
I don't understand how what you're saying contradicts any of my statements.
> Not as easy as it sounds. They are like threads in a yarn ball, if there are one or two ends visible it's easier to sort them out.
Still easier than the Zig version, where all the same things you've mentioned apply, but also there's no visible indication of progress and issues are unmarked and could be pretty much anywhere.
> It's too early to declare it as anything remotely close to a win, optimistically saying.
Based on the rewrite blog post it's pretty clear that the Rust version is outperforming the Zig version by pretty much every measurable metric at this point.
I think the backlash is mostly focused on the ideological opposition to fully AI-authored 1MLOC+ PR approach they took.
The original code was one giant unsafe block with almost no tangible way to find or debug all the subtle memory bugs and leaks they had.
Now it's smaller, faster and has fewer bugs. Also its every potential memory issue is neatly annotated by an unsafe block so you can go and refactor them out one by one with confidence.
All this seems like a pretty huge improvement to me. Why is this an abomination in your eyes?
People getting emotionally attached to non-openweight models must be having it rough these days. I personally never understood the concept, but sucks to be them.
Unrelated, but, it seems that "I wrote this myself without any AI help" has firmly established itself as an excuse for shitty incoherent writing at this point.
I like the effort, but honestly there's tons of apps that are cross-platform, free, and can do everything imessages can, but better. Telegram is just one example.
I see adoption as a biggest problem. I personally tried to migrate to Telegram and failed to convince even my own wife to give it a try, since imessages work for her and all her friends are there and why bother.
Cars are a really weird choice of consumer products to paint in vantablack. All the aesthetics of rigid car body shapes are obscured and you can't really appreciate it. Not to mention how impractical such a car would be.
I totally understand that this is an artistic concept and nobody is planning to mass-produce or sell those, but still.
What I really wanna see in vantablack is clothing. I think it'd look really interesting and eye-catching.
The convenience of a car is determined by how likely you choose a car over other means when you need to get somewhere. If there's less roads, you're less likely to choose car, thus the lowering the convenience factor. If there's no roads at all, owning a car is meaningless since you can't drive anywhere, and its convenience is pretty much zero.
No, I get the necessity of deployed armed SWAT units every time there's a risk of gun violence and stuff, I don't understand why an anonymous call warrants such a response.
I wonder if there's some kind of metrics available breaking down how often an anonymous calls amount to something real vs abuse of system.
I don't understand why the police has to react to an anonymous calls the way they do in the first place.
Is there a legitimate case where you'd need to call in a SWAT team and remain anonymous at the same time? Seems like if you're legit concerned about the situation, you should have no problem proving your details that could be traced back to you. If you wish to remain anonymous, then your call should be deprioritized and so maybe they send a nearby patrolling officer to investigate the situation before sending SWAT team.
I think this is already very much prosecutable. The problem is that these calls are always anonymous and it's hard (often impossible) to track the perpetrator.
I own a pair of Bose QCII and it cuts off when I'm walking down a busy street. Also, it maintains a connection to both my phone and laptop at the same time, but I can't hear the phone before I explicitly tell headphones to disconnect from the laptop via an app.
I think it's a bad example since your private GitLab instance wasn't all over the HN earlier screaming "are you tired of Github outages and Microslop breaking it every day? Migrate all your shit to Codeberg, the good guys of the internet" only to later pull the rug like this.
Private stuff is cool and there's place for it. Codeberg was actively positioned as an indie almost drop-in Github alternative and it's currently failing miserably at this.