HN user

codedokode

9,301 karma

PHP developer from Russia.

Posts7
Comments4,866
View on HN

Blockchain is unnecessary complicated, for example, it has mining, rewards for those who add new records, even VM and scripts and all of these are not needed for a government registry. I do not need scripts within a land registry.

One usually uses "query builder" pattern for that.

Also, regarding placeholders, historically many DB and frameworks do not support passing lists for a value in a placeholder (like "WHERE id IN(?)") so users of such software fall back to string concatenation.

It doesn't matter, it's a dumb idea anyway because there is a central authority managing the land registry and there is no need for anyone else to be involved.

Also, SQL database is much more convenient to use, it has query language and indices unlike a blockchain.

No. Blockchain is made for managing transactions between untrusted parties. In case with a land, there is an authority managing the registry, so a standard relational DB (with optional digital signatures) is the bets option. Why someone wants to use a tool, not good for a specific purpose, for that exact purpose?

So that 50% attack results in someone taking all the land? No thanks.

It is a poor idea to use blockchain for government registries. If you want transparency, simply publish signed daily updates and that's enough. Just use simple DB with backups, and optionally, a printer printing changes on a paper.

I think no country can be trusted and therefore all IoT device communication (telemetry/updates) should go through government-controlled local servers in an unecrypted form. This way local government can enforce its policy over foreign manufacturers and has a "kill switch" if they misbehave.

Also, all communication and telemetry should be opt-in and turned off by default.

Government-controlled server would prevent foreign countries from collecting intelligence and pushing malicious updates.

The problem might be more complicated. In those times, they might not use a separate mic for every instrument (and the mics probably were not great), they might might not do the mastering properly, the amps could distort the sound, and instruments could overlap each other. And if you try to simply amplify lower frequencies, you might end up getting too much noise.

Could it be that irregular sleeping is caused by inner clock being off due to genetic errors, and genetic errors are the main cause of mortality? I.e. irregular sleep is not the cause but the indicator?

Or irregular sleep corresponds to bad habits like drinking and using drugs and they are the cause of mortality?

Or, could it be that problems with sleep are caused by using alarm clocks, i.e. not waking up naturally but forcefully at unnatural time? Waking up at the same time every day benefits people whose inner clock has 24h period and disadvantage people with clock tuned to 23h or 25h day.

Or I am wrong?

But to write the text, LLM needs some source, where does it come from? You need to write something anyway.

No I meant you must use an API that accepts URL and cannot create SSL sockets and hide communication from Telegram.

Maybe the voice should be copyighted or protected then, I do not want anyone use to my voice, let them use their own boring afwully sounding voice. I am sure such models are used in 99% cases for illegal purposes or creating fake news.

Also, one's likeness (like face image) should also be protected from being used by anyone.

Could it be because the author is not very confident in their English skills so they asked an LLM to translate text to a proper English?

This means the code must pass the URL in cleartext so that Telegram can detect those who try to use bots for scraping and proxies.

It looks like they are making their own cloud, with such a little team?

Also we should be using Matrix but it doesn't have half of the features (no channels, no mini apps etc).

Also I wonder whether compiling JS to native code is worth the hassle or not. In browser, it would slow down page load, but here you need to compile only on deploy.

It makes sense: European users are assigned to EU data center, and Chinese to the one closer to them. The "custom code" should not be complicated, just a map of country to DC.

You are suggesting to develop a compicated solution (spend money) when current simple one is working ok without any elections.