As others have also mentioned, Minoxidil can be effective at slowing or stopping balding, with daily application, though it isn't immediate (may take a couple of weeks to start showing results). It can vary a lot from person to person, so give it a shot for a couple of months before deciding whether to commit or not.
While the issue of the inter-server protocol being overly chatty is very much real, putting the burden on the users isn't a good solution.
The focus should instead be on improving the protocol itself and its implementation with better algorithms, batching, etc. I'm not super knowledgeable about the inner workings, but I feel like there's still some relatively "low hanging fruits" in the protocol design (are activities properly batched? are they sent as linear broadcasts to all federated instances? could we use some alternative broadcast distribution, like binomial? etc) and implementation (is the data model leading to some expensive operations? are the SQL queries well written? could we speed them up some other way?).
I say this as someone who's been running an instance for many years now, and can tell you for sure it has been a rather bumpy ride, as a small server. Running a good and fast server with lots connections is not cheap; not as much as it should, at least imo.
You're correct, but that's like saying along the lines of manufacturing a car is just bolting and soldering a bunch of stuff. It's technically true to some degree, but it's very disingenuous to make such a statement without being ironic. If you're making these claims, you're either incompetent or acting in bad faith.
I think there is a lot wrong with LLMs and how the public at large uses them, and even more so with how companies are developing and promoting them. But to spread misinformation and polute an already overcrowded space with junk is irresponsible at best.
I've been getting into the habit of also using em/en dashes on the computer through the Compose key. Very convenient for typing arrows, inequality and other math signs, etc. I don't use it for ellipsis because they're not visually clearer nor shorter to type.
That is not really true. Yes, there are jump instructions being executed when you run interference on a model, but they are in no way related to the model itself. There's no translation of weights to jumps in transformers and the underlying attention mechanisms.
This. And to add to what other commenters have said, by using Bitwarden and paying for their Premium plan (very cheap, just $10/year), even if you don't use all their features, you're supporting a good project. It's critical infrastructure, I think the price is more than fair.
Either way, you should always make periodic backups from any cloud service you use, encrypted of course.
This would be really neat, however it's not trivial to sell those everywhere. If you're lucky to live in a country or even city where they can get those to, you're golden. If you don't, you're screwed.
Unfortunately, as much as I love the idea and tech behind Monero, actually accepting it is not practical at all, as the coin is used a lot for criminal stuff and is thus very strictly followed by many agencies. We don't know if they can break it, but even they don't, businesses can get a rough treatment just for accepting Monero. It's perfectly understandable if they'd rather not do it.
Very useful, even for someone who has been using Linux for many years. Sometimes you just forget or need that tool you rarely use. tldr can be much handier than parsing a man page when you're in a pinch.
I use the tealdeer implementation, but any is fine really.
Wait what? Was there ever an option to open a private tab as a normal tab?? 🤔
I'd love to have that, but thought it would never get added. What version were you on before (and in which one are you now)?
Adding onto what's already on the thread, you can try look at the newer Element Call, which is an implementation of Matrix's native calls.
I've been using it a bit recently, since Jitsi seems to have stopped working reliably for me (to be frank, I've not put much effort into debugging it yet). It works well, but it's still early stage, lacking some features Jitsi has. If that one works for you, I recommend you stick to it.
Not exactly. Matrix 2.0 relates to the protocol (Matrix) version, which has its major number incremented due to a bunch of, well, major changes/updates to make it much better. OIDC, sliding sync and native calls are some of the new things that comprise the 2.0 update.
The server implementations are somewhat orthogonal to this. Synapse (the original Python server) is still the main implementation, and is Matrix 2.0 ready.
Yes! Oh my, I'm silly; that was precisely my point and I managed to mess it up 🙃
Thank you for the correction!