Yeah, it’s federated, meaning you can subscribe to each of them and post to whichever one you fancy. If you want to post to multiple, it’s a good idea to use the cross-post feature.
Having only one singular official community would be rather bad, as then the respective server owners and moderators would have central control like on Reddit.
Hmm, yeah, it is a bit surprising to me, too, especially for an audio issue, but it’s always possible that you had some weird configuration values in about:config for historic reasons and now some new code, that came in with a Firefox update, isn’t working with that configuration.
Either way, it happens often enough that Mozilla has a troubleshooting routine for it, too, namely refreshing your profile.
If I remember correctly, it places your old profile data into a folder in your Desktop folder. But you can also separately backup your profile by closing Firefox and then copying ~/.mozilla/firefox/ onto an external hard drive or such.
Does it also still happen in fresh profile? It will be like a factory-reset Firefox (except that you can go back to your current profile), so then it definitely wouldn’t have anything to do with your Firefox configuration.
Does the problem still happen in Troubleshoot Mode?
Well, if you’re self-hosting GitLab, there might not be much of a difference. Codeberg is hosted by a non-profit organization, so you don’t have to self-host it.
The open-source software that it uses, Forgejo, is also more so developed by the community, rather than just one corporation, who could change the license for future updates at any point.
Huh, so Tony Hoare invented null and then Graydon Hoare invented Rust, immediately terminating the existence of which does not have a traditional nullnull value.
LTT is Linus Tech Tips. It’s more of an entertainment channel with technology flavor. They’re pretty terrible when it comes to actual technological understanding.
Yeah, that is my understanding, too. Otherwise you’d only want to generate them on the database host, as even with NTP there will be small differences. This would kind of defeat the purpose of UUIDs.
If you’re saying that even without NTP, just by manually setting the time, things will be fine. I mean, maybe. But I’ve seen it far too many times already that some host shows up with 1970-01-01…
For others wondering what’s wrong with UUIDv4:
UUID versions that are not time ordered, such as UUIDv4, have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.
I guess, this means with these new UUIDs, ideally you only create UUIDs on systems that are hooked up to NTP, though I guess, it won’t really be worse than UUIDv4 either way.
We’ve been using Leptos at work, which is a similar framework (and probably shares half the stack with Dioxus).
And yeah, it’s really good. My favorite thing about using Rust for the UI is algebraic data types.
So, in Rust when you call a function which can fail, there isn’t an exception being thrown, but rather you get a Result-type as return value.
This Result can either contain an Ok with the actual return value inside. Or it can contain an Err with an error message inside.
So, in your UI code, you just hand this Result all the way to your display code and there you either display the value or you display the error.
No more uninitialized variables, no more separate booleans to indicate that the variable is uninitialized, no more unreadable multi-line ternaries.
It just becomes so much simpler to load something from the backend and display it, which is kind of important in frontend code.
It’s not a dual-language platform, though. You write the backend and the frontend in Rust. The frontend code is compiled to WASM to serve it to the browser.
Making the API version a feature flag is a very interesting idea.
Excuse me, Windows is the cheap copy of KDE.
Various ant species do a similar thing where their soldiers have really big, flat heads and when their nest gets attacked, the soldiers stick their head into the entrance way, so the attackers can’t come inside.
Apparently, this kind of behaviour is referred to as phragmosis.
I mean, I doubt the Windows support is particularly solid here either. Using shell commands to formulate tasks will never be great for Windows, because the shell ecosystem is simply Linux.
Your comment is perhaps a bit confusing without a link: https://just.systems/man/en/
There’s not exactly a dichotomy there…
Hmm, you must have misread something. It translates to “mouth bags” or more specifically “mouth-of-an-animal bags”.
I mean, these communities do get created when someone feels like there’s a reason to. There’s just no council or whatever regulating when and where a community gets to be created, so any user on any instance can decide to open up and promote their community.
And frankly, I have no idea what the precise effects are. When you subscribe to all of these, it won’t really be much different from just one big community in that sense. It may mean, though, that someone new accidentally joining only one of the communities will not be presented all the content they want, yeah.
On the flip side, having it split is kind of cool, because you can decide to only subscribe to 2 out of 4 communities, if you only want half as much of this content in your feed. Or you can decide to subscribe to all of these, but not to the one on
angry-instance.net, because you don’t like the tone of the discussions in that one.