skysight-inc/HackerNews huggingface dataset:
Yeah this idea has been tried before, see for example the cycleGAN architecture (not for language, but image-to-image translation)

https://bellchen.me/wp-content/uploads/2018/01/LUOHAO_151325...
Mine is
"[JIRA_TICKET] Add something"

It's simple and worked well for us so far. Less rules, more information, and developers are free to use their words to express intention of changes instead of nonsense (feat, fix,....)
Project Loom is the only approach that truly promises to solve function colouring, user code just uses the thread API, while the underlying implementation can be swapped out transparently. I'm not aware of any other ones that do this (not, not even Zig).
Security can't be made simple. At the core what SELinux does is simply enforcing a policy. A list of "Should X do Y to Z?".

This is something that can't be implemented with just file permissions. What SELinux does is sandboxing every process it controls.

For instance, my cupsd is running as root. It's accepting connections on port 631.

If it started accepting connections on port 22, that's probably a bad thing. If it started messing around with /etc/passwd and /etc/shadow, that's probably not good either. It probably also has no business with my GPG keys, or /dev/sda.

But under the Unix permission model, if it runs as root, there's nothing you can do about it. It's root, it gets the entire system. If it has a hole, that's that.

SELinux first applies labels to stuff, then defines what actions can be done on what. So under SELinux there's a rule that says "A process with the label "cupsd_t can listen on a port labeled ipp_port_t". That's what lets it listen there, and absent a rule that allows it to listen on the ssh port, it's denied even if running as root.

So with a well implemented policy, if somebody exploits your cupsd, they can waste your paper. But despite it running as root they can't run a shell, can't open ports, can't mess with your password database, and can't install its own kernel driver. With the right rules, the attacker can find themselves at a dead end, where there's nothing useful they can do.

You can to some extent do this kind of thing with containers, but it really amounts to doing the same kind of work in the end to a large extent. If your container's security is at all useful you'll have to tell the system what should the cupsd container be able to do, in a very precise manner, and not just "eh, it can have root access to everything". At that point you've got another SELinux-like system to deal with.
No, because I felt that some of these titles seemed quite ambiguous despite showing progression. I spent several years at the company and worked in several different areas. I felt that using titles like "Build Engineer" or "Tools Engineer" was more useful than "Software Engineer I", "II", or "III" even though they were my "official" titles. I've thought about changing it a few times to display seniority progression, but it's not felt quite as intuitive as what I have now.
Didn't someone rage ban Trump on the way out?
With respect to burnout, traditional sports can only be practiced for so long each day, typically only a few hours, which due to being in the real physical world is going to include natural downtime like moving cones around, and people are also aware of injury risk. So when you're practicing football it might be intense for a bit at a time, for a few hours, and then you go sit in an ice bath or go home (and play yourself in FIFA heh).

eSports being basically an office job is not going to have that issue, people who are sitting in a chair for hours at a time look like they can be pushed harder until quite late in the night. That goes for both gamers and people doing normal office jobs, you're pooped out way before you look like you are. There's a psychological toll that is hard to see.

Having said that the main thrust of the article is economic. If people got paid more, they'd do it more. NFL players get paid experienced FAANG dev salaries at minimum, fantasy money at the top. There's good reasons to stay in the game as long as possible. If people were paid that kind of money to play games, they would stick around and the narrative would switch from young-and-fast to older-and-experienced.
> I don't know why people are so freaked out by living in a surveillance system where every corporation tracks their every move for profit

You haven't read enough dystopic fiction.
Pour one out for the Machine God.
speaking for myself, "fair" means they obey the contract, which gives them that ability

there is also the option of not letting people buy or sell stocks at all, which would resolve the same issues the mandatory sell provisions resolve
Broader Autism Phenotype: What does it mean to have just a hint of autism?
No, I just accepted a Rails job offer a while ago.
So they just displayed the wrong message as in people could cancel rides free of charge but the message said they couldn’t? It seems a bit of an excessive fine for something that mostly seems harmless. Like booking.com seems to be using all the dark patterns they can find and I never hear them being impacted by fines.
Because we didn’t ask for systemd. We like init scripts that we actually understand.
SELinux policy can (and does, by default, on rhel-like systems) enforce the security guarantees the container frameworks provide.

This is very much an optimal scenario for SELinux when you have some macro-level policy restriction and you want to enforce it.

SELinux is just not very well matched for the usual scenario of trying to graft a security policy on software and a system admin that is completely unaware of it.

This means people get frustrated when an Apache server can’t read some files in some folder arbitrarily set in the config, because there never was any policy of the Apache server only being able to read files with the right security context, that was never part of the HTTPD sever documentation, it’s a default system policy called selinux-policy-targeted that originates with Fedora.

Now if you run the same HTTP server in a container, you have first class concept of a volume, and the container framework is aware of that and can label files with the right context as needed; in fact with Podman it will even use MLS to prevent cross-container contamination.

So IMO containers are not in any way incompatible with SELinux, they are in fact a great abstraction match and they work great together. There’s been many container escapes that were prevented by SELinux policy.
As a completely new admin, could you elaborate on "be very careful with volume mounts"?

In the k8s env I run, the filesystem is backed by ceph, which creates persistent volumes that the different pods can claim. Is it just "be careful not to mount docker.sock"?
Does it also make sense economically, i.e. comparing how much time you put in vs how much money you get back?
It was before that
Where are you sending these mails from? Mailchimp, Mailgun or similar?

Or a self-hosted server? If so, have you checked if you're on a blacklist or something that would lead to providers marking it as spam (or refuse delivery altogether)?

If your customers mark something as NOT spam, I don't think that will do anything at the server end unless they have also set up Sieve?
Ok, let’s take the in store analogy. Agree that following someone home to spy on them is wrong. But in store, if I see a person looking at some items on a shelf and start to tell them about related items, doesn’t that violate the need for explicit consent? Expecting “full understanding” is too high a bar, IMO. Implicit consent, public notice and opt out are sufficient. Otherwise you end up with GDPR cookie opt ins that only train people to indiscriminately push “accept” buttons.
I run thousands of severs. None of them have SELinux or systemd. It’s banned tech.
Doctors could be struck off for spreading fake news on vaccines and lockdowns
I'm not sure. But FWIW I don't think more complex nesting would change anything in this regard. Those transforms essentially just avoid you having to wrap some things in functions manually, and avoid some extra function calls. Avoiding manual wrapping is a convenience feature and those extra function calls are not really that expensive (or it wouldn't be possible for Voby to be faster than something optimized like Solid in the benchmark).

If you'd like to come up with a different sort of benchmark where you think Solid would shine I'd be happy to write an implementation of it with Voby and see what happens. Or you can just try that yourself, the API is fairly similar.

---

I should probably add that js-framework-benchmark is heavily biased toward measuring creation time actually, which is something where compile-time optimizations should shine. If you are more interested in updating things, like you would be in a rich application, Voby is actually some 20% faster than Solid at replacing rows with other rows, because it support reusing of older nodes (opt-in) (this also lowers memory pressure in some cases by the way, no need to make and gc lots of stuff in some cases). This optimization is not supported in Solid nor Svelte, and interestingly it's not a safe optimization that can be applied all the time, so it must be opt-in, but how are you supposed to tell to Solid or Svelte when it's safe to apply it if something like Voby's "template" function, which is also used for this, is abstracted away entirely from you? In some sense the transform actively goes against performance here.
For those who don't know who that is but know even a little about the fighting game community, he's the guy behind EVO moment 37, the legendary perfect parry into super; https://www.youtube.com/watch?v=JzS96auqau0

(And for more context behind that, which I love because they actually got Justin Wong, Chun Li's player, to comment on it, see https://www.youtube.com/watch?v=4cNCa8PylLA)
Ok, you own a store. A customer enters your store and buys a widget. Since you're smart and want to know everything you record the sale and add it to your database.

Only that's not where it stops.

After the customer leaves the store one of you minions follows him to every other store he ever enters to record what he buys, or even looks at

That's why your analogy falls completely flat.

Nobody would complain if it only concerns your store and your sales. But people violently dislike you snooping on everything that your customer does.

Worse! He doesn't even have to be a customer of yours. You snoop anyway, even into his most private affairs.
I'm running Clojure code compiled with GraalVM native for AWS Lambda. Cold start times are low and performance is decent enough, even with CE edition. The whole process is reasonably painless through the use of Holy Lambda https://github.com/FieryCod/holy-lambda

Not quite what you were asking for, but I wanted to chip in as another happy Clojure + GraalVM native user.
Distribution of block producers over time on the Tezos proof-of-stake blockchain
We do the same and it works pretty well. The problem with that approach, though, the codebase may live for decades but issue trackers change and old tickets usually don't get migrated to the new system.
Board meeting -

"How's, like, the code that gets the spaceship in the air and back down again. Is it all working ok?"

"Yes Elon, should work fine. It's basically just typing."

"Great! Should work without any problems."
Next version of Amazon Linux (2022) will have SELinux enabled by default.
Wasn't the CIA also a big heroin dealer during the Afgan war, with military planes with "unspecified" cargo constantly taking off from there, so they can earn money for their black-ops projects?
It is really great that people are discovering the utility of triplestores through their ubiquity in the Clojure ecosystem (e.g. Datomic and its many clones).

I do feel saddened that few seem to realise that the fundamental idea actually comes from RDF (i.e. the semantic web) and that Datomic's Datalog dialect is actually very similar to SPARQL. Datomic's primary innovation is the immutability/time travel feature, not the fact that is uses triples and works like a graph database. If you find triplestores fascinating I implore you to explore the semantic web stack too.
This a strawman. We're not talking about your friendly neighbourhood corner store here. We're talking about large scale systems with billions of users, systems that contain and shape a lot of our public discourse. The way these platforms make money inherently affects our society and our democracy. "Helping your customer" is irrelevant here.
I don't think you're alone. I felt the same way about overcomplexity until I had a few runs at working on already established complex frontend codebases. What seemed to happen around 2008 onward is that the basic principles of the web were sort of simple, but then to do anything at a larger scale it got pretty crazy quite quickly, and so new architecture ideas came along to address that by people who were in the business of solving engineering type architecture problems.

For any site of inherently simple interactivity, it's always been as easy if not easier than it ever has, but now it's also more manageable if you know you're going to need to scale a certain way.

It doesn't necessarily take all that much before you can start to see the reasoning. For example, take a humble grid of products, each with their own add to wishlist button, and a profile preview button in the corner of the page that indicates how many things are on your wishlist. Pretty simple to handle, render the thumbnails with unique ids and make an XHR request that stores the data with your account. Update the wishlist total count however you would.

Now suppose though that each thumbnail in the grid can open a bigger preview dialog that has more images, a bigger description, and it's own add to wishlist button. You can click that button, and it does the same thing. You close the dialog, but now your grid item needs to reflect that it's already been added to the wishlist. These things get really tiresome to keep building, something that I'm sure isn't new to you if as you say, you've been in software a while.

Sorry for the book, I mostly wrote that to challenge myself to think it through, not to imply you couldn't think of how it would be necessary to componentize things.

I'm not particularly fond of React more than Vue or anything, except for the fact that they both allow you to define UI as collections of functional state machines when it's necessary to do so.
Atuin for zsh shell history in SQLite
Personally I think we already exceeded the sweet spot. Things like jQuery were merely abstractions and shortcuts, but didn't bring much to the table. In the end you had to do all the work. On the other end things like Next.js do so many things up to a point at which you start working against them to achieve certain things whilst ending up not using 80% of the framework because they are aimed at basically every possible case without being really specialized. It's mostly about accessibility these days, like getting started fast. While I don't quite agree with the clustering and categorization (as already mentioned by other comments), for me it feels like the ideal point was somewhere between era two (Knockout) and three (Vue, React), with a tendency to the second era.
That's already the case today if you are not in a very good sector, at least in France and Switzerland.
FSFE asks EU to legislate hardware life cycles, bootloaders, and right to repair
> This point cloud assembled by Team CSIRO Data61 shows a robotic view of nearly the entire SubT course, with each dot in the cloud representing a point in 3D space measured by a sensor on a robot. Team CSIRO’s point cloud differed from DARPA’s official map by less than 1 percent

https://i.imgur.com/1Mi9YwA.png
> Some even seem like wilful lies (e.g. the one about Windows and Mac allowing you to 'configure everything via the GUI').

That's true excluding registry hacks 99.9% of people couldn't care less about.

In Linux on the other hand a TON of things do require using console.

> In short, it's FUD, and the author is not honest in his assessment.

I've heard this assessment from rabid Linux fanatics before.

However "FUD" is more likely your assessment of the article because it's as factual as it can be considering I've been using Linux as my primary OS for 25 years now.

> As such, the article is without merit.

Well, you've spent 10 seconds reading it, so your comment is without merit.

> So, what can you not do on Linux that you can do on Mac?

No clue, I've never used MacOS to a large extent (excluding wasting 3 days trying to install Windows next to it which I succeeded but I hated every second of that experience considering I had to even use BIOS loader hacks to make Windows work), the article is not about an Apple OS either.

There's no way I'll ever do that again. Apple hardware is meant for Apple software, period. Using anything else is a never ending source of pain.
"Siri Data is associated with a random, device-generated identifier. This random identifier is not linked to your Apple ID, email address, or other data Apple may have from your use of other Apple services.

Siri Data and your requests are not used to build a marketing profile, and are never sold to anyone."

https://www.apple.com/legal/privacy/data/en/ask-siri-dictati...
What I want to know is how realistic it is that you can create a blockchain app at scale without using "centralized" resources. Can you build a social media app clone that is used by millions without using AWS or Google Cloud or Azure? Because if not then what exactly is the point of decentralizing everything if you still depend on a few key players?
> I also feel crazy in that there seems to be consensus that blockchain is suppose to do everything, or should be doing more than it does. In all of this, I am viewing the problem space from the domain of infrastructure, agnostic of application. Is blockchain tech already everything we need it to be?

This is where the line is drawn here and we start to see the problems in using 'blockchain for everything' which as silly as using one tool / language for every. single. application, which is what Ethereum originally proposed.

As I already said [0], since that has failed to scale on-chain, it cannot be used for many serious applications without overpaying for fees. If it cannot manage to scale and keep its fees low, then its possibilities are quite limited for anything on-chain.

Like Bitcoin, both of them have proven after years of existence, waiting for improvements and promises had no notable improvements for either of them for on-chain scaling.

One of the only useful applications for these blockchain tech is and has always been payments. That is why companies like Stripe [1] have gone and made a crypto payouts product with that which as always needs to use a layer-2 side chain since they also know that Ethereum itself is too expensive for on-chain payments.

Highly likely in the future Stripe will add a faster and cheaper on-chain layer one blockchain that can scale faster than both Ethereum and Bitcoin and is suitable for payouts.

[0] https://news.ycombinator.com/item?id=31031572

[1] https://stripe.com/blog/expanding-global-payouts-with-crypto
Sure, cameras in todays smartphones are great and take beautiful pictures, but bird photography is pretty much their achille's heel - tiny fast-moving objects would require much better zooms, higher iso, and lower shutter lag than what's currently available with smartphones.
I used to switch SELinux to permissive with the intention of checking and correcting the policies later, only to completely forget about it when other issues get priority.

Now I just turn off SELinux and be done with it.
Thank You to everyone who stopped by Sqwok today and/or left feedback here! Much appreciated! Thank you dang
It's kind of a pointless question when you haven't provided any details. Are you self hosting? If not, which provider? Are you using an email delivery service? Have you correctly configured DKIM and SPF?

To answer your question, no you cannot force them to do anything. Either fix it yourself or hire someone who can fix it for you.
Elon doesn't yet own or control Twitter, and won't for months to come.
Searched the comments if someone asked the same question :)

Maelstrom is on it at least.
I get your overall point, but your example is not a good one: on Linux, at least, xscreensaver does not have a component that needs to be setuid root.

xscreensaver-auth uses PAM to authenticate, which (typically) runs a small program called unix_chkpwd, which is setgid shadow (not setuid root), as /etc/shadow is owned by root:shadow and is readable by group.

xscreensaver is one of the very few screen lockers that is reasonably secure, because the bit that locks the screen is pretty minimal and only links with a few fairly-low level X11 libraries, not a full-scale GUI toolkit.

> What we should have instead is some sort of authentication service. A program confined by SELinux to only interact with a socket and the password database, speaking a simple but well designed protocol.

That sounds pretty overengineered. All you need is a small binary that is setgid shadow, that can take username/password on stdin, and exit 0 if auth succeeds, 1 if auth fails. But we already have that: unix_chkpwd.
Are you Elon Musk? Then you can buy the email company.

If not, you must check your email server's reputation, check you are not using trash netblocks like linode, and check you follow best practices like having a sane RDNS for your outbound mail server.

Some places check there is a valid MX that has a sane HELO matching the sender.

In short stop seeing this as 'big email' problem and as a technical quality issue about your mail arrangements which you do have control over.
Nginx is written in C and optimized to avoid dynamic memory allocation, whereas Go's net/http stack performs a lot of allocations, which I think are them main source of the observed performance difference (together with different approaches regarding socket handling and polling, I think). There are libraries like fasthttp that can significantly speed up Go HTTP performance, but they have their own set of tradeoffs.

So yeah if you worry about peak throughput on a CPU-bound system Caddy probably isn't the right choice though I'm not sure nginx is, either. A hardware-based load balancer, at least as a pre-stage is probably more sane in those cases. For everything else I would always trade ease of usage for a bit of performance. I would e.g. never dare to touch the nginx codebase, but writing a plugin for Caddy doesn't intimidate me at all.
Small increases of small numbers are deceptive when reported as percentages
That cost needs to be higher than not breaking the law.

Otherwise, why would a company ever respect the law?

You hire any fresh grad accountant, have them figure out that:

Profit from breaking law > cost of fine

and the company will rationally decide to just keep breaking the law.

That's not a deterrent, it's just another line item in an accounting spreadsheet.
I mean that E-ink business practices are the biggest (the hugest even) obstacle to a wide ePaper adoption. They pretty much own all of the most important patent and you only see progress in the products in the consumer market when they expire.
Old Latin and Chinese wisdom of about 2000 years ago. “Unum castigabis centum emendabis”, “punish one, teach a hundred” (can't write it in Chinese, sorry.) Made popular again by Mao Zedong about 50 years ago.
Force is a difficult word. You can certainly help, by following their guidance on DKIM, SPF and DMARK.
The employment screening algorithms aren’t looking for talent, they are looking for a cultural fit.
Hosted Large Language Models (DALL·E 2, GPT-3 and J-X)
I think you just proved the author's point. That looks entirely inscrutable.
We used to send them
from Gmail, then we switched to Fastmail.
It was the same in both cases.
We're not aware of being on any blacklists.
Our emails are delivered, just land in spam for few Big Email providers.