When will the UK citizens stand up against the regime?
not gonna happen, the issue is very deeply rooted already, you can't change that without force
Readit NewsaPoCoMiLogin commented on Mullvad VPN: Banned TV Ad in the Streets of London [video] youtube.com/watch?v=rwhzn... · Posted by u/vanyauhalin
aPoCoMiLogin commented on Elasticsearch was never a database paradedb.com/blog/elastic... · Posted by u/jamesgresql
”That means a recently acknowledged write may not show up until the next refresh.”
Which is why you supply the parameter
refresh: ”wait_for”
”schema migrations require moving the entire system of record into a new structure, under load, with no safety net”
Use index aliases. Create new index using the new mapping, make a reindex request from old index to new one. When it finishes, change the alias to point to the new index.
The other criticisms are more valid, but not entirely: for example, no database ”just works” without carefully tuning the memory-related configuration for your workload, schema and data.
it's the other way around: `wait_for` waits for the next refresh (there is configurable refresh interval, 1s by default), `refresh: true` forces refresh without waiting for the next refresh interval.
the difference is that waiting for refresh assures that the data will be available for search after the "insert" finishes. forcing refresh might be foot gun that will criple the servers.
aPoCoMiLogin commented on Elasticsearch was never a database paradedb.com/blog/elastic... · Posted by u/jamesgresql
I worked in a company that used elastic search as main db.
It worked, company made alot of money from that project. It was a wrong decision but helped us complete the project very fast. We needed search capability and a db. ES did it both.
Problems that we faced by using elastic search: High load, high Ram usage : db goes down, more ram needed. Luckily we had ES experts in infra team, helped us alot.(ecommerce company)
To Write and read after, you need to refresh the index or wait a refresh. More inserts, more index refreshes. Which ES is not designed for, inserts become slow. You need to find a way to insert in bulk.
Api starts, cannot find es alias because of connection issue, creates a new alias(our code did that when it cant find alias, bad idea). Oops whole data on alias is gone.
Most important thing to use ES as main db is to use "keyword" type for every field that you don't text search.
No transaction: if second insert fails you need to delete first insert by hand. Makes code look ugly.
Advantages: you can search, every field is indexed, super fast reads. Fast development. Easy to learn. We never faced data loss, even if db crashed.
most of these is more lack of experience than the DB fault. most systems have its quirks, so you have to get used to it.
aPoCoMiLogin commented on Ask HN: How do I help a colleague who introduces a lot of typos? · Posted by u/tornadofart
in my case, i ultimately introduced linters, formatters, git hooks, gh actions, etc. i've tried to explain and tried other things, but it felt like babysitting at that point. if someone is unaware of their own weaknesses, there isn’t really much you can do about it; you'll just end up fighting, which will make both of you resent each other
make everything as code, introduce linters, formatters, hooks and checks. when you work in a small team with people of a relatively similar mindset, such things aren't necessary, but when the team grows, there will always be issues with such things. so having a mechanism to enforce rules is necessary for your own sake
very nice. there are things that won't show up in the network panel and you had to resort to proxy for debugging, especially when you are using puppeteer/etc for testing.
aPoCoMiLogin commented on Aisuru botnet shifts from DDoS to residential proxies krebsonsecurity.com/2025/... · Posted by u/feross
recently had to research "residential proxy", and the number of websites that claim that they have millions of IPs on hand was very strange. then the fact that a lot of them work in the exact same way, and a lot of them accepted payment mostly in crypto was very strange. so now connecting the dots, makes sense now why these "residential proxy" websites looked and worked the same way
aPoCoMiLogin commented on Why did containers happen? buttondown.com/justincorm... · Posted by u/todsacerdoti
it happened because the story of dependencies (system & application) was terrible. the ability to run the app on different distribution/kernel/compiler/etc was hard. there were different solutions like vagrant, but they were heavy and the DX wasn't there
aPoCoMiLogin commented on Google Pixel 10 series review arstechnica.com/gadgets/2... · Posted by u/thunderbong
Pixel prices tend to drop like a rock after launch. By Christmas they'll be a lot cheaper.
exactly, i'm using "google phones" since nexus s, and they always have some discounts few months after release. other thing is that they currently offer 5y of updates, so even one year later with heavy discounts the phones are still good. i've got my P8 Pro with 1/3 discount
> they also got me reported to HR by the manager of the XROS effort for supposedly making his team members feel bad
This is madness. The safe space culture has really gone too far.
it is madness, you would be surprised how many ppl take things too serious. been there, had talk with HR cause i've said that the solution is mediocre and we have to do something better than that.
aPoCoMiLogin commented on He Rewrote Everything in Rust – Then We Got Fired medium.com/@ThreadSafeDia... · Posted by u/wallflower
Can people not use Medium? I'm not making an account just so I can read something.
prepend medium url with https://freedium.cfd/<medium_url>