Sharing != downloading forever. When you browse it, yes, technically it's in your cache, but that's why it's called a cache. Most people won't install a client that puts their browsing into long-term storage (unless Microsoft takes a screenshot for them and promises never to upload it somewhere). Regardless, it is still a security issue (as I just described with releasing the encryption key). You can choose to ignore it, until someone comes along and exploits it. Then you have a bunch of angry people screaming at you because you "didn't close an obvious security hole".
I remember thinking about this long time ago and even asking some hackers about it to get blank stares back. Basically, there are multiple problems around data access.
Take the simple scenario of a unfriending. Let's say you have 12 friends, but Susie turned out to be a real bitch and you unfriended her. You don't want Susie to have access to your photos, messages, and basically anything anymore! That means the encryption key has to change -->
Where is all the data hosted and who is going to reencrypt all the entire history from the point Susie became your friend until you unfriended her? The most secure would be that you have all your data and that you re-encrypt it. Great, you are data-frugal and have maybe 10MB you have to re-encrypt. But Karl, your photography pal paid for gigabytes of storage and now has to rencrypt a good chunk of that if he unfriends somebody.You could of course say "fuck it, the asshole friend probably made a copy and re-encrypting is pointless", but then your ex-friend can just share the private key with the world and TADA, everybody has access to the files you shared with said friend.
And that's just one problem I can think of right now. When you take more time to think about it, you'll run into more and more stuff.
I'm not saying it's impossible, but it definitely isn't easy. Add to that that many people don't care and it's less likely. The closest I get to that is Signal.
I'm not saying "immediately". He can take his time and make a decision or wait to see if they'll pester him further or if it'll even go to court.
For me, I'd just not bother with being in the unknown and just change the name to something unique, so that next time someone comes along, I can tell them fuck off because I did my research.
While unfortunate, it seems like a legit case. Especially given how similar the apps are. One character off is quite confusing for a potential customer 🤷
I'd just rename the app and move on. Pick a different name that doesn't come straight out of the English dictionary and is unique.
proc macros can be called in tests and debugged. They aren't that horrible, but can be tedious to work with. A good IDE makes it a lot easier though, that's for sure.
Defining run is definitely the quick way to do it 👍 I'd love to have a proc macro that takes a bash like syntax e.g someCommand | readsStdin | processesStdIn > someFile and builds the necessary rust to use. xonsh does it using a superset of python, but I never really got into it.
I'd use clap, yeah. And env vars std::env::var("MY_VAR")? You can of course start writing your own macro crate. I wouldn't be surprised if someone already did write a proc macro crate that introduces its own syntax to make calling subprocesses easier. The shell is.. your oyster 😜
May I introduce you to rust script? Basically a wrapper to run rust scripts right from the command line. They can access the rust stdlib, crates, and so on, plus do error handling and much more.
I honestly don't get why people like Go. Structural typing makes it so difficult to find classes that interpret an interface. Every dumb go project has to be opened in an IDE or something with a language server to find implementors of an interface. Also, forcing every capitalised object in a module or struct to be exported is just... wat? Returning a tuple of whatever, err also feels wrong. It's like they couldn't decide between throwing exceptions or an enum and went with something in between.
I get that the inbuilt concurrency features are nice, but the rest of the language and stdlib feel very lackluster. At least that's my impression after ~2 weeks of it. My retreat to Rust was rather quick.
Maybe it’s sharing public keys in person time again.
IIRC, Briar requires (or at least required) you to exchange keys face to face and verify them before starting communication. Maybe that changed, but it looked like the most convenient app to communicate in such a manner. But Signal also has key verification so...
In the United States, for example, the non-adjusted average woman's annual salary is 79–83% of the average man's salary, compared to 95–99% for the adjusted average salary
I had a look at NetBSD and FreeBSD: I don't think they are in a better position than linux honestly. NetBSD still uses CVS and mailinglists for contributing.
An addition or change to the existing source code is a somewhat trickier affair and depends a lot on how far out of date you are with the current state of FreeBSD development.
Both might be even be worse than linux in terms of ease of contributions...
Sharing != downloading forever. When you browse it, yes, technically it's in your cache, but that's why it's called a cache. Most people won't install a client that puts their browsing into long-term storage (unless Microsoft takes a screenshot for them and promises never to upload it somewhere). Regardless, it is still a security issue (as I just described with releasing the encryption key). You can choose to ignore it, until someone comes along and exploits it. Then you have a bunch of angry people screaming at you because you "didn't close an obvious security hole".
Anti Commercial-AI license