Just use the Mutex from the parking_lot crate.
Just use the Mutex from the parking_lot crate.
The only time I’ve ever needed a Mutex<()> so far with Rust is when I had to interop with a C library which itself was not thread safe (unprotected use of global variables), so I needed to lock the placeholder mutex each time I called one of the C functions.
Actually I think in this case you’re still better off using a Mutex with “data” inside. I’ve done this before. The idea is that you make a unit struct MyCFuncs
or whatever and then you only call the C functions from methods of that unit struct. Then you can only access those methods once you lock the Mutex and get the instance of the unit struct. It feel elegant to me.
New fetch just dropped
The expect lint is really great, been looking forward to that for a while.
Still waiting for more flexible const generics 🤞
it wouldn’t make sense for the server to hold your private key, since that would mean the owner of your instance could make posts as you.
I mean, this is quite normal and common for all traditional social media (or any site really) you sign up for. It’s what most ActivityPub instances do too, though there’s nothing in ActivityPub that requires the server to hold the private key. It could in principle be held by the client but I don’t believe there is any implementation that does that currently.
But what if the server that holds the cryptographic keys is suddenly gone? Then what?
Or does Bluesky use client-held keys? I just think client-held private keys is probably too complicated for most people to realistically and safely use.
Right, of course. I don’t really see any way any protocol can get around that though. If the original server is suddenly just gone, there is no way to tell it to move your account elsewhere. Hopefully such a situation should happen very rarely though.
ActivityPub actually has a similar mechanism of a “Move” activity. There are just very few implementations that support that kind of thing.
That’s… exactly what I’m saying. Did you misunderstand my comment perhaps? Normies are not “choosing” not to learn, they just literally don’t have the tech literacy skills to easily participate in the fediverse. The fediverse should improve its UX to allow more people to participate.
I think I’m probably closer to the normies than the stereotypical tech-literate Mastodon person.
Just from the fact that you are here, it is statistically likely that you are much closer to the tech literates than the normies. Can you search for a specific email in your email inbox? You’re already way ahead of many people. You are severely overestimating the technical literacy of normal people.
Seriously yea. Same reason Linux user experience is generally bad. Unfortunately engineers usually make for poor designers.
I’m pretty dumb and uneducated
Statistically speaking, the mere fact that you are here indicates that you are among the top percentages of tech literal people. This isn’t necessarily about intelligence or general education, but about tech literacy.
Well, only techno-pessimistic about mainstream technologies that are used by most people, which is warranted I guess. Most people don’t use the fediverse after all.
The use of open, decentralized platforms such as the fediverse is one small step in the right direction at least.
Jesus Christ Fedi
I once again encountered something where const generics for something other than the current supported types would be awesome but alas… Guess I’ll live with the inconvenience for now.
I don’t think it should have an emoji either, but how does this rule apply to real currencies being emojis? I mean there is dollar banknote 💵 and yen banknote 💴 and euro banknote 💶 as separate emojis, not just a general money one. And honestly, even most of the emojis referencing anything that has to do with money uses dollar signs, i.e. $. Were these rules made after these emojis were already added?
Do any of them have public transport directions?
Security concerns? Closed-source software is a security concern in itself!
They were also plain C functions in my case, but it doesn’t take too much discipline to only call it through the struct. Also, you can put the struct in a different crate which includes the C bindings to ensure that you can’t call the C bindings without the struct.