Nah, they're always going to have a free tier, that's how they get you hooked to their service. It might be even ad-supported in the future (watch an ad to earn credits, or by inserting sponsored content in the responses).
Plus the free tier gives them loads of new training data. I do agree we will see two types of adverts soon: Traditional and submarine (paid-placement).
In many cases "AI" signals some sort of betrayal to users, because it shows that the developer CAN drastically change the GUI to implement features it wants to implement, except in practice "AI" isn't a feature that provides tangible benefits to the user.
So you get the feeling of "you could have done this this WHOLE time?" + the fact they didn't do it for you but just to say they are using AI now.
If the developer wanted to please the users, they would instead implement features that users have been demanding for a while. That got a lower priority so that AI that nobody asked for could be implemented.
>The model is built via a merge of https://huggingface.co/nex-agi/Nex-N2-Pro and https://huggingface.co/Qwen/Qwen3.5-397B-A17B, proceeded by On-Policy Distillation from a stronger model. We detected an incorrect upload in the previous version, where the base merged version was upload instead of the final distilled model. We are sorry for the confusion and apologize profusely.
Incidentally are people using Github issues as blogs now?
Edit: I didnt even notice until someone pointed out this was on the Nex-n2 repo not the rio one, now I understand the OP’s confusion!
It wasnt framed as an issue which is the norm breakage I think you’re reacting to, as in they didnt ask that the readme be updated etc, but it is common now for folks to use a project’s issue tracker to name and shame them in a place they cant easily ignore.
Whether that’s right, prosocial, or professional is up for debate (as well as if any single definition of etiquette can be expected in 2026 on an issue tracker).
But surely you can see the optics reason why someone would take their complaint to the repo directly? It pressures the maintainers to respond, it allows for a pile on from the internet, and makes any decision to lock down a hostile thread into its own kind of statement.
The maintainers should absolutely post an official response and lock the thread though, it will likely get ugly in there.
The best case scenario of LLM is transforming input into output where both are languages and accuracy doesn't matter, e.g. "rewrite this poem in pirate speech."
Does "publication" refer to the software or to something documenting the existence of the bug? Because I thought zero-day meant the bug was exploited the same day the software containing the bug was released, but your phrasing sounds like if you exploit a bug before the maintainers know about it then it's a negative day.
Zig raises overflow. There are +|= and +%= operators for clamped and wrapping addition.
Rust doesn't raise overflow by default. But you can just 123.checked_add(321). Now your code is unreadable, but it's overflow safe.
Honestly, based on the way I write code I'd rather something like an end of line comment. Like:
var x = y + z; # wrapped
Because I'm very unlikely to mix wrapped/checked/clamped arithmetic in a single line. It can't be a compiler state like doing(wrapped) { x + y } because in Zig every line must be "compilable" by itself, without requiring context from other parts of the code. Function names are too verbose. Casting is too verbose. Having a statement-level modifier would be a good compromise.
Agreed, the option that sacrifices security in search of performance should be the more verbose one. There's a reason Rust doesn't have `safe {}` blocks and there's a reason it chose immutable-by-default semantics.
>They may be trying to vilify Yoti, they may be farming karma, they may be trying to discourage people from using GrapheneOS
I don't understand why you draw that conclusion. Based on:
>The OP of this reddit post has a lot of other posts (now hidden) about age verification, bypassing it, and privacy. They even got called out about this in the reddit thread and responded by hiding their profile
That just sounds like a privacy-conscious person doing things privacy-conscious people would do.
What if they aren't faking the e-mails, and it's Yoti who is lying? Then it's just a privacy-conscious person.
What if neither is lying? The e-mail was sent, but this was never recorded on Yoti's customer support records, or the record was deleted? Do we know what kind of customer support system Yoti is running? What if there was a bug or hardware failure? What if someone saw it being deleted but they figured it's better for them if they didn't say anything, so Yoti isn't aware of its own internal cover up?
What if PalDuck was actually paid by Yoti to publish a fake e-mail screenshot as part of a PR campaign? What if the screenshot is real, but it comes from a different timeline and Yoti did nothing wrong in this timeline?
With this "he said she said" situation, considering nobody is going to open an investigation over a reddit post, I think we might have more fun speculating about time-travelling screenshots. We'll never know the truth either way.
It's been a while since I last used IRC, but afaik one of the issues with it was that servers revealed the IP address of users to every other user by default. Since the IP is geographic that's one piece of information you could use to doxx someone.
IP addresses aren't linked to a complete street address, and many times don't even show the right town, especially those on CG-NAT or a plain ol' direct public dynamic address. I have seen some IPs, like on AT&T and Comcast home Internet, showing a different state.
So in many cases, you don't need a VPN to prevent revealing your actual geographic location.
The fact that this is needed at all is a serious problem. Making people who aren't aware of some obscure details accidentally doxx themselves is incredibly user-hostile.
