skysight-inc/HackerNews huggingface dataset:
> When a player is earning $10 every 4-6 hours by automating chopping logs, that's a sign that some of your playerbase isn't enjoying what's happening to them. They're sending the clearest possible economic signal they can that the grind isn't a positive or rewarding experience for them.

Unfortunately, in the scope of Runescape, this misses the point in a big way. Runescape has a robust economy where every action can be measured in gold and experience per hour (when played efficiently). Someone might be buying magic logs for gold because cutting them down is a poor choice for them from an opportunity cost perspective (i.e. they can make more gold per hour via other activities their character has access to).

Zooming out, the system is actually incredible if you get a chance to analyze it a bit more. For the hardest of the hardcore players, there's a resource called CrystalMathLabs[0] that shows exactly how much time and gold it costs to max your character. And the devs are constantly optimizing new content around these "max efficiency" rates.

0: https://crystalmathlabs.com/tracker/suppliescalc.php
Just changing time_t to an unsigned int would take us all the way out to 2106.

This has seemed to be an unpopular observation, in the past.
I feel this is like a Reddit detective moment. Almost everyone here is going to have uBlock Origin installed.
I don't know what you think you're adding to the conversation here. The point of the auto insurance system as mandated by governments, including the "required liability" part, is to rise a bit above (or a "smidge above" as you might say) this folksy "it is what it is" nihilism.
An overview of rare allergic reactions to Vitamin D
You are leaving out the point that we have practically limitless energy in the form of solar, wind, and nuclear. It's inevitable, the oil companies can't block it forever.
I think the best way of doing this is a 4 step approach:

1. Old situation, time_t is 32-bit

2. Migration starts, time_t is 32-bit by default, -D_TIME_BITS=64 to get 64-bits

3. Migration continues, time_t is 64-bit by default, -D_TIME_BITS=32 to get 32-bits

4. New situation, time_t is 64-bit

And with a long time between these steps. So glibc is at step 2 while musl skipped step 2 and is at step 3. There should be plenty of time between steps. It might make sense to keep it at step 3 until 2037 or so for very restrictive embedded plaforms etc.
So… then you can’t use it to heat other rooms.

That’s not an advantage.
Just quoting the whole sentence shows that that's not what they meant:

> "Reducing surface area for conflict" is one of many steps on the way to the goal for profit, and if cutting out Colorado is less painful to profits than disclosing salaries and opening up that conflict surface, then that's naturally what will happen.
Because if they didn't Average Bob would feel like they're missing out.

Some people don't care about 4K. Other people think they care about 4K but don't really know the difference.
This is awfully close to arguing for lower life expectancies.
Saw this on my twitter feed. Just came by to wish you good luck! When will the boards be available for purchase? Can you post the cost and specs? Alles gute und danke!
Not a PhD just a MSc, but the presentation skill I picked up along the way was definitely the most important thing I got out of it.

To paraphrase the words of my professor: if I really understand something, I must be able to explain it to any audience in 2 seconds, 2 minutes, or 2 hours.
Christmas without a Die Hard?
That’s still a breaking change, although somewhat less of a break. Better to just do it right.
Lots of code would break because they assume they can do signed math with time_t, though. It's a less invasive change to make it wider: largely, it's just a recompile, except for code that persists a time_t directly or sends it directly over the network (and both of these should be considered harmful for other reasons).

The other problem is that more unsafe code in libraries, etc, will happily cooperate with 2038-safe unsigned time_t code, but will start to do bad things shortly before 2038.
Did you try https://pydoit.org/, it's a build tool in similar spirit, which allows the actions to be either python-functions or external programs. Try to look past their tutorial 1, I don't know why they mixed in module_imports there, making it look a lot more complicated than what it really is.
Hah, this is quite ignorant and I really appreciate you were willing to share it! :)

I think every kid should get one of those sets of 50-52 books about the states (plus DC and PR) to pore over.
Silly question, but if a heat pump extracts warmth out of the ground, how much extraction can take place before that warmth runs out?

Quantitatively, of course planet Earth has infinite warmth to give compared to what we could possibly extract but I have no idea what the numbers are actually like.
The EFF really makes a contribution to the world way out of size with their budget. The EFF's budget in 2019 was only $10 million dollars. Kudos for them.

https://apps.irs.gov/pub/epostcard/cor/043091431_202006_990_...
I don’t think they were assuming eSIMs provide a new type of connectivity. I think they were referring to the fact that these embedded SIMs are more integrated into the device and therefore physically agnostic to the mobile operator of choice. This would make switching from e.g. Verizon to Apple like switching from from Netflix to Disney+ – much easier since it’s fully software-based. For Apple that would be easy to bundle with the rest of their services. Yet another thing that will retain customers in their ecosystem.
> Except all you earn is worthless non-exchangeable karma.

I think you look at it the wrong way:

For me that "karma" counter on the profile only roughly signals someones worth here: it might either be because they've been helping others for a long time or it might be because of tactical posting of a few interesting stories ahead if everyone else or even just grinding by trying out a couple of (non spam) stories a day or something.

The real value of HN comes from what I have learned over the years, and for many others from the business opportunities they have found as well.

Bonus: I think the only real value of those stupid internet points is to look at threads and see which ones are getting upvoted or downvoted.

If they are upvoted it signals that people found them useful.

If nothing happens that either means the comment was seen by others as correct but not very interesting or few people read it because discussion moved elsewhere.

If they get downvoted then either they:

- said something mean

- was wrong

- said something widely believed to be wrong

- wrote in a way that made people misunderstand your otherwise correct explanation

- you poked a wasps nest, saying something correct that angered many easily angered individuals.

In fact I think we could (not should) remove the accumulated scores from profiles and not lose much of value (though I think many glances profiles sometimes to get a feel for who the person they talk to are).
KeePass or PasswordSafe, and some means of synchronization.

None of these opaque, closed-source "cloud" password managers. Because if you don't control your secrets, then you don't have anything. I don't care if it's a zero-knowledge construction approved by Big Name Cryptography Guy or best intentioned founders since depending on a single service that could potentially hold your secrets hostage, expose them, or forget them would be insane.

The end.
VR, VFIO and how latency ruined everything
SigNoz (YC W21) Is Hiring Senior Go Engineers to Build Open Source APM
Huh, til. I had a little Crayola brand camera that fit APS cartridges as a kid, and I had just lived my whole life assuming disposables had a similar "not quite" size film inside.

I also haven't actually seen any of those pictures in nearly a decade, because my family lost a storage unit at some point that apparently had all my childhood memorabilia in it. I'm probably remembering them worse than they were.
The Tokamak hype machine is in overdrive. But no commercially viable power will ever be generated with a Tokamak. Such a reactor would be much more expensive to operate than a fission plant, and fission plants get less competitive every year.

We may hope that the plasma physicists employed on these projects are learning things that will later be applicable to actually-practical fusion. It seems like a Good Thing to be keeping plasma physicists employed, but I hope the crash when reality catches up to the projects does not leave them suddenly unemployed, as has often happened to (particularly) aeronautical and electrical engineers over the past 60 years.
Exactly. Annexing parts of Ukraine, and then complaining that Ukraine joining a defensive alliance is a threat is beyond absurd.

If they didn't want Ukraine to join NATO, maybe Russia shouldn't have gone out and demonstrated to the entire world precisely why Ukraine needs NATO protection.
The pithy summary of your views could be, “because it’s not in the company’s best interest”.
DMCA takedown kind request in 3, 2, 1…
> Looking at the current job listings on your company's career section will be the very first thing that everyone will do if those salaries were to be made public.

This right here I think is the real reason companies do not disclose compensation in their listings. Their current employees fall below the range and they do not want them to know. This is unfortunately a widespread problem in tech, where companies constantly offer more for new hires than what they pay their own employees for the same work. The new hires that have joined will then find themselves in the same position next year when their compensation falls below what someone will be hired at that year! And the cycle continues. It's absolute madness if you look at it from the big picture perspective and there are some fundamental problems with the way HR orgs are structured that need to change. From an employee perspective, the most optimal thing you can do for yourself is to move companies frequently and that is the reason for the crazy churn we see in this industry.
The tradeoff there is that you would be unable to use time_t to express times before 1 Jan 1970 (iinm). That may or may not be important depending on use case.
Almost any internal part of a large machine would be inscrutable. Most are inscrutable even now. If you handed an automobile carburetor to a person under 35 they would struggle to identify it, and even if you handed it to a car mechanic, 25 or younger, they would struggle to identify it, as fuel injection became standard by the 1990s and old cars with carburetors largely vanished by 2010 or 2015. And yet anyone 50 or older will remember seeing them in their cars any time they popped the hood.

A central fuse box has been standard in all new homes since at least 1945 if not 1930, so if you hand someone a disposable fuse from 1930, would they be able to guess the purpose?

My dad was a photographer from 1950 to 2007 and he kept the "dark room" in the basement of our house, a large room full of thousands of objects. He was an expert and dodging and burning, decades before Photoshop. He created his own tools for the dodging and burning, typically by taking a coat hanger and bending to the right shape, then attaching some cardboard and wrapping it with tape. It was a specialist tool and even in 1970 or so, 99.99% of the people on the planet would not have been able to guess the purpose.
> For some reason this page uses ~200KB of javascript, but I don't understand why there is any JS on this page besides analytics. It also puts up a message if javascript is disable.

Menus, at least. They behave consistently with the rest of Apple web properties so I’d assume even with code splitting they’re on every page.
Good read as I've heard/seen relatively few people fully automate their homes. There definitely are a lot of snags and Alexa/Amazon has their own share after watching my dad spend a few hours trying to integrate a stereo in with his many Alexa devices. We have a long way to go for sure.
Oops. That should read: "In isolation, it isn't."
Another tradeoff is that you can't just subtract two time_t's and get a negative value for an interval. I'd wager this is a far more common problem.

E.g. you can't do...

time_t completion = time(NULL) + 30;

do {
time_t remaining = completion - time(NULL);

/* ... */
} while (remaining > 0);

Without risking a sporadic infinite loop.
Some examples would be appreciated, please.
they count on you to price it against going to the movies and a lot of people (particularly families) choose to stay home and spend 1/5 to 1/10 what they would have spend going to the theater
> Runescape has a robust economy where every action can be measured in gold and experience per hour (when played efficiently). Someone might be buying magic logs for gold because cutting them down is a poor choice for them from an opportunity cost perspective (i.e. they can make more gold per hour via other activities their character has access to).

I don't think this holds up when real-world money enters the equation. I don't think this can be accurately descriped as player optimization or class specialization if people are paying real money to skip it.

> they can make more gold per hour via other activities their character has access to

If this was actually true, no real-world money would be entering the system, because all of the players would be making enough gold in-game via those other activities to pay for the logs. If they're being forced to spend real-world money, then the other activities they're engaged with are not giving them enough gold to sustainably fund themselves in-game.

The problem isn't having an in-game economy, in-game economies are great. The problem is people paying to get rid of gameplay. People who do that are signaling very clearly that they believe there is monetary value in removing a section of gameplay from the game. Designers should pay attention to that signal.

----

I don't doubt that there are people legitimately having fun playing Runecraft. But it can't be everyone, or else people would not pay $10 to remove less than a day's worth of grind.
My parents have a “propaganda” book written about the US by the Soviets back in the ‘70s (it’s a Romanian translation, I’m from Romania) which was quite spot on, meaning it was quite on point when it came to the Vietnam War, the condition of the black population in the States, the homelessness issue (this last one scared me the most, as we didn’t really have homelessness on this side of the Wall back then). All this to say that from time to time they were on point, but, I agree, when it came to internal stuff pretty much all of it was besides the truth.
Not a christmas I want any part of.
I suspect, though I have no documentation, that they are generally built with "cleanout" access points along the exhaust path (possibly in the form of "these are the stones to chisel out if the thing needs cleaning; be sure to mortar them back into place when you are done!")
My friend, I think you've got this humanity stuff figured out.
The solution here is to simply not use dynamic linking for anything outside glibc and openssl. If your program is statically linked, or if each program ships all the dynamic libraries it links against, this compatibility problem disappears.
Static linking doesn't fix it. You still need to know how every library you use was built, and choose the same setting.
Luvoir Space Observatory
Miners have real expenses: electricity, depreciation, etc. Miners also generarte revenue, $45 million per day is a reasonable estimate [1]. This revenue is extracted from the Bitcoin system through both transaction fees and inflation (creating new Bitcoins), but these are sold in portion to pay real expenses, with presumably some profit.

We can estimate 300k transactions per day, which implies about $150 revenue per transaction. Miner revenue is your cost: it is what they extract from the Bitcoin system.

One Bitcoin transaction costs on the order of $150. It's really expensive.

1: https://www.blockchain.com/charts/miners-revenue
Right. So exactly the same is true of stocks when it comes to trading existing stock. The key difference is the creation of stock - IPOs. The company uses that money they get from the IPO and invests it into the business, which results in profits, which they give out as dividends. There's no such mechanism in cryptocurrency.

Unfortunately the other side has a good response to this - if the dollar value of buybacks+dividends exceeds the dollar value of IPO's, then you end up with the same problem that Bitcoin is in, where it's a net loss system. That seems to be the case[0]. This is not a well known fact.

Ultimately this comes down to the fact that we don't have a stable velocity of dollars, and an unstable velocity that results in more dollars chasing less more goods produces speculative bubbles that must eventually crash and create recessions.

All investments, including all currency, whether it be stocks or gold or bitcoin or dollars, is inherently valueless. The only time you can calculate the value is when you actually are extracting utility. You can then work back from that to determine who produced that value.

[0, Figure 5/Figure 8]: https://www.yardeni.com/pub/buybackdiv.pdf
It is a problem with the insurance, as it would be for anyone else. Shitty tactics are not exclusive to insurance, but that doesn't negate their actions, or the expectation that they should perform better.
Specifically: For bash, `set completion-ignore-case on` in ~/.inputrc, for zsh ... I have `zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z}'`, which seems too complicated but that's what's in my zshrc.
https://plato.stanford.edu/entries/panpsychism/

And for a fun magazine read: https://www.noemamag.com/the-conscious-universe/
And you'd think people understood exponential growth after covid. But then I remembered that a sizeable part of the US electorate doesn't think it's real
> enum case with parameters
Ah, this is a language feature of enums in Swift. Swift enums allow you to keep associated values with a specific case and you need to unpack them with a `let` when dealing with that value.

E.g.

enum Animal {
case lion
case tiger
case bear
case ohMy(Int)
}

The case `ohMy(Int)` means that it has an associated value so when you want to get at it from a variable, say:

var a:Animal

switch a {
case .ohMy(let value):
// do something with `value`
...
}
I blog to share knowledge. This is akin to contributing to an open source project, but the project is all of human knowledge.
Is phase 2 that useful?

Why would you -D_TIME_BITS to something other than the default? It's a hard thing to do safely, since you're choosing to be ABI incompatible (in a way that's not caught at compile or even invocation time) with the system's default.

And then, all you get is a binary that will potentially handle times past 2038 safely, when the whole rest of the system won't.
I have the middle of the night insomnia that CBT-i doesn't seem to touch.
Depending on how motivated your users are, this could be a difficult battle for you. Even if you use a paid service like MaxMind to identify residential IP addresses, your users can tunnel their traffic through residential proxies to skirt detection.

I’d recommend tackling the issue from another angle if possible.
I'm assuming that you're also building all your dependent libraries as part of your build process, as is common with languages like Rust. Closed source libraries are somewhat out of scope when talking about Linux distributions, though you can always ask the vendor to provide you a 64-bit compatible library.
> There's a good deal of microtransactions where the person spending the money still wants everyone else to have to grind for it.

I'm not sure that having a system that's unpleasant for a portion of the playerbase and letting people pay to pretend that they've gone through it is all that better.

I've commented to the same effect elsewhere, but public prestige systems that can be paid to be bypassed are sort of self-defeating. They only work if a very small portion of the playerbase is cheating, which... I still don't think it's good design to set up gameplay incentives or monetization around a minority of the playerbase pretending to the majority of the other players that they've legitimately earned something.
The http_archive has a sha256-attribute to deal with the "random". You could add multiple urls to point to your local mirror as well. It's a way to pin external dependencies and get reproducible builds without checking in a big blob into your git. pkg-config in my experience is less reproducible and tends to pollute and be affected by system environment, unless you have some build guru who can setup chroot in your project.
First they take the dinglebop, and they smooth it out with a bunch of schleem. The schleem is then repurposed for later batches. They take the dinglebop and push it through the krumbo, where the fleeb is rubbed against it. It's important that the fleeb is rubbed, because the fleeb has all of the fleeb juice. Then a schlomi shows up, and rubs it, and spits on it. They cut the fleeb. There are several hizzards in the way. The blamphs rub against the trumbles, and the plubus and grumbo are shaved away. That leaves you with a regular old plumbus.
"Daycare for adults" is how a coworker described a particularly dysfunctional government agency.
Summary once again, because I think you're going in a roundabout way.

You assume:

a) Companies will by necessity pay people doing ostensibly the same thing different amounts of money

b) People do not necessarily wish for their salary to be made public

c) Making a salary range requires the lower and upper bound to be equidistant from the expected starting pay

d) Making too narrow a salary range would therefore reveal pay, in contradiction to b).

Therefore, it is a necessity of employees' desired privacy and employers' ability to advertise the lowest, er, "most competitive" wage possible for the company to have a wide salary range.

EDIT to add: I think your argument still falls a little flat, because salary ranges should still be accurate. "We would consider hiring someone with slightly less resume experience for the bottom range, we would hire a rockstar demigod at the highend, and just what we're looking for somewhere around the middle".
J2ME was so bad that it once made me throw my Sony Ericsson soap bar shaped cell phone down on the floor so hard in furious anger and frustration that I smashed it, and it felt so wonderful, and was well worth it.
I confirm this. It's also true that they seem to be the only users of SMSes now. People are using WhatsApp or Telegram or Messenger, roughly 90-9-1 in my experience (Italy.) Cost is not the issue because plans include at least hundreds of SMS if they are not unlimited. It's functionality: pictures, vocals, videos, multi user chats, etc.
In India, I feel the same about Chartered accountants and Lawyers. Not trying to dismiss their knowledge and expertise, but it is crazy the amount of stuff you can do yourself in this day and age but still need their signature. Low key I feel the same about some of the lower skilled Doctors too, although it is a very different ball game risk wise.
An extra (small seeming) refresher doesn't seem like news?
I'm sure I'm "doing it wrong" but the lights on my homekit, bought directly from Apple, take 5 to 90 seconds to respond and worse, the Home App (by Apple) often gives zero indication it even noticed I pressed a button in the app.

in other words I'll press the off button for a room but there is no indication that it understood me and it's going to turn off the lights, then if I wait 5 to 90 seconds it may eventually turn them off, or not, try again. If I try again at the wrong time, as in just before it was about to actually turn them off then of course it turns them back on, repeat

my guess is apple only tests in some kind of ideal conditions and has no idea their system is so crap in others.