Generated by AI.
Use 1secmail API without giving any credit.
False advertisment.
Readit Newsnpn commented on Show HN: Mephisto – A RAM-only, ad-free disposable email PWA built with React mephistomail.site... · Posted by u/benmxrt
npn commented on The Tor Project is switching to Rust itsfoss.com/news/tor-rust... · Posted by u/giuliomagnifico
I'm sure replacing the battle-tested C implementation with a Rust implementation that's extremely vulnerable to supply-chain attacks and has seen little real-world usage is not going to backfire at all.
It is intended. Like any other US gov funded projects.
npn commented on The Tor Project is switching to Rust itsfoss.com/news/tor-rust... · Posted by u/giuliomagnifico
Is this the version where all adult content safety guards dropped? No wonder they bump the price, the demand spike will be huge.
npn commented on Bikeshedding, or why I want to build a laptop geohot.github.io//blog/je... · Posted by u/cspags
Is his build even possible today in a laptop?
In a desktop, you would need a top of the line threadripper for that 256GB/s of memory bandwidth.
Consumer grade Zen 5 desktops reach only about 80GB/s in real world testing, with a theoretical max of slightly over 100GB/s.
Yes. OneXfly apex. Amd 395+, oled panel.
I say this as someone who has been cautioning about Microsoft's ownership of GitHub for years now... but the Zig community has been high drama lately. I thought the Rust community had done themselves a disservice with their high tolerance of drama, but lately Zig seems to me to be more drama than even Rust.
I was saddened to see how they ganged up to bully the author of the Zig book. The book author, as far as I could tell, seems like a possibly immature teenager. But to have a whole community gang up on you with pitch forks because they have a suspicion you might use AI... that was gross to watch.
I was already turned off by the constant Zig spam approach to marketing. But now that we're getting pitchfork mobs and ranty anti-AI diatribes it just seems like a community sustaining itself on negative energy. I think they can possibly still turn it around but it might involve cleaning house or instituting better rules for contributors.
> turned off by the constant Zig spam approach to marketing
? what? from my experience zig marketing is pretty mid. it is nowhere at the level of rust.
heck, rust evangelism strikeforce made me hate rust and all the people promote it, even for now.
npn commented on Do not put your site behind Cloudflare if you don't need to huijzer.xyz/posts/123/do-... · Posted by u/huijzer
Traditional non-cloud, non-weird DNS providers have sufficiently long TTLs, not the "60 seconds and then it's broken" crap that clouds do to facilitate some of their services.
Something like TTL 86400 gets you over a lot of outages just because all the caches will still have your entries.
Only for you use case. I use cloudflare for my dynamic ip dns, caching that long make it worthless.
npn commented on Gemini 3 Pro Model Card [pdf] storage.googleapis.com/de... · Posted by u/virgildotcodes
My impression is that Grok is very rarely used in practice outside of a niche of die-hard users, partly because of very different tuning to other models, and partly the related public reputation around it.
https://firstpagesage.com/reports/top-generative-ai-chatbots... suggests 0.6% of chat use cases, well below the other big names, and I suspect those stats for chat are higher than other scenarios like business usage. Given all that, I can see how Gemini might not be focused on competing with them.
well, there are 3 kind of usages for grok:
- using grok inside X/Twitter: most people interacts with Grok this way.
- using grok on its website: this is really annoying, as you get delayed by cloudflare everytime you access the site. As grok does not provide serious advantage over other services, why bother
- you can also use the app, but it is not as convenient as other services.
it is understandable that grok is not popular.
> The good parts
posts before 2015~2016. that's it.
> the build time is over 30 seconds!
that's silly. 30 seconds building time is nothing compare to the accumulated time you wait for micro changes to your frontend.
for typical web development using react/vue/svelte you have hot code reloading, which can reload the current website < 1 seconds after you hit [Save] on your favorite editor.
for htmx to update, you have to wait for your whole server to reload (which can be way slower even you use interpreted languages like ruby or python, due to complexity of the framework you use).
not to mention it does not keep any state of the current website, make debugging way more troublesome compare to a js mature framework.
only people who never have to improve their website incrementally think htmx is a viable option. or insane people.
obviously, for some small websites with minimal interactions or no need to change the content very often, then htmx can be good, but for that case, vanilla js also works, and they do not need 14kb of excess baggage.