I haven't used any flatpacks, mostly because they don't seem to have a good solution for running terminal programs. (Also I don't like that the application developer chooses the permissions to expose rather than the user.
However, I have been using bubblewrap which is what flatpack uses under the hood to sandbox. This allows me to run both gui and non-gui programs, and I have the control of exposing the minimum required permissions that I'm comfortable giving an untrusted piece of software.
I seem to be in the minority here but I personally prefer using $ and # to denote root. I like this because not everyone uses sudo and might not even have it installed.
That being said, if you already have other commands that are using sudo -u ... to run commands as a different user then it might be best to just be consistent and prefix everything with it, but if there is only a few of those maybe a # cp foo bar && chown www-data bar is an alternative.
Rust has a strong emphasis on strongly typing constraints. So if a collection of fields are always some/none together having them listed as separate options in the struct means there is some assumptions you are making that the type system isn't aware of which can lead to pain and bugs in the future.
I agree that separate types with Into sounds like a nice solution to me, it would be good to see the error the compiler is giving you (or if you can a minimal reproducible repo). If you absolutely can't make it work, a single Option<Inner> at least would be more correct as all the fields on the inner struct would be optional together.
I never understand people's obsession with buying things on amazon
it has a nice working sync of connection profiles (even of ssh keys…encrypted!)
Sorry, but what on earth does this have to do with a terminal emulator? Something like this makes way more sense as a separate tool. It's like if I was making a decision of what video player to use because it can sync my browser bookmarks.
The way I remember the order is that the parentheses around the link would make grammatical sense outside of markdown (the goal of markdown is to still be fully readable even when looking at the raw source).
For example if I were posting on a forum that didn't have markdown support which one of these would make more sense:
You can find that on this lemmy instance (https://lemmy.world).You can find that on (this lemmy instance) https://lemmy.world.Option 2 makes no sense grammatically. Then you just need to use the square brackets (which rarely show up in non-markdown text) to denote the link range.
Alternatively, if you still have a hard time remembering the order, you can use reference-style links which make it even more readable outside of markdown rendered contexts (note that there are no parentheses in this version, nothing to get confused):
[Here is a link][1] and [here is another link][2].
[1]: http://example.org
[2]: http://example.com
Seriously, I can't think of a single good reason to use amazon in 2023. Not only are they usually more expensive than buying directly from a manufacturer or other retailer, but you run the risk of getting a counterfeit item and not notice within the return window. Not to mention the fact that you're contributing to the further monopoly they have on online retail. Support smaller online retailers, almost all of them have a return policy equal to amazon's.
Hah, too late. You're already being linguistically fingerprinted by your grammar and word choice. Only option now is to not comment on public forums anymore I guess. 😩
Invidious is just a frontend to Youtube like Teddit was a frontend for Reddit. It's not federated, and Google can and will do everything in their power to make it suck. Just like how Reddit will now destroy Teddit next month.
Peertube is the federated option for video hosting/sharing. But of course, like everything else currently controlled by the centralized mega-corporations, there is a huge network effect hurdle that users need to overcome to get their content off of the user-hostile megacorporations (Youtube) and onto the federated alternatives (Peertube).
I see invidious/teddit/nitter/quetre/rimgo/scribe/libremdb as stop gap band-aids to temporarily give power back to the users, but in the end the owners of the content have full control over stopping these.
This is why it is so important that we promote federated networks like lemmy, mastadon, matrix, peertube, etc... Otherwise the entire internet will be a user-hostile cesspool.
It's a VFX shot duplicating I10 in downtown LA a few times to make it look way wider than it actually is by Corridor Crew.
There's no way of knowing, which is the whole problem with their model and why a lot of us self host things in the first place. Even if they super duper promise not to use the data, they could be lying. And if they are actually true to their word today, that could change tomorrow.