skysight-inc/HackerNews huggingface dataset:
The faster and heavier you are, the more capacity for harm you have, and the more you must pay attention to just the road in front of you instead of the world around you.
Your esteem for Generalists made me think of glial cells.

https://en.wikipedia.org/wiki/Glia
When will I be able to upload my brain to a computer?
Texts were mentioned as-it-is since for now we are lack of training data to reproduce the same model for English language.

In terms of understanding list:

1. Yes it is.
2. Entity tagging model, based on DeepPavlov, is a part of ARElight, not AREkit.
3. AREkit implements and provides tools for BERT data preparation only; BERT-related service is a part of the ARElight.

Overall idea and understanding is correct.

In terms of the AREkit, the latter proposed as a data-preparation toolkit. However, at present, it additionally provides a Tensorflow-based neural networks zoo in, adopted for sentiment relation extraction task
https://github.com/nicolay-r/AREkit/tree/0.22.0-rc/arekit/co...
It's just like any other tech; you read the docs, try it out, do some troubleshooting, and then you know how to use the tool.

I bet you could get microk8s running correctly on your first try. Give it a shot! Here's a doc: https://microk8s.io/docs/getting-started

You could probably get some additional nodes in your cluster on your first try too: https://microk8s.io/docs/clustering

This isn't Usain Bolt. This is normal people doing normal work with normal technical tools, and then somehow people keep claiming they must be some kind of world-class genius to have done it. Try it for yourself before you claim that you'd have to be a world-class peak performer to have installed and configured some simple daemons on a few linux servers.
Would the six second microwave work well? Would it obliterate your food in one region, while another isn’t warm?
>yet they haven't managed to achieve that positive impact.

You don't reach billions of users without positively impacting people who use your service. If there was no positive impact people would simply abandon Google's and Facebook's services.
OK, but how much time are you spending on managing these yourself? If it's non-zero then the cost between $5 and $120 for a company is trivial. For a personal side project, sure, but if we are talking about paying customers' data then even things like automated backup and recovery need to be taken into account.
It depends. Humans vary and, while you may thrive on a plant diet, you can't generalize your experience. There are people who have problems even supplementing B12. Others don't. You can't just tell those who have that they've been living a lie.
>those Brent-style types

Which Brent are you talking about?
Mostly agree, but personally I comment when it is a bug impacting production stuff(outage for me). I don't know how else to get support, if they have a paid support option my company would be all over it for most of these projects. But therein lies the usability issue of OSS. With commercial software I can open a ticket and at least get some response that will help me make plans on how to deal with the issue.

There really needs to be some org that simply lets devs get paid for supporting paying customers and let customers procure such support.

For personal stuff I don't care but after fighting many battles to sell OSS when I have some issue what other recourse do I have than to politely explain my situation and hope I get therir attention. I literally beg for help! I am sorry if that annoys devs, but it is either that or I give up on OSS and be permanently pessimistic about anything related to it.
Sucks as its properly dangerous due to simple statistics (you need just 1 out of 10000 drivers to not pay enough attention, be high, super tired, getting seizure or heart attack, etc.). Riding on roads without dedicated full cycle lane sucks, period.

Another point - directly breathing all fumes from thousands of cars every day, lorries, buses and other diesel marvels. More than compensating a healthy activity with equivalent to smoking a pack of cigarettes.

Fanatics always propagate their sports/activity as next coming of jesus, but as with everything there are pros and cons. Biking on standard roads has massive cons.
I think a lot of the problems with domain ranking is domain expiry and dead links. It's extremely susceptible to domain ownership changes. If you monitor high value domains for expiry and then immediately purchase them and fill them up with links to your websites, you will effectively inherit that website's ranking power.

HTML does not provide any information of when a link was created, and DNS and HTTP does not provide any information bout how long a website has been around or ownership changes. HTTPS isn't much use either. Maybe you can coax it out of a registrar, but the information is not readily available and not easy to interpret. It's really a bit of a design flaw.

The WWW was just never designed with this in mind, it was designed around long-lived academic and government institutions, and it really struggles to deal the ephemeral nature of the public and commercial web adequately. I'm not sure if RSS feeds are much better.

Not really sure what's a good and scalable fix to this that allows the linked resources to still be mutable by their owners.
As referred to in the article there is a 18Bn solar mass black hole with a 150Mn solar mass black hole orbiting.

Whilst very assymetrical it’s still huge, I imagine this will take a millions of years before collision.

https://www.jpl.nasa.gov/news/spitzer-telescope-reveals-the-...
This reminded me of a particular quote, I think by an Indian author. To paraphrase

"Cars are way too fast, the world speeds past in a blur. Bullock/ox carts are nice but not much faster than walking. Cycling, however, gives you time to say hi and be waved back, while being fast enough to be practical."

I wish I could remember the author (maybe Sudha Murthy, Ruskin Bond, Rudyard Kipling or even perhaps Roald Dahl?), perhaps some other HN-er might remember!
There’s a video of Magnars giving a presentation where he starts with some slides in org-mode and then live codes the slide manager in Emacs as part of the talk—-that was very inspiring while I was new to Emacs!
Even if there were a fixed peg between cryptocurrencies, that still wouldn't imply that GPU-mining BTC is just as good as GPU-mining other cryptocurrencies.
Nitter is not that big of a deal, as they're just one website. Easy to block.
2 things:

A common error about CH4 is misunderstanding half-life vs CO2e calculations. The half life is 10 years but that does not make it a non-problem; a commonly used number is that CH4 is 25 more potent that CO2 -- but that number 25x is OVER A 100 YEAR LIFESPAN that already INCLUDES the decay over those 100 years. So if you mention that half year is 10 years you also throw the number 25x out the window, then the multiplier is much much larger (forgot how much). Because of this scientists use different potebtial multiplier for CH4 for different time horizons. Anyway it IS a problem to have CH4 instead of CO2, how big a problem depends on your time horizon and over 100 years CH4 is 25x worse than CO2 INCLUDING decay.

You touch on the second point already. As long as lifestock is constant, CH4 is constant at a certain level. Still: Reducing lifestock will reduce CH4 to a lower constant level which will reduce greenhouse effects as CH4 decays to a lower stable level where emission and decay balance.

In a sense, reducing lifestock is the same as CO2 capture -- not the same as stopping to burn fossils.
How to Not Get Hit by Cars
For those wondering, Google translates this as "fuck you and fuck you."
Where science meets fiction: the dark history of eugenics
Has anything like this been done for simulating the economy of a country?
It isn't a synthetic example at all. We want two receivers of the same set of messages from the same set of senders to process them in the same order. Determinism is of utmost importance.

In your example, the vehicles' messages have no causal relationship; they are concurrent. Order does not matter. However, for the sake of determinism in a simulation, the above constraint is necessary even for concurrent messages.
That's a pretty inefficient space heater
You're unlikely to get hit by larger pieces of wood at high speed. Dust, small chunks, maybe a part of the saw may come flying at you, but i suspect they're way more likely than large wood chunks. But if you believe this photo was not staged, then safety goggles are pretty good https://external-preview.redd.it/qVMDLhaXQN8Vd9UI6d5fDswF396...
Is not so simple. Polar bears migrate to avoid the harsh season.

To survive, they need to cross a chilling open sea that is all except calm. They can swim for more than a week and more than 650Km non stop. This is what grants them the tag of marine mammals, and is well earned.

Finding a chunk of ice to rest and sleep in this travel can be the difference between surviving (at coast of a 20% of its fat reserves) or drowning in the sea, specially for cubs that often die in the travel. Less and less floating icebergs mean less bears surviving, until none will be able to swim so far without help. And then you have a big chunk of the population vanished in a couple of months.
>Prioritisation often becomes harder the closer you become to being an open source maintainer, since you're often more focused on software maintenance/internals than on using the software in real-life contexts

i contribute to a FOSS project. I am not a dev nor can i hire someone to do dev work so i assist the actual dev team into giving them real life use cases which brings out a lot of bugs which get fixed along the way.

That way, instead of trying to achieve some sort of tangent "idea" of what a software is going to be and it becomes something the users can actually use and relate to.

the software in question, when people are going to use it and will face "normal workflow bugs" for example, we can forget about adding new features. right? maybe they can go side by side but unless you are working on the bleeding edge software and do not expect anyone to use in production it can work but not otherwise.

Also, by pointing out edge cases, the present software itself would become what would be called "battle tested" because most if not all the issues are fixed.

that said, if a project had a good budget, a good roadmap, a thriving developer community and users who are using it, reporting bugs and people volunteering to fix stuff, we can think about experimenting but otherwise not
I am not a director of engineering at a large tech company. But looking at the profiles of those who are, I get the impression that in addition to having an amazing CV, those people have an excellent professional network. To an outsider it might look like a meritocracy, but it is most positively more about who you know, and how you connect socially, etc.

@drdunce, it really does depend where you are starting from. Regardless, start hustling your network and build up an incredible profile. A PhD + MBA might be useful but most certainly not sufficient.
I've been writing Go professionally for about 10 years now. I don't really buy your arguments against Go. Error handling is optional only if you explicitly ignore error results, and you can have the linter yell at you for that. The Go ecosystem is much larger and more mature, with many production-ready libraries available, and success stories everywhere you look. This article is a great illustration of how Rust just makes certain things hard, for better or worse: https://hirrolot.github.io/posts/rust-is-hard-or-the-misery-...

That being said, I think Rust is cool so I'll give you a hint. Go has a kryptonite: binary size. This didn't matter until recently when WASM runtimes became the new hotness. It is very very difficult to deploy Go on e.g. Cloudflare Workers. Even with Tinygo, it's a struggle getting your binary less than 1MB. Some features that make Go ergonomic like reflection (encoding/json package is a good example) ruin "tree-shaking" and bloat the binary.
If you're dead-set on using Rust, I'd try framing it in terms of edge computing. Rust is absolutely in a position to become the best non-JS language to use for these kind of 'workers' environments. And they have a lot of benefits: super fast, super cheap, effortless deploys, etc. so it's totally possible to make an argument for them. "Rust is the only compiled language viable in these environments"[1] is certainly a compelling position.

[1]. Hyperbole, I'm sure there's good progress towards getting others to work. For example, I'm currently working on adding Prolog support for Cloudflare Workers :-)
If you get phished or something, can attackers use this to turn off the car while driving? Or something lesd harmful like keep it on while you're at work and drain gas.
Sometimes it's not about what the public wants, but what it needs.
> Huh? Isn't the output of the linker roughly the same size as the sum of the inputs?

No. Linkers today even do link-time code generation. Debug info is gargantuan and can be kept as separate files too.
I looked at a company in this space and was quite surprised they never thought to check whether the vehicle was in motion during OTA updates. So much for risk assessment...
You got downvoted by people that know nothing about mining it seems.

And yes the auto switching which in this case is almost certainly nice hash is a joke. For years the only thing you would mine on a gpu has been ethereum.

Nicehash takes an absurd fee and their software might as well be return "Ethereum".
It's funny to read this article and thread while doing exactly what everyone suggests to avoid: building Kubernetes on bare virtual metal for a team with few programmers without any dedicated devops or SRE roles.

The reason I'm doing it is because our business owner thinks that we need scalability and high availability. We have law obligations to keep our data inside a country. And we don't have any managed Kubernetes offerings inside our country. The best cloud stuff I've found is hoster with openstack API and that's what I'm building upon. I thought really hard about going with just docker swarm, but it seems that this tech is dying and we should rather invest into learning Kubernetes.

Honestly so far I spent few weeks just learning Kubernetes and few days writing terraform+ansible scripts and my kubernetes cluster seems to work good enough. I didn't touch storage part yet, though, just kubeadm-installed kubernetes with openstack load balancer, calico network and nginx ingress. I guess hard part will come with storage stuff.

Worst thing is: everyone talks about how hard it is to run Kubernetes on bare metal, yet nobody talks about what exactly issues are and how to avoid them.
Capex is spending on your crap, ie buying it and maintenance. Opex is what you spend to run your crap.
> The combined brainpower working on Web3 is unprecedented.

The data that I have seen indicates that there are roughly 20.000 developers [1] actively working in the web3 space. Only Microsoft has roughly 100.000 software engineers.

[1]: https://cointelegraph.com/news/web3-developer-growth-hits-an...

> That rate of innovation pales in comparison to what’s happening around Web3; it’s nowhere near it. There are about 18.5K cryptocurrencies in existence (12K with a whitepaper), out of which about 10K are active in 2022, and the rate is increasing exponentially (about 50% of all cryptocurrencies on Coinmarketcap were listed in the last year).

So the allegedly unprecendented combined brainpower working on Web3 was able to come up with 18.000 different ways to market a distributed database, out of which only 12.000 could be bothered to even write a document describing how their database works and only 10.000 are still active, even with huge financial incentives.

That's a lot of innovation.
It was decided not to provide this link since the its demo become a separated project, i.e. ARElight.

Maybe it might be better to refer the particular demo from AREkit as well, so I will think about it.
Do you force the public to read it? Or just live with the fact you get dozens of views for news that took hours and thousands of dollars to create.
Agreed, there is no objective benefit to an (otherwise) advanced society in keeping slaves. But it is easy to imagine one that does because they like to.

When the Maori in New Zealand heard from the English about a peaceful society on Chatham Island, 800 miles east, before two weeks had passed they set out on an expedition to exterminate all the men and enslave all the women there.
Instead of talking about specific technologies/software/services, I'll give a quick rundown how you can achieve this in theory, and hopefully it can apply to whatever you're currently using.

The requirements:

- Your application should be able to run on arbitrary ports, preferably controlled with env vars or similar

- You need to have something in front of your application, like nginx or apache

- Whatever webserver you have should be able to "hang"/pause/suspend requests while you switch application version

- Each version you create needs to be concerned about what the previous version did. Breaking changes needs to happen across multiple versions, where you can soft-deprecate something, and a release after that, actually "break" it

- You need to have some sort of "healthchecking" that can tell you if the new version is OK or not

The implementation:

- You have Version 1 running of your backend on port X

- You want to deploy the new version, so you deploy it to your server but the web server in front still serves requests from Version 1

- Run healthchecks against Version 2

- Once they pass, tell web server to "pause" in-flight requests

- Switch web server configuration to use Version 2 application instead (this can be combined with the previous step, `nginx reload` would combine these for example)

- Stop Version 1 from running

- Repeat for each new version

And now you've achieved deploying a new version of your application without any failing requests.

(Sidenote: You can replace hanging/pausing requests with graceful shutdown of your webserver (meaning it waits for no pending requests) if you have a low amount of traffic)
OP was saying the death spiral will happen because miners will decide That the combination of BTC price and block fees is insufficient motivation to mine at present difficulty levels. This is effectively miners setting rates. I am saying that miners will act in self-interest and avoid death by suicide by enabling this deadly spiral by continuously turning off hardware during times of down trend.
> This is where yet another amazing open-source project comes in. It’s called MicroG. It’s basically an open source reimplementation of Google’s Play Services, APIs, and some of those services. We were talking about this before, that AOSP has APIs for everything. What MicroG does is it provides the implementation or everything that an app would expect from Google Play Services.

> But they implement push notifications. The way push notifications work is, say you are using WhatsApp. WhatsApp will send a notification to the Google servers, so MicroG has to talk to Google servers to get that notification, because that’s where WhatsApp sent it.

They address the privacy aspects of this, but I've been wondering what implications this has for control and stability of open-source android distributions.

With enough time and effort, you can certainly reimplement proprietary on-device APIs that commercial apps expect to be present - but Push is in a sense an "off-device" API: To send a push notification, an app's backend-server talks directly to Google's backend and submits a push request. Then, at a later time, some Google Play Services component on the device calls an internal API on Google's backend end fetches the enqueued push notifications for that device.

To get Google fully out of the loop here, MicroG would have to run its own backend server and convince the developers of every single app that uses Push to also send their push requests to MicroG's server in addition to Google's. That's of course practically impossible.

So what MicroG does instead is to call Google's internal API and fetch the enqueued messages from Google's backend like the original Play Services component would do. However, by doing that, they depend on Google's goodwill to let them use their internal API.

If Google some day decides that they won't let anyone else use their internal APIs anymore (either by doing some ML on the API server to distingish "genuine" Play Service clients from MicroG clients - or by threatening to sue MicroG), then all the alternative Android distributions would be instantly left without working push notifications.

If Google wanted to be insidious, they could even purposefully degrade service for MicroG clients - e.g. randomly hold back queued push notifications - to make alternative distributions appear unreliable.

I don't know if there are any other APIs besides Push which follow that same pattern.

That always seemed like a huge achilles heel to me.
"boost liquidity" what a wonderful euphemism
What does your current experience look like? It’s more about
Isn’t it not all fields? (Mostly?)
Language design is hard.
I still imagine Seinfeld doing this bit with an increasing intensity and widened eyes as it progresses to infinity.
> One of my most exciting trips was going from Southern to Northern Europe in just a week.

Now that is impressive. Do you remember your route?
The thing is, statistics is against you on this. You only need 1 instance of careless driver, 1 aggressive dog or clueless wild animal to have a relative high speed crash. In that case, your skills and experience will not matter.

Its all nice in echo chambers with heavy survivorship bias where everybody claims how they are fine (but had close calls here and there, often not even realizing them), but its far from reality. If you want some counter-balance (which most folks in these echo chambers really don't want), talk to some ER folks, or orthopedics.
I like what you're saying, but your woodworking metaphor falls a bit flat for me because it teaches me more about woodworking than about building IT infrastructure.
At least the heavy industry is fxkcing doing something.
I did a couple of 2000+ km tours in Europe on a... motorcycle. It's not sports, it has a big carbon footprint and gas can be expensive, but you can experience some of the same benefits: take less traveled roads, stop anywhere, meet people.

I ride a bike every day but only on short distances; on a tour I would be afraid of not being able to pack enough things (clothes, shoes...) But it's a neat idea.
Disassembled planets should be enough for anybody.