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

nomercy400

no profile record

コメント

nomercy400
·4 か月前·議論
Can I do the reverse now as well? Email a company a unilateral change in the TOS? Or do TOS's have provisions against that as well?

"I do not agree with your new TOS and will continue under your old TOS, and I will continue to use your service". And see when they will close your account down.
nomercy400
·4 か月前·議論
Yes, this is simply 'technical debt'.

They should try to fix technical debt before going to the next round. Of course Claude can probably also do this.
nomercy400
·4 か月前·議論
I was taught years ago that MUL and ADD can be implemented in one or a few cycles. They can be the same complexity. What am I missing here?

Also, is it possible to use the GPU's ADD/MUL implementation? It is what a GPU does best.
nomercy400
·5 か月前·議論
ASML is not a chip maker, it is a chip-maker maker. Still important though.

Europe should request a discount for ASML machines in a EU factory.
nomercy400
·5 か月前·議論
Yes exactly.

Where the map does not represent the actual venue. Where every route leads to the gift shop. Where some displays are only in English. Where the flow between the rooms is non-intuitive. Where the audio guide is too loud/quiet and you cannot adjust the volume, or pause it during an item. Where there are mind-your-head bars in the way for no reason.
nomercy400
·5 か月前·議論
That also sounds like the client came with list of additional requirements.

The ethical part you mentioned is still true.
nomercy400
·5 か月前·議論
That's about an extra iPhone every 3-4 years.
nomercy400
·5 か月前·議論
I wrote my comment without knowing about the moltbook thing. I somehow missed it.

Good to know it exists.
nomercy400
·5 か月前·議論
How long until we have agents talking to other agents in a web of agents, and together deciding on something catastrophic? Not individually, but somehow the result of a group process.
nomercy400
·5 か月前·議論
You might as well place it next to the © 2026, on the bottom every page.
nomercy400
·5 か月前·議論
From what I understand, sentry.io is like a tracing and logging service, used by many organizations.

This helps you (=NAS developer) to centralize logs and trace a request through all your application layers (client->server->db and back), so you can identify performance bottlenecks and measure usage patterns.

This is what you can find behind the 'anonymized diagnostics' and 'telemetry' settings you are asked to enable/consent.

For a WebUI it is implemented via javascript, which runs on the client's machine and hooks into the clicks, API calls and page content. It then sends statistics and logs back to, in this case, sentry.io. Your browser just sees javascript, so don't blame them. Privacy Badger might block it.

It is as nefarious as the developer of the application wants to use it. Normally you would use it to centralize logging, find performance issues, and get a basic idea on what features users actually use, so you can debug more easily. But you can also use it to track users. And don't forget, sentry.io is a cloud solution. If you post it on machines outside your control, expect it to be public. Sentry has a self-hosted solution, btw.
nomercy400
·6 か月前·議論
In contrast to what other country?

If a think tank from a non-tariffed country would write this piece, they risk getting tariffs tomorrow.

And would Americans trust a (US) think tank in the juristiction of the US government right now?
nomercy400
·7 か月前·議論
This fix sounds more like a hack. Effective, but not a long term solution, and it has negative effects like the firewall.

It is almost guaranteed that people will not be able to call, due to firewall blocks or process not running or some other issue.

It feels kind of strange to pull the main feature/usecase of your application out of your application. I would reconsider my design by then.
nomercy400
·7 か月前·議論
From a story point or view it makes sense. Why try to please those not present at Christmas table.

If the table was filled with carrots as guests, do you think the rabbits would be invited? The original wolf would.

I know, I know, it is about bettering yourself.
nomercy400
·7 か月前·議論
Anonymity should not be possible if you pay/receive money for it. Anonymity should be possible if it doesn't involve money / contracts with money. See my sibling post on my view.
nomercy400
·7 か月前·議論
The important part is that there is a difference between

content for money

and

content not for money

The first should make the hoster liable, they have a contract involving money. The second should not automatically make the host liable.
nomercy400
·7 か月前·議論
The party which decides to show the advertisment in exchange for payment, should be more responsible for what they are showing than a free user posting content.

Now things become interesting when a users pays for ranking or 'verification' checkmarks. What makes that content different than a paid advertisment?
nomercy400
·8 か月前·議論
You cannot lead if you only copy.
nomercy400
·8 か月前·議論
How about using Javascript to fetch the XML (like you would do with JSON), and then parse/transform it with a Javascript or wasm XSLT library? Just like you would do with JSON.

You need a server to serve Json as well. Basically, see XML as data format.

RSS readers are not chrome, so they have their own libraries for parsing/transforming with XSLT.
nomercy400
·8 か月前·議論
Aren't there other ways to load and parse a technical format like RSS to a human-readable format? Like you would do with JSON.

Or can't you polyfill this / use a library to parse this?