skysight-inc/HackerNews huggingface dataset:
Mullvad claims to not log IPs so they cannot hand out anything via a court order and at least once a court order has turned up blank [1]. It is possible that CIA or some other intelligence agency has infiltrated Mullvad and logs them but that is nothing that will ever be used in a normal court case. They will only risk revealing their hand if you are some major crime boss, a spy or a terrorist.

If you are just a file sharer or normal low level criminal I doubt the CIA (or whoever may have infiltrated Mullvad) would give anyone your IP.

1. https://www.svt.se/nyheter/lokalt/vast/husrannsakan-mot-vpn-...
US and US/British army have a weird addiction for drug. China is only a very recent player. Golden Triangle and Golden Crescent were developed by US/British armies and FBI as a drug powerhouse.
Now that we have another Nix post, maybe someone can enlighten me about something I've been wondering about.

I'm one of the maintainers of a popular django application. Someone made a nix package of the project, but we've now twice gotten invalid bug reports from people using the package because the package depends on "django_4" and whenever someone updates that nix package, the package for our project breaks.

Of course we, like all other python projects, don't support using other dependency versions then the ones in the requirements.txt file. So when someone just uses a different minor version of django, stuff breaks. What's the disconnect here? Why does all nix packages that use django_4 need to use the same version, that seems super prone to breaking all kinds of stuff. Same for the other 35+ dependencies that run arbitrary versions instead of the ones defined in the requirements.txt file.
This is the form for reporting malware on Play, and it includes a free-form text input for describing the issue:

https://developers.google.com/android/play-protect/pha-repor...

(It is a bit odd that there's no DoS category on the report form, despite it being listed as a category on their taxonomy page at https://developers.google.com/android/play-protect/phacatego..., but I expect that you can just enter that in the "other" free text field.)
Illustrates how using Rust or any other fast language doesn’t necessarily make things fast.
hence duh...and the idiot who downvoted me is just that, an idiot
> But since COVID I would say thats only been about 25% of my direct reports. It’s certainly not the majority. Some have, unfortunately, been let go as a result.

Well, I'd say it's good. Remote work also requires commitment and responsibility. If the excuses are feeble and are always the same then, well...

> Unfortunately Executive leadership is seeing this in the non-tech divisions too and are now mandating less remote work.

Yeah, see above. It is important to reinforce that remote is not a "free for all".

Sure, everybody goes in an errand once in a while, but productivity/meeting attendance etc is needed
Show HN: Track3 – Analyze your crypto assets on CEX and Web3 wallets
"Track3" is a desktop application designed to analyze your cryptocurrency assets.
It can analyze your assets across centralized exchanges and digital wallets, presenting their changes through various charts such as asset allocation, rankings, price fluctuations, and more.
It does not have a backend server and by default, all data is only stored locally.
However, it supports cloud synchronization, users can turn on it to make data can be synced across devices.
I am in the same position. I also live in a third world country. I am currently planning to quit my job (similar to Singapore pay) and start my own software business. I plan to do lots of experiments to create small products that solve niche problems relevant to the local context. Like you said, there are so many problems. What is important is to think about distribution or customer acquisition channel/cost before you build the product and facter it into your product. It is worthless if you can't sell it. Focus on quick product iterations to find out product market fit.
I was at Twilio for 10.5 years, and left at the beginning of 2022. It's interesting to read things like this, from someone who joined in 2019, as the change OP is talking about in the company started well before his arrival. We all saw it, with increasing emphasis on enterprise sales (we hired someone from Salesforce as COO specifically for this). Courting individual developers and small startups stopped being a priority, even though those sorts of folks are the ones who formed the backbone of Twilio's mind share.

I'm not saying this was bad thing for the business; Twilio's growth would have slowed well below what would have been acceptable for a VC-backed (and the newly-public) company without this move. I'd be lying if I didn't say I was happy with where the value of my equity went. On top of that, Twilio was life-changing socially: I have many dear friends who have remained dear friends well after we all left the company, something that's never really been that case for me at other companies. As for the work itself, there were many fun and challenging problems to solve over time as the company grew, despite our frustration with the growing pains.

In the end, I left for very similar reasons as OP: the company seemed more focused on helping brands increase engagement than on doing anything novel with communications. Sure, a lot of the older, interesting use cases (the ones that got me stoked about Twilio in the first place) were still running on the platform, but those kinds of things felt like a minuscule percentage of the business.

The change of the billboard to the "How can I reduce my acquisition cost" branding makes me feel sad any time I drive by it. "Ask your developer" was brilliant, but Twilio isn't that company anymore, and hasn't been for a while.
I'm curious if you have any pointers for whole Mac config with nix-darwin. This is something I've just started looking at and at the moment don't have much more than a nix-shell with some nice-to-haves. Any tips / tricks / guides are greatly appreciated.
800. But for every Arabic loanwords you'll find a romance one almost in any case.

Aceituna->Oliva.

Alcoba->Habitación

Alcancía->Hucha

Except, of course, for universal stuff like alcohol, álgebra, azúcar, azafrán...
And at a glance I have no idea whether S is better than One without going to Wikipedia.
> Britain is unwilling to apportion blame at this stage for the destruction of the Kakhovka dam in Ukraine and is awaiting "all available facts", Foreign Secretary James Cleverly told AFP on Wednesday.

> "We're not going to say anything until we are completely armed with all the available facts. So we're going to err on the side of caution on this one," Cleverly said in an interview on the sidelines of a meeting at the OECD in Paris.

> He said that Russia bore ultimate responsibility for all events and destruction in the war, however, having initiated the conflict with its invasion in February last year.

> "It's clear that this event is a direct repercussion of Russia's invasion of Ukraine, and there's nothing that Russia can do to hide that fact," he said.
I had a Chinese video app, like 10+ million installs and it bricked my tablet. It worked by only targeting people with other keyboards then Chinese.
Even tho I'll get flak for it, I'll call bs on the article.

It's the same as the phrase "(premature) optimization is the root of all evil". Does it mean you should never optimize? No. Does it mean you should always optimize as a last step? Also no.

Here's the full quote:
"Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%."

It's way more nuanced and basically says: "Stop wasting time on optimizations with little gain, but still do them where they are useful/necessary."

Right now I'm working on an embedded device running a small Linux. Our resource usage is well within the bounds, so thinking about better architectures or optimizations is an imaginary problem. Right? No. Not at all. Making our software smaller and/or faster doesn't only mean we can put on more software, it also means we could produce cheaper because we need less resources.

Thinking about and experimenting with different architectures or newer technologies also seems like imaginary problem solving at first, but there is a good possibility that you improve your system as well. A better architecture could make your software more maintainable or give you the flexibility to implement new features in a way, that was really cumbersome with the old code.

So while I agree with the sentiment that you should not implement things you don't need, I also think that there should be room for people to experiment and try out different things. Because sometimes, the people working with the code the longest are blind to it's many shortcomings. Because it's normal for them to just work around them. But getting rid of those shortcomings can save you hundreds of man hours of work in the long run.

To cut a long story short: Do experiment. Do think about problems you might have in the future. Do the mental exercise and think about how to improve your current code and architecture. But don't blindly implement it

Always evaluate what your trying to do. Check if it improves the things it's supposed to improve and also check if it doesn't make matters worse elsewhere. Get to know the tradeoffs and make informed decisions if changing something that works to something that's better is worth it to you.
If you look at the Baltic, I presume (But never worked there, this is a guess)

* We know what ships went near the pipeline. AIS probably has it, and in that case radar would show a ship without AIS.

* We know where the pipeline is.
* We don't know that something tiny like a bomb was attached. We don't know which of the passing ships did it.

Same for the north sea: We know what ship/windmill/.. exists on the surface and on the floor. But I know of some divers attaching an experiment to a war ship wreck, coming back a few months later for the results, and they notice someone stole one of the ship's cannons (and these are huge and heavy). They were surprised this happened because of the sheer size of the thing, but minor theft and vandalism underwater is an everyday occurence for them.
XBox 365.
> Using VS Code Remote SSH on NixOS systems

This is the main of issue with Nix and other niche distributions: they are new operating systems, with their set of file layouts, package managers, and even syscall variations.

Linux ecosystem is awfully fragmented. If you ever want to use any software outside of your not-very-well-walled-garden provided by distribution authors, you have to hope your operating system (that is, distro) is sufficiently similar to one of few distros software authors have built and QAed their software on.

I have written at length about it here: https://dottedmag.net/blog/linux-is-not-os/

I wish for a system that:

1. provides declarative configuration.

2. allows for easy local patching.

3. is ABI-compatible with a major distro.

Alas. Fedora Bluesilver delivers 1 and 3. Gentoo provides 2. NixOS provides 1 and 3.
Amazon Drivers Are Just “Drivers Delivering for Amazon,” Amazon Says
I believe I had a Soviet stove in my early childhood whose burners were made out of titanium, at least they were super light like made from plastic.
This is pretty neat. I tried the "Digital Colour Meter" app on MacOS, but both whites shows exactly the same values and it is also impossible to take a screenshot of. So I wonder how this works in the OS.
Goddamnit, the JavaScript ecosystem needs its own Visual Basic. Something that comes with everything you need to build and deploy a basic, but functional, real-world application.

* Any dependencies need to be installed to build a real world (server + UI or API) application = non-starter.

* Any shell commands needed to write, build, or deploy the app in a container = non-starter.

* Any code necessary to lay out the UI (including HTML, CSS) = non-starter.

I haven't kept abreast with the Microsoft ecosystem. Does Visual Studio have something like this for Node apps? Is ASP still a thing for C#?
You can get by in Tokyo without knowing much Japanese, but the real joy of traveling to Japan is experiencing the culture and you can do that best by learning the language. It isn't easy though and that can be off putting, but learn a few of the useful phrases like " how much is it" and go from there. It's well worth visiting especially with the yen so weak.
This rhetoric pops up every time gql is discussed on HN, and it is invariably full of misconceptions and, well, nonsense, that just tells anyone who's actually used gql that you clearly haven't.

I never understood why people insist on having strong opinions on things they clearly know nothing about.
Why I started (and stopped) making games
They could have used increasing rotational degrees - Xbox 360, 540, 720, 900 and so on. Just like action sports, very extreme.
More like power hungry mods who were happy ruling their subreddits not being happy that there are people who are more powerful then them and willing to make decisions without them.
Before opening the article I was thinking "I bet its another 2D side-on platformer". The genre isn't even mentioned in the article, but from looking at all the screenshots (as I would on steam) I can't see why I would buy this over the other three thousand or so 'indie platformers' released each week. They need to do something different, not in theme, appearance, gimmicks or whatever, but in actual game style.
Does it hold up for today?
Rock and Roll Drums: All You Need to Know
I agree. Anyone developer who has had to work on multi-player games will never say "just add multi-player". The whole way you approach the game changes massively.
One of my friends lived in a squat in Melbourne for a few years. They sort of ran it, meaning they would put the place on couchsurfing.com to attract more people. They had anywhere between about 4-20 people living in the house at any time, each staying anywhere from a few days to a few months. The place was a little bit run down, and had no electricity or running water, although they did have gas and were able to cook food. They used candles to light the place at night, and would retrieve water from a nearby public tap and shower at a nearby university. They'd also dumpster dive all their food. The place was actually pretty awesome and had a really great community feel, albeit run-down and mouse-infested. There was lots of artwork and poetry printed directly on the walls.

They'd often have lots of people over and spontaneous parties were common, though they had to keep the noise down since the owner could theoretically come at any point and kick them all out, and in the end that's exactly what happened. The owner was actually pretty nice about it, and was impressed at what they'd done with the place, but kindly asked them to leave, which they obliged. The house is actually still there and my friend hasn't lived there for years so I'm not sure why the owner kicked them all out.

On another note, Moxie (of Signal/Open Whisper Systems fame) has some pretty cool stories about his adventures in squatting - https://moxie.org/stories/together-two/
> stock buybacks, or other things that directly enrich investors at the cost of employees

As a former Twilio employee (and current stockholder), I have to disagree with this. Stock buybacks generally raise the stock price (or at least keep it from falling). Up until 2020 or so, Twilio was fairly generous with equity comp (at least for some of us; obviously I can't speak for all employees), so employees do indeed benefit from stock buybacks.

I suppose you could make the argument that, as a company spends cash to buy back stock, base salary raises get worse, since the company has less cash on hand to fund those raises. But I think you'd need evidence to back that up.
The big auth companies have been really good at creating those "Don't roll your own auth EVER!!!" articles.

You're not alone. I take it a step further and don't deal with passwords. I use login through email, in which I send a nonce to the user's email. The users enter that nonce to log in. This is what many online bank apps do. That reduces the security surface area to CSRF, securing cookies and session expiry. Most popular frameworks should handle that part of it.
That was pre COVID news, if not more on the order of five years ago. Although now that I think of it, with Spectre and Meltdown mitigations perhaps the clock has been turned back on those improvements.
Feels a lot like what happens with electronic music producers. There is a bunch of highly taltented sound designers out there, putting their hard work on BandCamp or whatever platform is friendly enough to make some bucks on. But almost nobody can make a living off selling releases. Almost everyone has to tour and play live gigs to make some money. And I guess the biggest reason why it is so hard to make money with releases is the same as with indie games, too many people trying to get a piece of the same cake... Paying fans are rare.
> In the realm of quantum computing, it always has

No: https://en.wikipedia.org/wiki/Post-quantum_cryptography
Can you give an indication of average salary in the US?
Github can't easily cache a remotely hosted repo that some random CI test (essentially a script) accesses, at least not without some very hairy proxying.
I still run WSL1. Perf on WSL2 was still horrible if your files are under Windows last I checked.
Impressive tool. I'm looking forward to giving it a try and learning more about the AT protocol.
> It's extremely elegant and nice to use over creating custom endpoints for every use-case, but the N+1 SQL query problem is a giant thorn.

Having not used, but only read about graphql, this was the first thing that struck me. It seems great at minimizing data transferred to the client, but it doesn't (seem to) stop that data being fetched from the DB - it just post-filters it.

I'm imagining a scenario like a dashboard, where you're getting a small amount of data from a lot of places. With REST, we'd generally do that by having a dedicated endpoint for the whole dashboard that executes a single query, letting the DB do what it's good at (efficiently retrieving required data). My naive impression is that graphql would execute a bunch of queries, trim what's not needed and join it all together. With anything non-trivial that seems like a performance nightmare.
Ah the good old "think of the children"-trope. A centuries old, but highly effective populist tactic — might you have fallen for it?

They say: $political_enemy wants to force children to do $x, therefore we must ban $x. Of course their goal is not to ban $x for children, but for adults as well. And the gullible public goes "Oh lord, not the children!" and supports them.

So be aware that in reality it is the right who wants to forbid gender reaffirming care for adults — if they gave a single fuck about children they would do something about the leading cause of death for children. Don't you think kids getting slaughtered is "a bit" worse than a tiny fraction of them undergoing gender reaffirming surgery? And if you don't exactly know what gender reaffirming surgery means, read up on it please?

The kids are just an excuse.

Just like with the book bans, where they first say they want to protect kids and then they ban books from public libraries that can also be used by adults. Or drag shows, first it was about kids now they want to ban adults from them as well (see: https://www.theguardian.com/culture/commentisfree/2023/mar/1...)
1995 car automatic transmission with neural network: https://www.sciencedirect.com/science/article/abs/pii/038943...
Frontend decoding x86 instructions to uops, like from P6 onwards, is a bit different from microcode in the usual terminology. I guess you could make an argument that uops are also a type of microcode. But it gets confusing since there is also traditional ROM based microcode in post-P6 x86 chips.
Given poor communication, trivial things lead to conflict. This is the case in every relationship. The takeaway should be that you need to communicate well, not that you need to pay attention to one specific subject.
Which they do. Twilio's equity comp was fairly generous, at least for a time, and I believe all employees had equity as some percentage of their compensation. In addition, Twilio offered an ESPP that all employees could take advantage of.

(Full disclosure: former Twilio employee and current Twilio stockholder.)
Using something like `pothos` for your graphql backend, you can get tight integration with `prisma`, which will practically eliminate any N+1 issues.

For fields which hit external services, you can define types as "loadable" so that every time those are requested in a batch, they are loaded efficiently to avoid n+1.
> * people append "reddit" to search results as one of the the last places they can get free genuine content

Genuine is reaching too far in this context. Reddit is getting gamed just like any other platform, you've just told yourself that it isn't. People have known about appending "Reddit" for years now. Many large tech sites write stupid articles like, "The 10 most popular mechanical keyboards according to Reddit users" and similar clickbait.

I'd also add to this that there are SEO tools that can give you tens of thousands of "Reddit" keyword suggestions in a single click, alongside their search volume, cost per click, etc. Brands absolutely will and do abuse this because it's marketing, just like everything else.

Speaking of SEO tools, that should perhaps be on your list of culprits with the issue of poor quality search, or rather - poor quality results. SEO tools make it an absolute breeze to get a global overview of what people search for and how hard it is to rank for that content. Outside of the major keywords, there are millions of long-tail keywords that can be exploited by thin content, and because people do search for those long-tail queries, Google has no choice but to index and rank that content.
15 years ago, I used to write a blog where I wrote free content in my area of expertise (PhD). The blog paid for itself via Adsense ads. It was a part-time thing. Eventually, the revenue dried up and I moved on.

Today, I'd never imagine myself being able to put out free content as a main source of revenue without either some sort of sponsorship/affiliate and or subscription. It's more likely that I will write but put my content behind a subscription on Substack or something like that.

And because of that, people lost the ability to read my content for free. I'm not saying that my content was insanely valuable but there exists a gap in which the content is valuable to many people but not valuable enough that people are willing to pay a subscription to read it.

In addition, subscriptions usually mean that you have to write full-time. Most experts in their fields would not likely to quit their main jobs just to write on Substack. This means Substack writers aren't likely to be at the top of their field - they're just good at writing and they write consistently.
Oh.. cool. Is that what broke my Docker project last week? Was complaining about clock skew.
To be fair, this is what US has been doing to US for a while, too.