skysight-inc/HackerNews huggingface dataset:
> It appears to me that there's intentional bad faith misunderstanding from some, regarding both the cookie law and GDPR, in order to try and paint it as unworkable.

Very much this. None of the cookie warning dialogs (I've seen) mention this, and a lot of them use the dialog to complain about the law.

Something seems to have changed when GDPR came around though. The cookie warning dialogs before just had angry or condescending warnings with only a big "I accept" button, and otherwise too bad. But recently I've begun to see more and more warning dialogs that both have more honest wording about what they're about, as well as providing a "Decline" button.

IIRC there is something in the GDPR about explaining the privacy choices in clear language to the user, as well as having to provide an alternative if possible. If that's the case then it really does smell like intentional bad faith.

Although to be fair in addition to bad faith, I think it's also a lot of webdevelopers just not doing research what is exactly required and just parroting the scary story off each other.

But there's certainly a large part that just want to scare their users into accepting Google Analytics tracking. I'm curious about what those lawyers told you, though. Analytics data flowing through a third party widget that is doing the same on almost every site anywhere, sure feels like tracking to me. But maybe if you disable the data collection for advertising option, Google really won't cross-correlate that data for their own purposes. Even then, doesn't Analytics track the path users take on a single site too? For measuring "conversions" and such, as well as just detect whether people get "lost" on the site, or something.

Now certainly that's useful information, but it is tracking. Also you can get a lot of that information (and more) by just doing basic usability testing on real users. No tracking required and if you ask 10 people to try your site, you get 90% of the usability issues, with diminishing returns (based on some usability research I once read somewhere). But the information is much higher quality because you can ask them questions, ask them to perform tasks, actually look over their shoulder, etc. Tracking website users through analytics is just numbers and doesn't tell the whole story in very many cases, anyway.
In the article's conclusion, the author writes:

"Finally, and briefly, we should be wary of imagining the work of cultivating attention as merely a matter of learning how to consciously choose what we will attend to at any given moment. That is part of it to be sure, but Weil and Pieper both knew that attention also involved an openness to what is, a capacity to experience the world as gift. Cultivating our attention in this sense is not a matter of focusing upon an object of attention for our own reasons, however noble those may be. It is also a matter of setting to one side our projects and aspirations that we might be surprised by what is there. "We do not obtain the most precious gifts by going in search of them," Weil wrote, "but by waiting for them." In this way, we prepare for "some dim dazzling trick of grace," to borrow a felicitous phrase from Walker Percy, that may illumine our minds and enliven our hearts."

This sounds an awful lot like meditation, which was surprisingly not mentioned at all in the article.
I think there's a middle ground, it's more a domain driven design centric view of the world. Each domain is a monolithic style application with services that run in their own processes and communicate via some type of messaging infrastructure e.g. postgres, redis, zeromq, etc. The critical aspect of this approach is well-defined message schemas and versioning. The services can be spun up with a Procfile or built into a container. As you move towards container based infrastructure, other services like instrumentation, monitoring, and aggregation of logs are required.
Hrmmm .... fun in Venezuela too ...

https://twitter.com/bgpmon/status/1104919654441467904

Must be because of that Dam blowing up

https://www.newsweek.com/sen-marco-rubio-blames-power-outage...
I think he's saying "stop trying to getting shell on your production hosts and use APIs provided by container orchestrators like Kubernetes". Which makes perfect sense because those APIs have a proper, granular security model with RBAC, etc.
Even scarier. Imagine someone with evil intent feeding captured feature vectors for any individual into a 3D printer scripted to render high-def latex masks? Privacy could then be the least of our concerns.
on-boarding new devs from the bootcamps, transitioning them to AWS + Lambda is as if starting from square one in terms of what they were expecting to work on. Very much a challenge, especially related to getting them to think about how to leverage good CI/CD for the cloud. Still a lot of knowledge gaps out there
There's no "Containers and orchestration" section, but there's a "Containers and Schedulers" which is what I assume you meant. Here's the full text of that section:

----

Once you have a containerized application, you can use a container scheduler like Kubernetes or Docker Swarm to run it on your production hosts. Container schedulers provide a well defined API to access the status of the container like its state and logs. This means users only have access to the running programs over a well defined API.

Because containers are self-contained images with everything they need to run, developers do not need access to production hosts to debug issues. For example, a good workflow allows developers to spin up a cluster locally on dummy data they control. However within production they would only have access to logs. This way data exfiltration is prevented because direct access to data is simply not allowed.

----

I read that as saying "no, don't run random containers to attach to prod, instead rely on orchestration to get you logs and instrumentation". Or is the entirety of your argument "containers are bad because images are full of vulns"?
> allows expansion up to 32 bits

It doesn't allow expansion up to 32 bits. How would that even be possible? Some of the bits are needed to indicate to use the second two bytes, so there's a hole in the range and it's less than 32 bits.
> ARIA, the language created to help make interfaces more accessible, was found on more than sixty percent of the home pages surveyed. Unfortunately, those home pages were more likely to have detectable accessibility errors.

> Pages containing popular JavaScript frameworks were more likely to have accessibility errors than those that didn’t use those frameworks.

This was obvious to me all along, but it's nice to have official statistics on this.

I would like to use this opportunity to point out the astounding hypocrisy of front-end developers who claim to be in favor of better accessibility, but then vehemently oppose the idea that HTML should have built-in component that cover basic web use cases without the need for scripting.

Sure, getting controls "right" in browsers is hard. But hoping that all web developers get them right when choosing/writing their own implementations of everything is absolutely hopeless. Accessibility should be the reasonable default you get "out of the box" when not doing something overly fancy or stupid.
Drew is one of our users: Drew is 70, with poor but functional eyesight, and they have shaky hands. I try to ensure our product works for Drew because many other users are on a spectrum with similar problems.

Chris is one of our users. Chris has a unique disability within our clientbase, and they work for a government department. There are two developers working on UI, and it would take me 3 man months to write code to make our product work for Chris. I am a founder so I have the authority to make our product work for Chris, but there is no external pressure on us to do so (not even by the government department).

The fundamental question that occurs is: should we invest 3 months working on functionality specific to a single person (Chris) or should we invest 3 months working on a feature that benefits all our users a small amount?
We have one unexplained crash where early reports about what happened /strongly/ match the circumstances that brought down the LionAir flight. We also have hundreds of public complaints from pilots across the United States of similar unexpected nose down behavior from 737 MAX airplanes.
It’s a reasonable question, but any comment that even remotely appears to “side with” Boeing is now downvote-bait. There isn’t much room for reasonable discussion on this thread.
How is it possible that reasonable people are OK with this kind of bullshit healthcare policy?
It was the local gov that let them off, it was them that hired the group. Being an American national doesn't mean you work for the US Gov.
as maintainer of two of the haskell libraries they use, a member of the core libraries committee, and a hackage trustee, i'd like to throw in my two cents:

1) i see they are doing fully qualified imports. please add major bounds to your version deps, stack doesn't excuse not tracking what versions you used!

2) they have

"data Next a
= Done !a
| Step !a
"
in their code,

this tells me they could have possibly benefited using the stream abstraction in Vector!

https://hackage.haskell.org/package/vector-0.12.0.2/docs/Dat... is a link to the latter
The article claims that things like Bash's restricted mode are ineffective. It gives the example:

parent$ bash --restricted
child$ cd ..
bash: cd: restricted
child$ pwd
/home/rjones
child$ bash
grandchild$ cd ..
grandchild$ pwd
/home

where the escape is that 'child' was able to create the non-restricted shell 'grandchild'. If you think that properly configuring a restricted bash shell is a simple as executing `/bin/bash --restricted`, then you need to read the manual. The restricted shell can execute arbitrary programs in $PATH; to deploy a restricted Bash shell, you'll need to construct a PATH with whitelisted programs that it is safe to execute. The restricted Bash cannot adjust PATH, and it cannot execute programs outside of PATH.

Something like:

$ PATH=/etc/restricted-bin bash --restricted

where /etc/restricted-bin contains symlinks to or stub-wrappers for programs that the restricted shell should be able to use.
I see they've made some progress putting Instagram on the same infrastructure as Facebook.
Session cookies are fine, it's only advertising and tracking cookies which are covered by the legislation.
== most of the time. The majority of people don't care enough to change the defaults. Most of the time, they don't even think about whether there even is something to change. The overwhelming majority thinks roughly like this: "Ooo, Computer just knows all of this about me? Neat!".

Source: I work in education - even in a highly educated area in a developed EU country, young and old alike think like this.
This is something I have been searching for many times. Will definitely try it out for my coming trips and recommend it to friends.
I tend to feel that way about Factorio, but I strongly don't about Dwarf Fortress (or Rimworld). Both of those games are story generators. It's about the things thrown at you and the ways you cope--or don't, which is also fun--with the unexpected while building something you think is cool.

Dwarf Fortress in particular doesn't care about optimization (either of code or of your play). Build what you want. Figure out what you think is cool and do it. There are, literally, no goals other than the ones in your head.
Recital 23 digs into more detail about what is considered "targeting." Choice quote:

> Whereas [...] the use of a language generally used in
> the third country where the controller is established,
> is insufficient to ascertain such intention, factors
> such as the use of a language or a currency generally
> used in one or more Member States [...] may make it
> apparent that the controller envisages offering goods
> or services to data subjects in the Union.

You are correct that reality is a bit more nuanced, but I think that saying "language and currency have nothing to do with it" is not a supportable claim. Audience and intent matters, but if you have German-language content in a country without a large German-language population, you are going to need a very good excuse why you aren't targeting Germans.

People don't have time to type every single caveat and exception. Translating to Polish is going to be targeting Polish geography 99% of the time.
Which kneecap do you want to get shot in? I ask this question a lot.

Microservices are trading one sort of complexity (the ball of mud) for another (configuration). I've found that the win for microservices is largely about developer efficiency, not code performance or whatever. Keep the developers from constantly tripping over each other in large systems.
Similar to how craigslist has led to many marketplaces it does seem like Facebooks current version has better alternatives for some groups.

I also see YouTube For X and Reddit For X as well. YC backed Tingles, an app for ASMR.

Cruise Critic could be considered Reddit for Cruisers.
Why did you leave off steps 4 and 5?

Because that's where many pilots would stop. The "runaway" stops when the pilot inputs opposite trim.
It's really a matter of productivity. Creating training sets of data is a labor intensive process. It may not be worth the cost to do so, if they can outsource that work instead.
It's probably closer to multi-writes though, than transactions in a classic sense, but good improvement nevertheless.
It does, but it isn't quite as cool (or as good for your job security) to roll your own, preferably from the ground up without any libraries or other battle tested code.
This is sad, but in no way surprising.
It has the same root cause as many websites misusing javascript to a point where they become unusable, and that is people not really knowing how to use the tools they are given.

One not so dirty secret of accessibility has always been that it is not something you do afterwards, but that you have already done 80% of what needed to be done by just writing valid, standard compliant, semantic HTML.

So I would argue, if you really want to do something to make the web more accessible, usable and a generally nicer place, learn the tools of your trade. No, HTML and CSS are not so simple that they are not worth your time. They are easy to learn, true, but put in the time to get them right. Headings are an H tag, Navs are lists of links, paragraphs are p, not div. Easy stuff like that. And of course, CSS goes hand in hand with that.

You know display: none on a dropdown menu breaks accessibility, right? Of course it does, you tell the browser to not show the content. So use position: absolute; left: -999em or something. These are simple things you could and probably should know and if you do them, you already eliminated most of the problems.

Alt Tag on Images? Yeah, they are easy to forget, but they are also mandatory! So if you tend to be forgetful, use something like pink css borders around images that don't have them, so you won't in the future.

And for using tables for layout: There was a time, way back when, when css 2 was sparkling new and the young guys in the office bought a copy of Zeldmans "Designing with web standards" so the old farts would learn that the world was better now and we didn't need old crutches. If you are still using tables for layout today, you are not a web developer. Harsh but true. They got obsolete with float and position and you also have flexbox or css-grids today. I think you still actually don't need these for 95% of designs, but if you find them easier to use, please do!

And those aria tags or skip to content links? They are actually not the problem. They are icing on the cake. Include them if you like, people might thank you for them, but they also have had tools to compensate for these shortcomings for years, so they are not the real problem. Not displaying content properly or not at all without 500K of JS is, though.

So do something for accessibility and the web and learn the basics, it goes a long way to making you a better and more efficient developer and making the web more pleasant to use for all of us!
I like the new integrations with Sublime Merge, but for now i'm going to keep using Git Gutter, which has more features for viewing information about diffs within files:

https://jisaacks.github.io/GitGutter/

You can easily view changes to individual lines or chunks, revert them, etc, without opening a separate tool. As far as I can tell this isn't possible with the new built-in integration.

You can also compare against any branch, not just `master` and `HEAD`.
ah, i believe you are referring to the webrtc data channel. it leaks local IPs, but the severity depends on several factors, including whether you're running VPN and what you're using the VPN for, or just running behind a regular local network.

if you're running behind a regular local network then I wouldn't consider the local IP leakage as a "privacy hazard". local IPs are compromised already. everywhere. they are easy to guess. they are easy to obtain in native apps. etc.

there are issues when it comes to places where VPN access is crucial/vital. thankfully, very few VPN providers leak your IP nowadays, and with drafts such as what the poster above mentioned (https://datatracker.ietf.org/doc/draft-ietf-rtcweb-mdns-ice-...) this problem will be history soon enough.
Agreed. Fans will dv this, but it's like saying an etch-a-sketch is on the level of photoshop.
I have this same problem. In factorio for example.

Either I use other people's efficient designs that are more optimal and then I feel like I'm just copy pasting and not playing.

Or I end up wanting to write a program or design things that can produce the optimal designs. All of which involve not actually playing the game but playing excel spreadsheet or programming dynamic programming algorithms.

I like games that allow min maxing a lot. But they need to be in such a way that there is more to the game and less copyable stuff. So that I can enjoy and play the game.
What if Apple Music is for free? Should be Apple be punished then, like MS for IE being free?
Traveltile looks really cool! The documentation is kinda amazing and I'll definitely clone it and play with it later today.

Before Travelchime, Peter and I had some experience with monetizing via hotel and flight affiliate fees via our past sites, https://bookwithmatrix.com and https://alltheflightdeals.com . We did a bit of research, and about 2/3 of travelers who use docs start one before they book the hotels. We believe that if our recommendations are good enough (based on where you'd like to go in a trip plan), we could monetize using the same model there.

Forking an existing trip plan and copying bits/pieces from friends' trip plans are both features we'd really like to build out really soon! So many of my trips end up having 50%+ overlap with some of my friends, so that'd save a ton of time
You're already logged in so it's just going to show you old content. I'd be surprised if your able to post anything, or if any "like" you give during the outage is saved. Same thing is happening with both Instagram and FB apps on Android for me.
That’s certainly possible. We’re probably still too early to tell, but the innate conspiracy theorist slash pattern-matching part of my brain wants to find a probable connection.
Very cool! I like seeing people find ways to innovate in areas of social that are often just surrendered to FB.

Also, just an encouragement to take the strong opinions here with a grain of salt. Obviously, you have a list of features you'd like to build at some point, many of which are likely mentioned in the comments. But HN may not overlap with your actual users very much, and is likely to have a different list of "must haves" than most folks. Make sure you talk to non-techies!
>Agencies operate somewhat independently, precisely to prevent the appearance (and reality) of political interference.

Unfortunately Trump didn't start this trend but I really hope whoever is next stops it.
> whats the appeal of Linux for software engineering, if you want the "it just works" approach

For one thing, Linux-based OS's like Debian GNU/Linux absolutely follow the "it just works" mantra - if the OS installs properly in the first place and does what you need it to, you can expect it to be rock solid with few or no future issues. Plus, they tend to work for a lot more time than the 5 years max that Chrome OS does (or Mac OS, for that matter). That's simply invaluable in this day and age.
I see this in enterprise. For example: Sellerscrowd
Just to note: Some death-metal bands have positive lyrics[0,1]... (Though, whether they can really be called a death metal band is possibly a point of contention.)

[0] - https://youtu.be/lk2-bgwA0Ro

[1] - https://youtu.be/Nh10gL_GP_w
But why, if you may spare the time? It’s the reasons that made me make my initial comment about the hype. I have yet to see good enough reasons to move, but maybe my development environment varies quite a bit from other people. Still, even if it had way more features, which I doubt, the performance differences are still (just tried it) too much for me to consider it.

Thanks!
Leftpad as a service?
I think slightly hyped by popular media. Kinda hard to defend with news like this. Just keep in mind not all Serbs are ruthless and dark, even if they had been impacted by war.

(Comic relief) If you encounter a Serb, don't panic, chances are he/she is not armed with anything other than kindness. "Hotyesh pivo" means "wanna have a beer" :D .
Planning a road trip from east coast to west coast and back (USA) with my wife this summer. I will give this a shot and let you know how it goes, thanks
> Most of our conversation focuses on scaling the database.

I think one of the emerging principles behind modern micro-service design is to break out your data model into separate services that hide the database. You can then publish data changes to an event stream. This can help avoid requests coming back to a database. I think this is a better approach compared to heavy caching (e.g. redis / memcache).

I definitely agree that micro-services aren't a silver bullet that solve every engineering problem that exists but the hyperbole of 150 micro-services is a straw man argument.

My main annoyances with Kubernetes/docker systems I have encountered is stability of the cluster and visibility into the health of pods. Both of these issues were the result of my org deciding to build our own Kubernetes from scratch and this has turned out to be a significant task.

If I was starting my own company and wanted to develop using micro-services I would probably use one of the existing off-the-shelf container cloud service providers (e.g. Amazon/Google/Microsoft). I think that is a better approach than "build a monolith then lift-and-shift into micro-services later".