HackerTrans
トップ新着トレンドコメント過去質問紹介求人

ummonk

no profile record

投稿

[untitled]

1 ポイント·投稿者 ummonk·6 か月前·0 コメント

India orders Musk's X to fix Grok over 'obscene' AI content

techcrunch.com
11 ポイント·投稿者 ummonk·6 か月前·1 コメント

India's Biggest Airline Falls into Chaos, Canceling More Than 1k Flights

nytimes.com
2 ポイント·投稿者 ummonk·7 か月前·1 コメント

This Week's AWS Crash Made Smart Beds Overheat, Get Stuck in Wrong Position

pcmag.com
1 ポイント·投稿者 ummonk·9 か月前·1 コメント

Robin Williams' daughter begs fans to stop sending her AI videos of late father

the-independent.com
2 ポイント·投稿者 ummonk·9 か月前·1 コメント

Why Language Models Hallucinate

arxiv.org
1 ポイント·投稿者 ummonk·10 か月前·0 コメント

Hulu Glitch Blocks Customers from Canceling or Making Changes to Their Accounts

cordcuttersnews.com
1 ポイント·投稿者 ummonk·10 か月前·5 コメント

コメント

ummonk
·25 日前·議論
I don’t follow. Are you under the misapprehension that ears was referring to auditory perception, rather than vestibular sense of motion?
ummonk
·先月·議論
You just press backspace and hit the accent mark key or for a printing press stack the accent mark on top of the letter. People ditched accents because they were rarely used in English writing (only really being used for some loanwords), not because simplifications were forced by typewriters or the printing press (which handle non-English languages just fine).
ummonk
·先月·議論
Protp-Sinaitic was an abjad not an alphabet.
ummonk
·先月·議論
"This is why Hebrew's alphabet near-perfectly phonetically represents the spoken language" - nonsense. That's just because modern Hebrew is based on the written language and thus reflects spelling pronunciation rather than historical pronunciation.

Also, proto-Sinaitic is not an alphabet. That's why Persian writing became harder to read when they switched from the nearly alphabetic Old Persian cuneiform to Aramaic abjad descended from proto-Sinaitic.
ummonk
·先月·議論
Yeah and we've already seen this with Facebook getting blamed for Cambridge Analytica.
ummonk
·先月·議論
It sounds more like this was a predefined account recovery flow, rather than some LLM agent making use of arbitrary write access.
ummonk
·先月·議論
If someone is talking about "spinning up a separate machine" for Postgres, they're not talking about a desktop or mobile app...
ummonk
·先月·議論
Why go through the trouble of shoehorning SQLite into a cloud database by getting solutions for HA/failover and DR, when you can just use Postgres off the shelf?
ummonk
·先月·議論
My argument is that they would add an exception for TSMC in the event that Taiwan fell under Chinese control. The alternative would be an extreme supply shock to the industry that's responsible for most stock market and GDP growth in America.
ummonk
·先月·議論
Wouldn't the rest of the world encourage ASML to keep supporting the fab because they want the chips to keep coming?
ummonk
·2 か月前·議論
Interesting project in general. I wonder whether it could be adapted to behave reasonably without relying on threading. E.g. run the GC only when *alloc is called.
ummonk
·2 か月前·議論
I mean they brought that incident on themselves...
ummonk
·3 か月前·議論
That factor was downstream of its complexity though. It's far harder to implement a compiler for Ada 83 than even for modern C.
ummonk
·3 か月前·議論
What's a situation where one needs to use `eval` in benign way in JS? If something is precomputable (e.g. `eval("1 + 1")` can just be replaced by 2), then it should be precomputed. If it's not precomputable then it's dependent on input and thus hardly benign -- you'll need to carefully verify that the inputs are properly sanitized.
ummonk
·3 か月前·議論
I don't see why the transformer architecture can't be designed and trained with separate inputs for control data and content data.
ummonk
·4 か月前·議論
Great stuff.

I would argue that hardened mode should be default though, similar to how siphash is the default hashing function in Rust hash maps. Faster mode should be opt in if the user is confident that the supplied data is nonmalicious and they need the speed up.
ummonk
·4 か月前·議論
That's Rule 5 no?
ummonk
·4 か月前·議論
The boilerplate and indirection isn't done for performance
ummonk
·4 か月前·議論
I've worked on optimizing modern slow code. Once you optimize a few bottlenecks it turns out it's very hard to optimize because the rest of the time is spread out over the whole code without any small bottlenecks and it's all written in a slow language with no thought for performance.
ummonk
·4 か月前·議論
I would argue that making the company experience the consequences of its choice of metrics / mandates is in fact a moral imperative.