skysight-inc/HackerNews huggingface dataset:
Trump EPA won't limit 2 toxic chemicals in drinking water
> When Lennart Poettering started thinking about the problem, he first looked at Upstart, which was an event-based system that was still based around scripts, but he concluded that he could do a better job.

I think I'd like systemd more if I had more confidence that he had done a better job.

I never really understood why Upstart didn't get more traction; was it just the Canonical backing made other distros avoid it, or did it have drawbacks I never ran across?
If you mean a rotatable (dive) bezel, you’re looking for something very very specific. Also, if you take it surfing, you’d want screw down pushers if the watch is expensive. Even if you find a watch matching these specs, it probably won’t be what you want in terms of quality, looks, fit, or price. You should broaden your search.
If FaceTime is implemented the way the parent comment mentions (which it very well may not) I don't see why you could make a client that performs a proper key exchange to set up an end-to-end call and simply pretend grab the video instead of hiding it behind the "dailing" screen?
I literally said the exact opposite of what you claim I said. Sometimes when I get riled up online it's helpful to take some deep breaths and come back to it later.
> When you have to go so far out of your normal mode of interacting with a device such that the User has to tear apart developer documentation

1. Download the APK from the website.

2. Tap on the downloaded notification.

3. Follow prompts.

It's just as easy as it is on any other computer to the point where F-Droid just has a download button on its website and needs no explanation for what to do after the download completes.
The snaps have ALWAYS been permanent. They are just not shown on your phone after a certain window of time.
Just thinking out loud here - why isn't there legislation that makes it mandatory for phone manufacturers to send out a notification to all devices affected by serious security flaws (like this one)? Not only will fixing and rolling out an update take a while, there is also no guarantee that the update will be installed. Meanwhile, hackers will have a field day.

Or maybe there is already one, and I'm blissfully ignorant!
Ask iXsystems. They run FreeNAS to sell hardware and support.
Indeed. Early systemd was a fucking dumpster fire and part of the reason I no longer use Linux.
I am not speaking about dedicated security teams. What security training is there for end-user app developers at Apple? From discussions with developers I know, it doesn't seem to exist, or at least not spread everywhere.
Systemd just makes things worse.

I remeber seeing someone post one of the simplest init process one could write. It was only about 100 lines of C.
https://news.ycombinator.com/item?id=19021350
You do not have "this", an OLED panel, in your XPS 15.
No, unfortunately it only simplifies the use of existing notification services.

I don't recall supporting a service that does that though. Perhaps I need a wrapper for Twilio? That service may at least allow text messages to the specific China phones you speak of... Not sure though.
Are you suggesting that the silent switch also turns off the camera and microphone?
Yeah, that's my point ;)
I hate how he talks about knee-jerk reactions to change. because I don't think that's what's going on here. I remember I first saw systemd on a release of opensuse. I didn't think anything of it at first, except that I didn't really like the command line interface (systemctl) and I found the flags and options cumbersome. I often see new software in new releases (including the old HAL/DBUS layer) and didn't have the same reactions (although HAL had a lot of issues and was later removed or merged into dbus).

I've seen the BSD talk on this and I agree, having a system layer is helpful. It'd be nice if it was plugable, NetworkManager (or others that have some standard messages you can send/get via dbus), consolekit OR logind, etc.

systemd does make it nice that I only have to write startup/shutdown scripts once for each distro, but I'm not happy with the layout of target files, the way mounts are handled, some of the weird race conditions I've found between systemd mount targets and fstab, etc.

systemd is modular, but the modules are still all part of the whole and are not easily replaceable. The same can be said when Docker went to a modeler refactor, but there are alternative implementations of the entire docker engine. Every attempt to create alternative implementations of systemd have eventually gone unmaintained because systemd keeps getting more and more complex and engulfing more systems.

If it wasn't for distros like Void, Gentoo, Alpine, Slackware, et. al, we'd no longer have a choice at all. There would be some things that simply couldn't be deployed on embedded systems because all of the dbus shims just wouldn't exist.

It's not that people are opposed to change, it's that there are legit concerns about some of the ways systemd works and is implemented, and the way it's been ham-fisted as a political move in a lot of ways.

Honestly, I don't think it will matter in a few years. I think the way things are going, eventually all services will be hosted via docker containers and it will be much easier to make Linux distros that have a tiny init layer that just launches a docker daemon and services. RacherOS already does this, with the init process being a container, which can be uses to start up shell environment containers and other service containers.
When the specification is defined by the program, it cannot have bugs.
The CLI is self-documenting. xyz --help, -h or --help | grep 'abc', along with man xyz gives you everything you need to know.

This is probably one of my favorite things about the CLI versus GUI. There is nothing worse than working with cli apps that have weird incantations.
Frankly, I’m totaly in favour of hardware interrupt switches for the camera/mic - but I think I understand why it’s not likely to happen. First, to a lot of people it will look like admitting your thing is hackable, which makes it seem vulnerable. Second, now every time I accept a call I have to check this switch - sounds like a switch most people will leave in the on-position 100% of the time and then when it accidentally gets flicked they’ll bring their phone to the Apple store because “it’s broken”.

Also, I don’t want my ringer to have to be on any time I take a call... but that’s just a debate about if it should be one switch or two.

Also the hardware switch doesn’t interrupt the speaker, it just turns the ringer to silent/vibrate mode - you can put someone on speakerphone or play music with it on.
I think Tumblr might be one of the worst examples you could cite if you're talking about successful social networks. Especially in 2019.
Will happily concur with the many voices in this thread advocating a visit. The Prado is absolutely one of the world's great gallery experiences. Make sure to check out Hieronymus Bosch's triptych 'Garden of Earthly Delights' which they've thoughtfully placed a sofa in front of so you can really sit and enjoy it.
Several hours to a day, depending on how many components fail to build.
Can someone please help me understand what common re-vesting schedules are for founders? Like, if I raise seed money, surely I'll have to agree to a reasonable 4-year vesting schedule. But then if I raise a series A, B, and C, do I have to agree to new vesting schedules at each raise? Will I then not fully vest until 4 years after my series C? Do I lose all my vested shares at each raise? On the one hand re-vesting seems unfair to me, but on the other hand if I were to give someone 20 million dollars I wouldn't want them to quit the next day.

Also, sometimes you hear about founders being fired by their board. In this case, are they getting fully vested or are they just leaving with the equity they had vested at that point in time?
A well-written, thoughtful article, worth the read.

> Nerds have a complicated relationship to change; it's awesome when we are the ones creating the change, but it's untrustworthy when it comes from outside.
We started getting cash about 4-6 weeks in. We were also lucky that the app went viral fast.
Large swathes of the US now have an ALDI supermarket where you can buy genuine German schwarzbrot. Much tastier than psyllium husk in orange juice, although fans of white bread will find it a bit chewy at the beginning.
fred hebert (monocqc) has his actual book out just now on Amazon, iirc

https://www.amazon.com/gp/product/1680506218
Germany to close all 84 of its coal-fired power plants
I am not sure if the phrase "They can rally up support from their allies" is not quite accurate, more like arm twisting (like when we bullied our allies to not join One Belt One Road and even our staunchest allies like Israel and South Korea jumped on board with the OBOR).

However, I agree with you, the arrest of Meng did seem unreal.

I consider myself to be very patriotic and I want my country (USA) to do whatever it takes to be truly competitive: more money for education, tax credits for primary research, etc., etc. But I don't like the thing with Huawei because it seems like we are fighting an economic fight with bullying - and not what will help us long term which is building tech excellance.
> Build every part of the application then suddenly "Oh Right! CSS!" Slap bootstrap or other popular framework then don't think about it.

It depends on the problem your trying to solve, if you just want something that looks decent (because you're a programmer and you don't notice things like colors, alignment and spacing) then something like bootstrap is a good go-to.

I still think learning CSS properly is worth it, using bootstrap without knowing CSS is like using an ORM without knowing SQL, but less dangerous.
Goodluck with that holding up in court.

I think docusign has the best sustinct summary of the bare requirements needed for a electronicly signed document to be recognized as legally binding.

https://www.docusign.com/learn/us-electronic-signature-laws-...
Show HN: Superbowl Squares
I'm in my mid-30s and I worry about this a lot too. This age has no concept of human lifespan.
I'm pretty sure there are a lot of Apple engineers evaluating and testing fixes (including this one) as we speak.
To provide a counterpoint:

- Fiber doesn't ward off colon cancer, according to the Harvard School of Public Health: "For years, Americans have been told to consume a high-fiber diet to lower the risk of colon cancer [...] Larger and better-designed studies have failed to show a link between fiber and colon cancer."

- Fiber doesn't reduce the risk of heart disease, according to the American Heart Association: "A fiber supplement added to a diet otherwise high in saturated fat and cholesterol provides dubious cardiovascular advantage." Furthermore, these supplements caused "reduced mineral absorption and a myriad of gastrointestinal disturbances" - factors that in fact, contribute to heart disease.

- Fiber doesn't prevent breast cancer either, according to the U.S. Center for Disease Control and Prevention. In fact, it's the complete opposite: "Carbohydrate intake was positively associated with breast cancer risk." Fiber happens to be a carbohydrate too, and carbohydrates are the only food that contains fiber.

- Fiber doesn't counteract diabetes, according to the Harvard School of Public Health: "Fiber intake has also been linked with the metabolic syndrome, a constellation of factors that increases the chances of developing heart disease and diabetes." Truth is, fiber requires more insulin or drugs to control blood sugar, and makes diabetes even more devastating.

(excerpts from Fiber Menace by Konstantin Monastyrsky)
Our client was impressed with your skills and you are a perfect fit for the team, however your Angular 3.46 knowledge was not enough to consider you for this role at this moment. Please, feel free to re-apply! :)
man while i'm reading this... answer your mom regarding her question.... we don't fly over the north pole becuse the fuel frezes...
altrogh it's possible it'smuch more dangerous and expensive...
If it's a client-side fix then I won't be surprised if it does take that long.
Adobe still gets a piece of the pie with their stupid certificate extortion scheme.

Want a green check box in reader, provider cumbersome instructions for your end users to trust public cert .
Or pay adobe their annual fee for a special signing cert..
Link above is for originating location in Portland. They're also located in some other places:

Minneapolis: http://freegeektwincities.org/

Chicago: http://freegeekchicago.org/

Providence: http://www.freegeekprovidence.org/

Fayetteville, AR: https://www.freegeekarkansas.org/

Toronto: https://www.freegeektoronto.org/

Detroit: https://motorcityfreegeek.net/

etc.

https://en.wikipedia.org/wiki/Free_Geek
What you're dealing with fits in the crux of my problem with systemd. They've made a series of assumptions about how things will be on a system, and if that doesn't match your reality, well terribly sorry, adjust your reality, even if it's not possible, or realistic.

Unfortunately, unlike before, you can't easily just cut systemd out of the mix.
New Findings: Cortical Blindness Eliminates the Risk of Developing Schizophrenia
Seems like the tl;dr is that v8 and spidermonkey need to work on adding more optimization tiers to their wasm piplines
https://news.ycombinator.com/item?id=19007493
We'll soon be able to know the original source of our coffee
600 cd/m2 might be just enough for outdoor work. Current MBPs say they are 500. I can only work on it with bright IDE theme.

My iPhone pushes up to 725 and it's useable with sunglasses at the beach.

Discontinued Lenovos OLEDs had pissy 330 cd/m2...
Don’t get me started about Eve...
Considering my old phones get burn-in after a year or two, that windows has far more static elements than Android, and that I don't replace my laptop every year, oled would be a horrible choice for me.
That’s not his Apple email.
Yeah, if you have a hacked iMessage client you probably could retire from bug bounties. At any rate the bug in question would pale in comparison to a rogue iMessage client.
The main point here is to gain improved resolution on text where it's quite noticeable going from 140 PPI to 280 PPI - many developers will appreciate it.

It should be fine for the kind of work you're doing though, are you using tools that don't support DPI scaling?
And now we've come full circle with reader modes that disable all that crap the designers add.
Sorry about that.

In my defense, I linked directly to example source code.
Maybe it's not enough for your satisfaction, but there are resources available for writing safe and secure code (I'm not sure if this is required, though), as well as regular audits by the security team.
This story is so California.
There was a sophomore class at Georgia Tech in the early 2000s (and maybe still going, not sure) where we all had to use Squeak. Theres some beauty to the language and its a very good way to learn about message passing.

At the time though, the full environment was incredibly buggy and would lead to having to take image snapshots way more regularly than you'd want to. Hopefully those bugs have been fixed by now if there are still people using it.
Does Windows not have burn-in prevention?
The platform is dell, lenovo, hp, etc...

Samsung is a big supplier of electronic parts.
Well this is the top Twitter trend right now, for starters. It's a very visible, very easy to reproduce bug in a very popular service, and it's definitely going to hurt their reputation with consumers more than if it was something more technical yet equally or more dangerous.
That just seems like a good idea anyways. FaceTime as a product just flat out seems stupid.
The problem is full process management, and in that regard, upstart was pretty much still just scripts. I will say this, systemd tries to solve the problem of tracking all children/grandchildren which is difficult to do with sysvinit or scripts by themselves.

Systemd also solves the problem of unified ways to start services across many distributions. Packaging things is easier. I don't like the systemd ini target format and wish something else had won out instead. With something like upstart, in theory you could rewrite the upstart daemon and use the same scripts, since the format/standard was much simpler.

I feel like there must have been a lot of bullying to get systemd across so many systems. It just seems weird to see so many major distros all decide to accept something so complex if it wasn't for Redhat cramming it into everything they maintained and helped fund.
The Next Climate Frontier: Predicting a Complex Domino Effect
Agreed. A founder should assume any ambiguity in a term sheet will be resolved in the investors favor (since you're very unlikely to walk away from a deal after signed). I preferred more comprehensive term sheets so that we could pin everything down while the investor was still in "courting mode".

Something we did in our later financings was to (very politely) provide an interested investor with a fairly comprehensive (~7 pages) template term sheet that had blanks for the major economic terms, but otherwise fully specified all the details of the proposed deal. This kept things from drifting off "founder friendly" after signing and had the added bonus of making offers easier to compare.
I made one a while back for fun.
https://github.com/fictorial/canvas_ui
Did you read the link? See popehat [0] as well. The prosecutors said he should get the 6 or 7 years. And, if the judge went crazy and ignored the guidelines, this is what appeals are for. You seem to be the one lacking intellectual honesty here!

0. https://www.popehat.com/2013/03/24/three-things-you-may-not-...
Must be a nightmare when installing a new Linux distro in text mode and having bird seeds as characters.
You're experience is so common that there are sites like "https://css-tricks.com/". I feel the problem here is that when they were making the standards, they for whatever reason separated the content from the layout and styling. I think XAML is actually an incredible example of well implemented layout and styling. I can do the layout graphically, and I can adjust the layout intuitively using XAML for those things that can't be done graphically. I can dive further into it and apply styling also through XAML. From a developer experience perspective, XAML is what a developer is looking for. HTML+CSS has it's roots in authoring pages of content, not applications and it clearly shows. They've attempted to evolve both to become application development languages and they're just not meant for that. The WWW really needs something akin to XAML+C#, maybe in this case a hybrid layout/styling language combined with TypeScript (IMO). All languages have their merits and their shortcomings, but for a web application developer, thank your lucky stars that CSS Frameworks exist.
I reckon there's a SystemD bug that didn't mount LVM volumes correctly, some has lost data that's real tragedy
"The initial FaceTime connection is made through Apple server infrastructure that relays data packets between the users’ registered devices. Using APNs notifications and Session Traversal Utilities for NAT (STUN) messages over the relayed connection, the devices verify their identity certificates and establish a shared secret for each session. The shared secret is used to derive session keys for media channels streamed via the Secure Real-time Transport Protocol (SRTP). SRTP packets are encrypted using AES-256 in Counter Mode and HMAC-SHA1. Subsequent to the initial connection and security setup, FaceTime uses STUN and Internet Connectivity Establishment (ICE) to establish a peer-to-peer connection between devices, if possible."

Source: https://www.apple.com/business/docs/iOS_Security_Guide.pdf
I used upstart deeply around 2012-2014 in a commercial product based on Ubuntu. I remember two problems with it which had me waiting for Ubuntu to switch to systemd (unfortunately my employer ran out of money right when that happened). The first was that Upstart's model is upside-down: where systemd has units that depend on units, Upstart has jobs that are activated as other jobs complete. Whereas you would tell systemd that (say) Apache depends on syslog and ask it to try to start Apache, and therefore systemd would first try to start syslog, you tell Upstart that Apache can be started when syslog starts, and that you should start syslog, and then Apache's dependencies are met and Apache can start too. Instead of having a single target (like sysvinit runlevels or systemd's multi-user.target) that it works towards, Upstart just starts ... stuff ... untill it's done. Upstart did have a runlevel concept, but as I recall it was an event that triggered jobs to start, not a target. See http://upstart.ubuntu.com/cookbook/#critique-of-dependency-b... for Upstart's defense of this approach.

(systemd is hardly unique in being dependency-based instead of event-based - but it is a strike against Upstart in particular. Also, while one of the stronger claims of why Upstart should work this way is it matches the evented mindset of udev, systemd can handle events from udev just fine, by just having it add additional targets - and in the end, systemd consumed udev.)

The other was that it was hard to deal with its bugs. I had a job that wasn't activating. I spent days chasing it, including attaching a debugger to Upstart, and eventually gave up. I've used systemd extensively and have not had "Why isn't this service starting" bugs. (I've certainly had that confusion, but I've always been able to figure it out quickly.) systemd has in my experience been reliable and trustworthy. I'm not going to say that it's bug-free, or that I like its implementation, or that I have no complaints about it. I am going to say I haven't been frustrated by it - even when running very old distro versions with lots of known bug fixes upstream. That's very important for whether I'm happy with it or whether I'm going to switch back to sysvinit and find something else for service monitoring.
> systemd tries to solve the problem of tracking all children/grandchildren which is difficult to do with sysvinit or scripts by themselves.

> Systemd also solves the problem of unified ways to start services across many distributions. Packaging things is easier.

> It just seems weird to see so many major distros all decide to accept something so complex

You answered your own question. Distributions adopted it because it solved many problems for them.
Just to play devil's advocate (not a lawyer though):

What constitutes a "phone"? Any device with cellular capabilities? What about WiFi calls? What if it's an industrial device with no network (LTE/data) access? Is a laptop with a 3G modem covered under this?

I would suspect the problem is in defining what devices to target, and also the fact that forcing any company to modify the functionality could be perceived as a slippery slope (i.e. security notifications first, NSA backdoors later...)

In Apple's defense, it is pretty difficult to miss an update alert considering it comes through as (a) a push notification, (b) a mandatory alert, and (c) a persistent red badge on the Settings app.

I agree that it might be a good idea to differentiate between a normal update and a security critical one, though.
Should the engineers who were responsible for this be punished or retrained?
Flexbox almost do what you told it to. Try it. Previous generations were giving days of nightmare, but current flexbox + many utility libraries have reduced headache a ton.
A fee years ago, I discovered that if someone was running dual monitors and using XScreenlock, you could unplug one of the monitors and it would bypass the lock screen. I have no idea if this is still possible, I've not used XScreenlock since then.
Yup. Or, at the least, have a separate switch that does so.
I'm sure you've heard of screen savers.
https://news.ycombinator.com/item?id=19022353