skysight-inc/HackerNews huggingface dataset:
Does anyone know if people have made serious attempts to do objective pain quantification? Of the ideas that come to mind, strategy 1 would be: let the patient press buttons that give her electrical shocks and let the patient say "This shock is worse than my pain, that shock is less bad, therefore my pain is between these two levels". (I once read about an early electrical scientist who would measure voltage by shocking himself and comparing the pain with known quantities. Googling, I find that "Kenneth Catania" has done this very recently to measure eels' output...) Strategy 2 would be to somehow observe pain nerves and/or the brain directly; I don't know if this is possible. Strategy 3 would be to describe hypothetical sources of pain and ask what the patient would prefer, though even a patient trying her best may not be able to correctly compare felt pain vs. imagined pain.

Wikipedia isn't much help[1]. It lists 30+ "pain measurement scales", but clicking a few of them doesn't tell me any specifics about how they work.

Looks like someone has in fact tried strategy 1. https://www.hindawi.com/journals/js/2018/6205896/ mentions: "Recently, a quantitative pain-assessing method using electrical stimulation was introduced [12–15]. PainVision™ devices measure perception threshold and pain produced by an electrical current. This system quantifies pain intensity by comparing the experienced pain with the intensity of electrical perceptions. The perception threshold indicates the minimal electric current sensed by the individual, and the pain produced is defined as the maximal electric current sensed by the individual. However, the skin resistance of an individual may affect the electrical measurement result [16–20]."

Their refinement continues: "our system measures from the patient’s skin resistance before measuring the pain." "In this work, we developed a pain measurement device that has two analysis methods, electrical stimulation and applying pressure, for more accurate cross-validation assessment. During electrical stimulation, electrical stress is applied on a nonpain site and then the observed stress can be compared to pain. ... During the pressure evaluation, pain was assessed by applying pressure on the pain site. Inflammation was induced on the rat’s hind paw by carrageenan, and then the inflamed hind paw was stimulated by a hand-type pressure stimulator. The pressure site was then compared with the inflammation levels." Seems like it might be workable.

[1] https://en.wikipedia.org/wiki/Pain_scale
The only thing that might make Apple improve their documentation is if there was evidence that people started actually abandoning Apple's platforms.

Currently it seems there is a never ending supply of developers ready to gamble years of their careers on Apples Terms & Conditions, and while these same people usually eventually realize that there's ultimately no money to be made, they are replaced with a new generation seeking an AppStore paved with gold. Until that stops, the docs will stay piss-poor.

While I have often used a Mac for development and enjoyed it, I don't often actually develop anything for macOS or iOS because, well, why would I risk my livelihood on Apple's whim? They regularly destroy developer's lives with no thought or consequence.
Water Predictions: Telling When Nanolithography Mold Will Break Through Droplets
We get 1-5% response rates (which is normal; I've done this on a few sites now) but we have enough scale where we're getting enough feedback that I can use the data to identify the worst docs. The basic methodology is to prioritize the pages with the most pageviews + lowest helpfulness scores. Of course there's a risk that we're prioritizing our work based on data that isn't indicative of our overall audience and due to the general nature of the question ("was this page helpful?") we also don't know how exactly the doc is unhelpful but in practice it's usually easy to make an educated guess (e.g. one of the Lighthouse guides is very low rated, and when I checked on it recently I discovered it's just a stub with very little guidance; so the educated guess is to add more guidance to the page; and then a few months from now I can see if the ratings have improved). Another good pattern is to provide a freeform textbox for feedback. The only reason we don't have that is because Gooble considers it PII and I have to jump through hoops to store that data properly.
> Then — as long as there is some program out there that could perform the same task while keeping your password hidden — an indistinguishability obfuscator will be strong enough to successfully mask the password.

I wonder if this will be the Achilles heel. If there were a way to perform a task without needing a secret, you would not be using homomorphic encryption. You could just do regular computation since there is no secret. However, if the only way to perform the computation is with the secret, then Indistinguishability Obsfuscation won't help you. To me it seems that iO is useful only for computations that didn't need homomorphic encryption in the first place, because they already had a way to do the computation without the secret.
I've not had a good experience with them either. I was contributed a bug fix to the std lib which would've been a decent feather in my cap. Not even a thanks; some maintainer copied, pasted, made a few changes, merged "his" fix. 2014 iirc; extinguished my interest.
Yea, exactly. The author's git workflow is eerily like the one I've converged too over a decade, but "never stash" (without acknowledging the existence of the quick stash use-case) is wrong enough that it's enough to give me pause about his general competency with git (or more likely and more charitably, that he just didn't put too much effort into that section of the article).

The advantage of stash is that it's quicker and easier than creating and cleaning up branches. If you're naming stashes and keeping them longterm, then you're basically using them like branches and should consider what benefit you're getting from adding a separate workflow.
I also really dislike that WWDC videos are now the de-facto documentation. It must be a lot of work to put them together – I wish they'd just write a doc instead. Would be way faster to read, search, etc. and could probably go into much greater depth.
> e2e is not a hipaa requirement.

But HIPAA does (iirc) require not having arbitrary third-parties to communication. E2E prevents that, but if there wasn't E2E… fairly sure Zoom isn't meant to be a third-party to therapy sessions.

> by all means, show me all the concrete harm zoom has done.

“Oh, they built houses badly? Show me all the concrete harm that's done.” We might not know until the next (metaphorical) earthquake.
Yes, though the expression “an up round is an up round” has a lot of truth to it. Dilution is important if you care about control, but as long as the stock is worth more on a per-share basis, you’re doing better.

The problem is when people anchor their calculations about their future lottery winnings to the current float.

I try to tamp down expectations when I’m hiring by trying to sketch out a wide range of plausible scenarios (basically the Drake Equation for startups) but I’m going to go out on a limb and guess that a lot of hiring managers and HR departments set new hires up for disappointment by not throwing cold water on their very optimistic math.
Agree with your complaint on async. And on asp.net, async doesn't disrupt that much the workflow (but creates the possibility for deadlocks). But if you are dealing with a UI and make a method async, then suddenly you have a ton more problems to deal with, like what happen if the user changes the state while you are waiting for an async call. That increases a lot the complexity of the code. Which is why I am lukewarm about their approach of mandating async for new features.
I don't know if this is related or not but back when Flickr was popular in like 2005 or 2006 my friends and I were uploading pictures of our events there (they're all still there AFAIK. We'd upload them to either our own accounts or for certain events to a shared account. One shared account is here: https://www.flickr.com/photos/sourpower/albums

I wanted copies of those pictures and the easiest way to get them was the write a tool to download them rather than have to coordinate with 3 to 15 friends and ask them to copy the images to a CD or USB stick or some other nonsense. Dropbox wasn't a thing and not all my friends were tech heads that would want to setup FTP servers.

Flickr had also come out with an API. APIs for online services seemed kind of new at that point and Flickr was one of the first AFAIK.

So I wrote the app https://blog.greggman.com/blog/flickrdown/
and a few months later it was accused by other users of flickr of being solely for the purpose of downloading copywritten images. Not once did I ever use it for such a purpose nor, AFAIK did any of my friends. None of us had any interest in other people's images on flickr, only shared images of mutually attended parties, bbq, picnics, events.

Those users reported the app to Flickr and the app was banned.

It was banned by the app's id. That meant you could register your own app and then hack in your app's id and still use it. IIRC I continued to use it to download pictures from our events but it always pissed me off they banned it. It also pissed me off because it wasn't accessing anything you couldn't just scrape for. The API made it easy to get a list of URLs, search for albums or people etc but you could easily write a script that just scraped the HTML to find all the same data. Didn't matter, flickr didn't budge.

It further pissed me off that over zealous flickr members accused me of lying about its purpose. Like many topics today, there is often absolutely nothing you can say that will convince someone else your intensions are not bad.
I've run into this more often than I can count with Java based things. "Just look at the Javadocs!" You...you mean the auto-generated API descriptors that have exactly zero usage information on them, and expect me to figure out how to piece things together just by type signature? That...that isn't how documentation works.
...I don't make the comments the author is referring to

And yet here we are.
Ironically the US already has tax funded healthcare, but only the most active voting block (old people) receive it.
That's it! Thanks for the tip
I suggest you consider giving them a little benefit of the doubt?

I agree with you that for a larger corporation it makes much more sense for the tool to be prepaid and for the developers to not worry about their usage. There's definitely a learning curve to switching to a new style of debugging, even if you're accustomed to rr, and so encouraging use is more likely to get people to actually get to the point where they're benefiting from the tool.

But that's a tough sales cycle, they've tried it, they've said they would be happy if someone came asking for that. You could make the argument that they should hire an enterprise sales person or something, which may be true but also has obvious costs. (Let's just say that it would be a large percentage increase over their current staffing.)

I'd think that their reality wins out over your "shoulds". You may be right that they're incompetent about selling into the enterprise, but I'm certain that they've had more experience trying to sell Pernosco to larger corporations than you have and so I'm not going to ding them for this additional purchasing opportunity.

Source: I work for a mid-sized company that does have a contract that gives me unlimited access to Pernosco. It's quite useful. I don't know the exact terms. I know I have solved some bugs that I would have been unlikely to ever fix and would be ongoing stability and maintenance concerns.

I'm working on a bug right now where the submitter is able to reproduce easily but I am not. They have managed to capture it in an rr recording, so I'm uploading it to Pernosco to take a look even though my desktop's CPU is mismatched enough that I can't just run the recording myself. From past experience, if I have it in Pernosco, I will be able to fix it, even though the root cause is far far removed from the resulting crash. (It's subtle GC corruption.)
github is owned by Microsoft now, did you try to get your account to normal ?
Was thinking similarly. I don't think there's any guarantee you'll get the particular plane model that is scheduled. Maintenance or other factors may mean model X is unavailable, and they substitute model Y instead. You've contracted to get from point A to point B via plane, that's typically it.
>Cortana

Agreed, Cortana is a big reason to avoid Windows.
> As part of the structure of the deal, Xenon guaranteed I’d take home $3.7m, regardless of what came up during due diligence.

I have never seen this before. Guaranteed outcome regardless of DD. Is this an outlier company?
This is the most annoying trope. Yes, I want color printing. Why wouldn’t I want color printing?

I feel like the “black and white brother laser” attitude is like buying a car with no air conditioning because you’ll save five hundred bucks off the sticker price.

The reason to choose inkjet:

1. Black and white sucks

2. Color lasers are huge and don’t really save money on toner vs. ink for typical home users.

My current printer is an HP OfficeJet 9015, which has been excellent. Zero software needed for Windows 10, iOS (AirPrint), macOS.

Another thing those cheap brother laser printers don’t give you is, you know, features. My inkjet printer has a scanner, auto document feeder with auto duplex, and auto duplex printing.

If you want all that with a color laser you end up with a monstrosity in your house.
Even after months, there is -- fortunately -- no evidence that Covid causes chronic illness except in very rare cases.
Extremely gross that he pocketed $3.7m but asked his investors to walk away from their $800K, because he needed to meet his financial "goals."

This is the flipside of all of the VC deals that completely fuck over the founders.
The paper compares to a group of people diagnosed with influenza (and a number of other things), as a control. For the flu, they find that 13.3% of these people had the same symptoms (vs. 18.8% in the covid cohort; ratio = 1.41). This is in Table 3.

Table 2 shows you the similar analysis, but just for first-time diagnoses, and these are 5.8% (covid) vs. 2.8% (influenza) for a ratio of 2.07. So while there do appear to be differences in the groups, focusing on the absolute percentage in the covid cohort alone is a misleading and fear-mongering way to interpret the results.

https://www.thelancet.com/journals/lanpsy/article/PIIS2215-0...
You are getting down-voted too by people who do not even bother replying, probably some blind followers, government-loving NPCs.

You know how you could turn this against them to make them think twice about it? Get the Russian vaccines, or the Chinese. Yeah, do it! Suddenly they are not so keen... Now imagine if their beloved State made it mandatory to get Russian vaccines inside them. They would most likely be against it, and our votes would not be down... It is not even the votes I give a damn about, but the fact that we do not know THAT much of COVID-19 but people seem to believe the claims that we have extremely safe vaccines ready just within a few months. Yeah, they say that of the Russian vaccines, too, are you going to take it, down-voter? Would you like the State to make it mandatory for your kid to get vaccinated? I am curious.

My entire family tested positive for COVID-19, and my grandma most likely has it. None of us has/had symptoms. I do not want to get vaccinated. If you (not you, the down-voters) really care, go get vaccinated by the Russian vaccines.

My country plans to vaccinate the elderly, kids, and people with chronic diseases first, then the rest of the population. I really, really wonder how many people are going to have FORESEEABLE side-effects. I think they are also planning to make it mandatory.

P.S. I am not an anti-vaxxer, but these claims by pharmaceutical companies sound shady as heck. If they said they found the vaccine after 5 days and they claim it is super safe because 5 people did not die from it within 10 days, would it make you OK the vaccine? Come on. My problem is that. It is too quick, and too many promises of lack of side-effects, and lots of financial interest. For that I do not believe them. We (medical workers) even have to lie about people dying from COVID-19 so we (the hospital) get more funding. How about that? Governments put price control on the tests, which resulted in zero competition as it was not worth it for private businesses to continue testing. How about that?
I don't think there's anything wrong with stashes, but there's another interesting trick that you might want to try for this purpose: commit the dead-end, then immediately make a revert commit. You can even add a rationale in the revert commit message.

The technique is not applicable all the time, but for those instances when you really think it's valuable to preserve the knowledge that was gained in trying and abandoning a particular approach it's great.
Any commits we can refer to, so we can expose this situation for potential contributors?
The only restriction here is selling Micro as a Service e.g AWS can't pick up and sell Micro. This is a common problem in the open source industry and Polyform is trying to create licensing standardisation rather than everyone hand crafting something. For larger orgs in the long term being able to approve a common license rather than 100 bespoke ones.
Color Your Word a Creativity Outlet for Nerdy Adults – Lawrence Jean-Louis
Four principles to ensure hybrid work is productive work
Fun fact: Vieques was a US Navy bombing range for 60 years, which included several cases where Navy planes accidentally dropped bombs on civilian homes nearby.

https://www.theatlantic.com/politics/archive/2016/09/vieques...
Avo's Ultimate Tracking Plan Template (With Downloadable Worksheet)
Thanks for this. It is weird how long it’s been. I totally forgot that Wireshark was once called Ethereal.

I hope that the DMCA takedown issue can be resolved reasonably, but it’s starting to seem more and more like a move off of Github is overdue. Especially in a world where anyone can stand up a Gitea or Gitlab CE instance.
> However a gap of only 20k votes. 99% votes in out of 3.2 mil So up to ~300K still left to count.

No, 1% of 3.2 million is 32,000 not ~300,000.

So, to make up a 20K deficit, the remaining ballots would need to break about 4:1 for Trump. (And the realistic shift for a recount is small enough, that it isn't meaningfully different if you were only concerned with what it would take for it to be within that range, either.)

> And still conceivable it could flip on recount if its close.

Sure, if it was within a couple hundred votes, it might. But it isn't, and it won't be.
Well they defintely don't work on Linux which is the point and I definetely can't play them. I personally left a negative review and removed the game until the patch was removed.

Whether the anti-cheat should be there isn't the issue. The issue is "does this stop the game from running on Linux". The answer was yes it does.

For a lot of people the only reason they buy a PC is to play games. So you might be okay saying "well I don't care about those titles" but for a lot of people those big titles with shitty DRM is literally the reason they bought the PC in the first place and saying the concern was absurd is just incorrect.
LumoSQL: Making it possible to add new back ends to SQLite
‘Stop the Steal’ supporters, restrained by Facebook, turn to Parler
It needs to have more conceptual articles with code listings like this https://developer.apple.com/documentation/swiftui/managing-m....
Ask HN: What's the smallest headcount for a tech IPO?
I started wondering about the extreme outliers in tech startups, and I remember that when Instagram was acquired for $1B they had ~10 employees, and that there was talk that they could have gone public at the time instead. Was that actually true?

Regardless of Instagram in particular, what's the minimum size for a company going public?
Fun newsletter about the real-world science behind science fiction
They are! We had a basic laser printer at work and even with 20 people printing everyday it rarely had issues.

Even the (5+ year old) HP laser printers are still solid. I've had a little one for 12 years and maybe change the $50 toner cartridge once a year. It would probably be less if i wasn't printing research docs to read for school.

Basically fuck ink jets. I email files to the local printer if I need a color document.
I am confused as to why "repair the thing before it catastrophically fails" is not the best of the available options. Decommissioning a facility like this is a loss for science globally, even if there are alternatives available. Telescope time is precious.
So you want to pause the thread and keep it from processing other requests for simplicity?
If you really want to see people humble-bragging about their salaries go to Blind.
I think the second one applies but I don't see how indistinguishability obfuscation could allow for the first.
> usually there's no guarantee of progress

I think lock free guarantees that at least 1 thread will make progress.

https://en.wikipedia.org/wiki/Non-blocking_algorithm#Lock-fr...
You can avoid much of the download suck by making a (steam client) backup of your games from the windows system, then restoring that backup onto the linux system.

AFAIK that will avoid re-download of most of the shared assets where possible. You may have to start the install of things on the new steam client, then pause them, before it will let you restore the backups.
It's also very hard to get in the minds of the developers who rely on the API/tool and create documentation that mirrors their mental models, background, language usage, etc.

With Chrome DevTools (I wrote/maintained pretty much all the official docs for about 3 years) it was a bit easier because I had a huge repository of direct user experience to draw from: the thousands of Stack Overflow questions about DevTools
Suppose I have a function which returns input + 42. I wish to obfuscate that function so that no one can determine how I arrived at the result, even if they themselves are executing the program.

In simple terms, why is FHE different from iO? I’ve read your reply a few times, but I don’t understand the concrete distinction. What is the “best possible result” of input + 42 obfuscatabiliry?

Note that I am using + 42 as a trivial example; please mentally substitute with “for example, a bunch of matrix operations to compute a super secret formula result.”