- WHOIS privacy is like the most common feature among registrars?
- Mail forwarding isn't always free but pretty common too
- According to dongleauth DNSimple, Gandi, Namecheap, and Porkbun also support webauthn right now (hover plsss)
valpackett
joined 1 year ago
Hair removal is hair removal, there's no need for "trans services". You're not obligated to out yourself to the professionals.
One bit of laser advice: do ask the person doing it to use more power!
Look for used ThinkPads with Ryzen, I bought an L14g2 (5850U+16GB) for about 600 USD and it's just amazing value
Dang, quite the big name to come to blahaj! Niceeeee :3
On Firefox Android, adding to home screen is basically just a shortcut to open a very slightly app-ier tab (no browser toolbar, notification to copy the URL). Otherwise it's equivalent to normal browsing, so yes, your extensions work as usual. (Just checked myself with Tampermonkey).
No, there's no additional information about your phone, that doesn't exist.
Huh. Thanks. I don't think I've had this problem with all kbin instances…
You can actually literally watch marcan/lina/(more rarely)alyssa from asahi work on livestreams :) No, they don't actually do that kind of clean-room. There's no issue with learning about how the hardware works and directly applying that to writing drivers! Hardware and drivers aren't even comparable, they're complementary. One basically cannot infringe on the other.
Clean-room techniques come from actually cloning very similar things. Basically the original Phoenix BIOS cloning IBM. As a more recent example Wine/ReactOS.
Oh cool… mm, do we have a GNOME forum on this here threadiverse?
Huh, right now it just went down indeed lmao, but all the times I've been trying I could open https://fedia.io/m/firefox just fine
I've been doing that search many times over the last week! It's just not connecting to that instance.. Could you please check the logs?
Again, only for things that you specifically want shared between threads.
There's no "the" refcount in Rust, anyhow. If you just instantiate some container or your custom data struct, like let mut x = Vec::new(); – it's very local to where you are, it's on the stack, it's not reference counted at runtime at all, you cannot pass it between threads (if it's not Send it cannot EVER cross a thread boundary in safe Rust). The standard library provides two ref-counter containers. Rc is just a basic refcount that is not thread-safe and thus also is not Send and won't ever be allowed to cross the thread boundary in safe Rust. Arc implements atomic-based thread-safe ref-counting and thus is Send, implementing what you're talking about, but as an opt-in per-object container, not as some behind-the-scenes global feature.
That refcount++ and refcount-- needs to be synchronized between threads
Only for things that you specifically want shared between threads – namely this (synchronized refcount) is an std::sync::Arc. What you want to share really depends on the app; in database-backed web services it's quite common to have pretty much zero state shared across threads. Multithreaded environment doesn't imply sharing!