skysight-inc/HackerNews huggingface dataset:
duller pixels require less light, so more profits can be made for shareholders. this is the main reason why marvel movies, the most commercial movies of all time, have gone that route. also the ceo happens to be colorblind.
The EU regulating itself out from the market.

Not for the first time, mind you.
The virus is in dying days and we have gotten here through the free market.The past few weeks Ive known many who have gotten omicron and all have had what feels like a minor cold and recovered quickly. It was capitalism and the US that made vaccines quickly and distributed them throughout the world. Socialism could never have done rhat. The failures of socialism are proven time and again in country after country. The effort to use this crisis as an excuse to extend the reigns of government control and destroy the free market engine that has brought much good is not persuasive. The desperation is apparent.
How much traffic do you get? What software? OpenVPN is a resource hog.

I'm on a $10/year VPS with 100 Gb/month traffic. Not great, but not terrible.
>It was designed and specified at a time when the Unicode code space had a 21 bit limit

21 bits is the current Unicode limit. Unfortunately UTF-8 in 3 Bytes only has 16 usable bits - the first byte starts with 1110 and the two continuation bytes start with 10, so it's 4 + 6 + 6 = 16 bits.
> I know a number of people who are just DONE with with covid culture, and just want to get away from it.

What do you mean? What is "covid culture", and how do you get away from it?
We don't have that.
> It's not like the enforcers could walk into the datacenter and plug in the usb drive and get the data.

They can ask and/or force a given company to hand data to them in many cases in most jurisdictions.

> Does logging constitute user data.

Logging of user-data? yes

> A much saner approach should be limiting what the company is allowed to do with the data.

GDPR does also regulate what a company is allowed to do with data. The thing is: whether the GDPR applies and is enforceable depends on where that data is stored.
I had a small business once with a few large outstanding invoices. These were owed to us (small company) by a very large organisation. Our payment terms were 30 days and the invoices were now out to 120 days. We were hurting very badly, but had pretty much no leverage over the very large organisation to make them pay - we weren't the only game in town and they could just take their business elsewhere.

Anyway, we investigated factoring of the invoices and we certainly weren't offered 95%!! This was probably 10 years ago now, but I recall we would only received something like 70% of the total invoice value. I thought it was a real rort.
Cool, is the guy from the video the one you sent your computer to?
Good luck!
There is a conclusion here that I'm missing which could have easily been made. It's that excessive logging often attempts to replace tests. Using the trivial example from the article, you wouldn't feel compelled to log the result of Add(x, y) if the Add was unit tested.
We use BoxiePro Deep Clean, Scent Free, Probiotic Clumping Cat Litter and it is smell free, you can't smell the litter or the cat 'presents'. My wife is pretty sensitive to smells and she loves the new setup vs traditional with yesterdays news.

You will smell it when you open the drawer to change the bag a couple times per week but only till you tie up the bag to take out.
No, it is not. NAT is not a firewall; its goal is to let traffic through, not prevent it. The fact that it sometimes happens to behave like a firewall is very dangerous since it leads people into a false sense of security.

I have early 2000s routers that would basically forward all UDP traffic from $IP to the last computer that had sent any traffic to $IP. This did wonders for most games, but you were in for a nasty surprise if you were relying on NAT to protect your fragile Win9x network...
Ask HN: Experience of “normal” hosting costs in SaaS?
As our SaaS startup increases we did hit the 10k monthly active users a few months ago.
One of our main questions we try to figure it is: Are our hosting costs in range of "normal"?

Currently we do pay ~ $1.5k in app server and storage plus ~ $4.5k in database.
This is roughly $0.5 per user per month.

I understand this differs a lot depending on the software provided, but still very interested in other numbers and opinions.
What is your experience with hosting costs in SaaS business?
It's strange to think I was working on AngularJS and Flash apps at the same time. Flash feels like it was a millennia ago, whilst AngularJS feels very recent. Maybe because AngularJS's successor keeps it's name fresh in my mind?
That's not "shitty code", just "simple code". Also regarding the last paragraph, IME the more senior you get the more you realize that writing code for hypothetical future requirements doesn't make much sense. I've seen this sort of enthusiastic overengineering much more often with junior peeps fresh out of university (including my younger self).

PS: It also seems the author is still early in the learning process, my advice: what you describe are all good programming practices, they're not just useful for the "learning phase", keep them!
There's nothing black swan in an inflationary environment that leads to hyperinflation, even if it's for a country with a reserve currency.

Every empire hyperinflated itself in the past, people just ignore history and how returning to sound money is inevitable.

The only black swan part is that now we have a better alternative to gold.
By three cars each X-D

But there is green lining added to the river at least.
That river looked very sad in 1902.
Deputy to Quit
I hope the author at least trademarks 'Wordle' to be able to counter some of the copycats.
Games went through this during the PS3-360 generation. I'm sure it'll pull back over time.
"Clarification: AngularJS and Angular are different frameworks. The announcement for end of life is for AngularJS that Google released in 2010.

Angular is in active development and growing. Exciting big changes coming in 2022!"
My interpretation of the actual post is less, write “bad” code, but more don’t let code quality prevent you from trying something. The former presentation of it though I can’t agree with while the latter I do.

I feel code quality is important, not because of future state and optimization but a strong architecture will facilitate other engineers learning, which is critical. For example, not all engineers have learned design patterns like the strategy design pattern or observer, etc (see https://refactoring.guru/design-patterns/catalog for great examples) where a little guidance can save them a lot of pain.

With that said, I understand we all bring different skills to the table. Some people love making every linter pass while others could care less and some actively hate it. This is fine, we just need to respect each other enough to try to build on each other’s strengths and support each other where we’re weaker.

TLDR: Rather than saying it’s fine to write “bad” code, say don’t let code quality intimidate you, and be willing to try. You can always refactor later and you’ll learn as you go.
»Max Schrems: "In the long run we either need proper protections in the US, or we will end up with separate products for the US and the EU. I would personally prefer better protections in the US, but this is up to the US legislator - not to anyone in Europe."«

That's the point: we need real data protection in US law for non-US citizens as well. Currently, US lawmakers treat EU citizens' data as US state property. Obviously, that's unfair.
Nothing about GDPR is hard ... unless your business model is to abuse your customers' personal data. Then it might be hard.

I routinely see the loudest complainers about the onerous nature of GDPR compliance suddenly get vague or stop posting when you ask for details of precisely what bit is so hard for them in particular. Note lack of those details in this present discussion, for example.

So far, it seems a safe assumption that the excuse makers are abusing personal data, and they know they're abusing personal data.

Perhaps one day a clear exception will show up.

I wrote up a thing here a few years ago with my actual on the ground experience of getting us compliant: https://reddragdiva.dreamwidth.org/606812.html

tl;dr anything that might vaguely constitute personal data, down to Apache logs, must either be in a writable database for redactability, or deleted.

Since then, our legal team - who are not your legal team! - has advised:

* 30 days for operational purposes is fine actually.

* Go feral on anything over 30 days. You need a named person responsible for GDPR redactions.

* If you want to do analytics on those Apache logs, do them quickly and into a form that doesn't contain personal data.

I'm in the UK, which is no longer in the EU, but the GDPR laws still hold here.
Also probably why security theater (TSA et al) still exists.
> My opinion is that once an organization is a certain size, everything really needs to be written down and easily accessible. I shouldn't have to regularly ask people how to do basic things, it should be on a wiki. If it's complicated, it should be in a training video, or a user manual.

This %100. Automate all the things, but for any part of the process that cannot be automated/scripted, write it down. And don't just put it in some random Google Doc or Sharepoint where it is lost forever in the ether. Put it in a README that lives with the code or have a shared Wiki for the team. It need to be somewhere that is generally available, searchable, version controlled, and easy to update.
Against Land Acknowledgements at the University of Washington
Some of those are nice things, indeed, but when you ballpark the hourly rates, you’re paying a very high price for them.

30 days PTO instead of 15 or 20 and being paid overtime instead of just being paid 3-5x as much with overtime being “included” isn’t obviously better to me.
This reminds me of the ZFS talk where they note that if you have enough clients doing sequential IO, it looks like random IO to the server.

https://youtu.be/yHgSU6iqrlE?t=2577
I think I got a raise two or three times in 20 years. Most real raises were new jobs.
What happened to the countries that hyperinflated?

We're they able to get it under control historically?
“I need my sleep. I need about eight hours a day, and about ten at night.”
— Bill Hicks
> What happened to us, as a society, that creates the expectation that a thing should be monetized?

Well, people need to eat.
> Something that would have immutable rows

Isn't this just a log (or a stream like Kafka or Kinesis)? In fact you might even be able say every database already has this ;) (binlog, oplog, etc)

> not the whole db

If rows are immutable, what part of the db is left not being immutable? If rows were immutable, doesn't that imply that any existing "ranges, searches, indexes, etc" are immutable too?

If you going to the effort of making a decentralized database, why not also decompose all of these parts from one another... no reason the tables (logs), indexes, search, etc have to live in the same database, they could be spun off as completely different parts. Basically a something that indexes logs and then something else that takes those indexes and makes the searchable.

In fact this is all the rage right now with centralized databases... all of the work being done with streaming systems just seems to be an effort of decomposing and inverting databases... every old is new again.

Anyways, I agree with the idea and don't really know enough about decentralized systems to really understand why such a distributed database can't or hasn't already been built.
> A much saner approach should be limiting what the company is allowed to do with the data.

Perhaps we should have some sort of GENERAL rules or legislation specifically for DATA to define what companies, based in or with customers in a region, can and can't do for the PROTECTION of the data and end users, so the companies can stay compliant with this REGULATION.
Empty oceans
I’ve always wanted to add an HTTP joke to these sorts of networking humor threads but the prospect makes me feel mildly insecure.
I mean, capital has the edge over labor in everything we do in this country. Labor even votes against its own financial self-interests. It’s who we are.
Using common services like GA or Stripe (https://noyb.eu/en/edps-sanctions-parliament-over-eu-us-data...), and even more services by smaller companies that don't really care about GDPR. Embedding Facebook or Twitter content.
> It's just that the implementation sucks big time.

Yes, the way companies are "implementing" GDPR compliance sucks, even though GDPR compliance is not that complicated. That should tell you that those companies think it is more profitable to annoy you than to have a privacy-compatible business model.

Github, for example, gets it right. It only stores data it needs for fulfilling the services it provides to you, so there is no need for cookie banners and similar. That's exactly how the GDPR intends it to work. The problem is companies dragging their feet and trying to fool you into thinking it's the fault of the GDPR that they don't respect your privacy. Incredibly backwards, but sadly it seems to work.
This is one of those posts that exclusively caters for reassuring the audience regardless of whether they are doing right or not just to make them feel better.

Refactoring is part of a cycle and you do it before you publish your code to others. If you don't clean it up, you are wasting someone's time.
For me some top qualities of good code is -
Readable
Maintainable
Fault tolerant

If it works, there are no plans to extend it and there is no one to read it - then it doesn't matter what it is. I know its good code without having to look
I am not complaining.

Someone in my team recently left because they wanted a short commute to a sociable office which we could not offer them. They had already been given a promotion and pay rise without having asked for it. And the company has all the normal career development stuff. Yes they "graduated" and that is fine. It was the right choice for them.

And our business model has limited flexibility in terms of salary anyway. We are honest about that. But it is still a good fun job with lots of oppurtunities within the company or in the wider industry. But their is always a risk that those graduates will be exploited and that risk does make me uneasy.
Not sure if this yt video was referenced, but it offers a good overview:

Why are modern films underexposed?
https://youtu.be/ctXc6YHIyac
> I know how to write good code.

> Usually it means spending more time now to make the code better for some future state of the world.

No. That is called premature optimization/abstraction/development and should be avoided. Shitty code is shitty today. Poorly chosen names, copy-pasted pieces, implementation doesn't reveal intent, mismatch in code and comments, etc. Doing these right should be habitual and shouldn't be a function of cycle time. Otherwise, they tend to creep easily.
I avoid changing it. I keep my desktops as close as possible to a standard install.
If in 2022 you still don't know about design patterns (not using them, just knowing about them) I feel sorry for you.
Why are those 4 thing worse no?

Ok, I understand that google search is worse, but it isn't obvious to me that's a result of engineering vs executive choice.
It's a fully client-side app with one HTML doc and one JavaScript file, both of which come back with 304s once you've been there once. I'm willing to bet the monthly "infrastructure costs" are less than the cost of a pizza.
I think it is positive example. Creation for sake of creation not to profit. I really wish more of Internet were to go back to that.
This would be great resource for creating a DL/AI course. Or chapter quizzes for such a course.

However, one of the important things when interviewing someone is that the person has not seen the question before. So as an interviewer my impulse would be to first ensure that my question is NOT in this book :)

Or perhaps even if it is in the book, if the question is advanced enough, I could test how they articulate and reason through the solution, so I know they are not simply regurgitating the answer?
Typed Template Haskell in GHC 9
> Looks like a great tool!

Thanks! I spent over 8 years working on it, I am still improving it :)

There is a page regarding privacy here: https://docs.uxwizz.com/about/personal-data-information

> I see that it tracks IP addresses, is that legal

My specific instance of UXWizz does not track IP addresses (you can disable that in the tracking settings), but only a hash of the IP+User Agent.

As for the privacy laws regarding tracking IP addresses, it's not very clear whether it requires consent or not as the law is ambiguous. The IP itself alone can not be directly considered personally identifiable information (PII) as having an IP address only, can not define which real person is the data associated with. Another thing to consider regarding IP addresses is that by default almost all services/servers/devices have an access log that does store IP addresses in plain text, so even if UXWizz does not store the IP, your OS/server/router/ISP might do.

> where people don't respond or opt out of eu cookie consent

As explained in the documentation above, UXWizz does not use any cross-session persistent storage on the user's system (not cookies nor localStorage).
Also, being self-hosted, no data is shared with/sent to 3rd parties.

If you need more detailed answers or want a deeper discussion on this subject you can contact me on Twitter or via the contact form on uxwizz.com.
As an example: My father (living in Germany) installed a 10 kWp photovoltaic system in spring last year along with a 10 kWh battery. In the summer months he was almost self-sufficient with that, as he could use his own solar power at night or on rainy days. The forecast for the whole year is ca. 65% self-sufficiency.

So local storage reduces the amount of both the power taken from and provided to the grid and therefore is beneficial for grid stability.

The problems start, when the storage is not local anymore, that is when the power surplus is not at the same location as the storage itself.
A few examples:
When the sun is shining your electric car is probably at the parking lot of your workplace and you can't store the output of your PV system.
Or when it's a rainy day, you and also all other households in a wide area around you, wont' produce much power. Then the power has to come from somewhere else, e.g. a sunnier place, offshore wind or gas power plants.

So to use all the distributed storage effectively, you have to route the power around a lot, which probably makes changes in the power grid inevitable.
How much one has to invest in the grid and how that relates to the overall power price is probably a very complex topic depending on a lot of variables including geography, power mix and cost of storage.
Probably over decade...

But more interesting is mine brother story. Before little bro was on Windows and frequently install-uninstall software. So on every 2-3 months he was make fresh install with format drive.
Then i show him Linux (Ubuntu TBH) and he join club "Years without reinstall".
Regulating oneself out from the market where main merchandize is people's private data sounds like reasonable thing to do.
It’s all the same shit. It’s just matter of your tolerance level for corporate b.s or startup b.s. The only thing about a vanilla big co is that it starts to look really lame (even to yourself) on a resume if you are in the 3+ year range. You start to feel icky, sort of like ‘oh geez am I really one of these h1b Fortune 500 shills now?’. The same goes for being at a startup for too long, then it becomes ‘oh geez am I really one of these wide eyed douchebags now that believes I have ownership and autonomy or some shit?’.

The most important thing I think a developer can do is remain compelling in the job market on your own two feet. While your mom may look at Microsoft and see it as some stable lottery ticket for life, in reality it can make you look less robust. That’s doubly so for a typical big co that doesn’t have the pedigree of Microsoft. My mom would probably say the same for my company, as in it’s well known - so what’s the problem? The problem is it looks lame past a certain point and she has no idea the nonsense involved in this job market.

For every person that joins a startup thinking they will have ownership, autonomy, or whatever else you can concoct, there is also a counter party that is leaving at the same time saying there was no ownership, autonomy, etc. It’s all perception. As you leave Microsoft, someone else is entering wide eyed.

It’s all just a giant game, so keep that track record fresh!
Ever since a bigoted scoundrel had to resign as CEO of Mozilla by trying to deny humans theirs rights, HN always has a generally negative view of Firefox. Just notice the outrage on the paltry 2 million salary of their CEO, while the same people will come to defend multi milion dollar salaries of white male CEOs who are far far worse than Mitchell Baker.
You are correct. Fathom Analytics is the only globally distributed provider that offers EU Isolation (keeping EU data completely away from US cloud providers).
https://usefathom.com/features/eu-isolation
It's really not rocket surgery to be compliant with the GDPR if your business model isn't to sell (or profit from) targeted advertisements.

It's not rocket surgery but it's also not trivial. Every time GDPR comes up on HN there are always people saying something very similar to "GDPR compliance is easy if you don't do dodgy stuff" and implying that anyone who thinks it's not a trivial matter must be doing something bad. This is dismissive and often seems to be based on wishful thinking about what these contributors wish the regulatory requirements said instead of what they actually do say.

The GDPR is nearly 100 pages long, in the standard English language printed version, just for the main document without all the supporting material or any additional material published by the individual regulators.

It contains ambiguities that invite broadly applicable questions like what "legitimate interests" actually means in practice.

It contains requirements to document various information and processes and to share that documentation with various parties under various conditions.

It contains provisions that could potentially conflict with other good practices (for example, the use of tamper-proof data structures for auditing or the use of diverse backup strategies for resilience) again with ambiguous if any guidance on how to reconcile competing good intentions. You can argue that this point is a stretch because it's unlikely any regulator would actually go after a data controller or data processor that was obviously doing reasonable things and trying to comply, but we are talking about legal obligations and the penalties that can be imposed are an existential threat to any small business so I think caution is fair here.

Ask a lawyer -- a real one who is an expert dealing with these kinds of regulatory compliance all the time -- how easy it is for any organisation to be sure it is fully compliant in this kind of environment, even if it has no interest in doing anything that anyone is actually likely to object to, and even if the people responsible for running it have nothing but good intentions. I doubt you're going to see the kind of one-sentence "It'll all be fine, just don't do anything dodgy" reaction we often see posted in HN discussions about the GDPR.
Now this is a scary disease. Any suspicions to the cause? Poisoning? Directed EM fields? Common health threat we weren't aware of?

An attack with microwaves wouldn't be that new, I believe there were some occurrences.