![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/f3189f30-f8c8-4c4f-b957-e3a7bfd1c784.png)
Used by search engines for listing which pages should be indexed.
Used by search engines for listing which pages should be indexed.
Did you install from Google Play?
Open the Play Store link on your phone - the automatic update process has been thoroughly broken for at least a year.
If you installed from f-Droid I have no clue - I use stock android without any alternate stores set up.
@dessalines@lemmy.ml released v0.0.51 in mid December, but I think it only reached Google Play on Dec 18th. I’m not sure when/if it was pushed up to f-Droid.
There are some minor issues, but largely it works fine for me on instances running 0.19
Good idea but sadly not feasible
Relevant part (credit to [deleted] and u/chiagod):
Assuming D-T fusion, a single fusion event releases a 14.1MeV neutron and a 3.5MeV helium nucleus. Assuming you can absorb all this energy and you’ve got an efficient heat engine setup at around 50%, you’ll get about 1.5x10^-12 J per fusion, so for a 1GW output you’ll need 6.67x10^20 fusions per second. Say you have 1TWe (electric output) worth of fusion reactors worldwide (about half of current electricity generation), then you’re producing 1000 times as much helium, or 6.67x10^23 atoms per second. About a mole each second, or 4 grams. This works out to 126 tons of helium a year, or about 1000m^3 per year of liquid helium. The US strategic helium reserve had a peak volume of about a billion m^3 . World consumption of helium is measured in tens of millions of m^3 per year so you’d be short by several orders of magnitude in the best case.
TCP Selective Ack is very much a thing, but it does take extra memory so lots of TCP stacks exclude it or disable it by default.
TCP was never designed with wifi in mind. TCP retransmission was only ever meant to handle drops due to congestion, not lossy links.
Tmux is a wonderful complement to mosh. Together you get persistence even when your local client loses power (speaking from experience)
I worked with mosh for years to connect to servers on other continents. It was impossible to work otherwise. It only has two small warts: forwarding, and jump hosts.
The second is fixable/ish with an overlay network, but that isn’t always an option if you don’t control the network. I tried to solve this with socat but wasn’t able to configure it correctly - something about the socket reuse flag was very unhappy.
If you really want to maximize your impact, check if your employer or professional association have donation matching for various large charities.
There are obviously many more charities - these are two that I believe have the highest chances of actually reaching civilians in Gaza and not being diverted.
Also that in order to exploit this it requires an active man in the middle. Which requires any of the following:
Almost all of those have decent mitigations like 801.x and BGP monitoring. The best mitigation is that you can just change your client config to disable those ciphersuites though.
You clearly haven’t watched your forklift safety video. Warning: blood starts a few minutes in.
Memes at home are made with 100% creatitity
I was not expecting the drama around it. Is the issue truly a different orthography or is more like a different font/ligature issue?
EDIT: forgot the article I found on it: https://restofworld.org/2021/tulu-unicode-script/
Performance Improvement Plan. Basically HR collecting evidence so you can’t sue after they fire you.
Thank you.
I hold out hope that they will reform their values and can be refederated in the future, but I doubt that will happen.
It’s a tribble. Give it some food and in a few minutes you’ll need to make it double
The OOM killer is usually triggered after it starts hitting the disk. Which means your system is unresponsive for a long time until it finally kills something.
Using something like oomd can help trigger before it hits swap but then why are you using swap in the first place?
The bigger issue is that the kernel sometimes ignores the swappiness and will evict code/data pages long before file cache even when set to 0 or 1. I’m still not sure if that was because of an Ubuntu patch or if it was an issue that’s been resolved in the years since I last saw this
Nope. Bitkeeper used it in the master-slave pairing and the term was carried forward. Gitlab did a whole writeup about it.