I thought Monero solves this issue, with a level of effort large enough that it’s almost impossible to crack.
I thought Monero solves this issue, with a level of effort large enough that it’s almost impossible to crack.
Any app that you can setup Macros with. I use Macrodroid on Playstore.
This one’s full of examples https://lemmy.world/c/bestoflemmy
https://feddit.de/comment/8071252 https://infosec.pub/comment/5269310 https://programming.dev/comment/5789966
These are just some random threads I saved. As others have pointed out, niche communities are (usually) the least toxic. Applies to any site or chatroom.
I haven’t heard of this before. How does it compare to Obsidian or Notion?
They just preferred to use WhatsApp. Switching to an alternative was trivially easy. People just didn’t want to because of personal preference. It would be trivially easy for me to stop drinking coffee every morning and only drink water
It’s not about personal preference. It’s about momentum. If I stop drinking coffee, only I am being affected. If I stop using Whatsapp, I now have to convince everyone I’m in contact with to also use the alternative when msging me before I can actually stop using WhatsApp.
If you want it to be a public utility and its owned by an American company, which country is going to be the one to make that happen?
I am confident the EU could do it. A complete transfer of ownership isn’t necessary for other countries to use exported services as public utilities. Public-private partnerships exist.
Also, calling “completely eradicating the first amendment in order to make it so that the American government can forcibly seize and censor people on its new state run social media websites” a “government problem” is an atomic bomb level of understatement.
“American freedom of speech = Nazis get to speak” was your stance before. Now it’s "Anything but American freedom of speech = government censorship". What am I even supposed to say here?
First off, I think you are being very rude. I didn’t call you names or make assumptions, so please treat this with more respect than a Twitter thread.
WhatsApp, by comparison, is trivially easy to replace.
Olvid, a French alternative to WhatsApp, was made in 2019. It took a law passing last month banning all ministers from using non in-house messaging services to stop people from using WhatsApp. I wouldn’t consider that “trivially easy”.
Also, your reasoning is kind of skewed, because in order to even use something like WhatsApp, you need other, already existing services. Namely internet access.
You didn’t mention Internet access and so neither did I. I’m happy we both agree it should be a utility.
I don’t know if you’re just speaking from a non-American context, or just don’t know how “freedom of speech” is codified into law in the United States.
I already said this is a “government problem”. I said this in reference to the US government, because this isn’t really an issue for most countries :/
When businesses ask you to contact their help-desk via WhatsApp, it’s a utility. When people call and message friends, family, and colleagues almost exclusively on WhatsApp or Messenger, it’s a utility.
It’s also putting the government in a position in which it functionally would have to provide a platform for everyone equally, Neo-Nazis […]
Godwin’s Law People preaching [insert terrible belief] on a government platform would be removed and charged for hate speech just as much as they would be if preaching these things in public spaces. If your government gives people with terrible_belief.jpg the chance to preach on public property, that’s not a public property issue, that’s a government issue.
Ultimately, saying social media should be a public utility is like saying casinos and strip clubs should be public utilities.
No, it isn’t. If anything, turning certain popular social media apps into public utilities would limit them from being pure dopamine hits. Let other websites exist to fill the cesspool void. Not the one my grandma uses.
I much prefer it over grub. I don’t think there’s any other bootloader’s that support btrfs snapshots.
I think flatpaks are good. The performance penalty for containerized software can be felt much more when you’re not using a good CPU. So containers do not “solve” my use case.
Could you pass me a link to an example setup?
I didn’t know about it, thank you for showing me this.
How does my point relate to HTML tag metadata?
I don’t think Lemmy or Mastodon would be a good place to start necessarily. Don’t be discouraged, I just mean that I think this should be something separate, like a library,
True. I meant suggesting this idea for generally any website that uses tagging. Will update post to show this better.
As a code library it could be maintained elsewhere and let these folks keep working on their projects.
We would need a group like the Wiki Foundation to set this up. Though I wouldn’t know how to pitch this.
😔
This place is more techy, but please don’t assume. I have no idea what you’re arguing for.
That is more of an argument involving the implementation of tags in general within the federation. But to answer your question:
Let’s say a group of people were to make a post on Mastodon with the tag #girls_night. How will all instances agree on the tag being correct?
The simple answer is they won’t. If a tag is contentious, it will be like any other drama between instances.
It’s the same for implementing tag hierarchy. Let’s say there is a default setup. Then if a tag or a tree of tags is contentious, each instance can include or exclude as they see fit.
Two new tables for “tags” would be required. One for instance wide tags and one for community tags.
a curated list of tags users can attach to their posts. The list of tags can be maintained by both admins and moderators allowing for each community to tailor tags to their specific needs.
It’s not what I was suggesting, but this should definitely be implemented for Lemmy.
I’m talking about how some tags should directly relate to one another, and how this should not always be the case in vice-versa. The system I’m suggesting is less useful when you limit the scope of tags (as the RFC does), but you can’t really do that for user-centric websites like Mastodon.
I think I’ll make an edit to clarify this in post.
“subvolume - cannot be snapshotted if it contains any active swapfiles”
Make a subvolume only for the swapfile.
has a chance to fragment
This is true for all files. Is it a bigger problem for swap?
has issues with hibernation (that I’ve personally encountered multiple times)
This one I can’t refute. How long ago did you have these issues?
It sucks, I don’t see how it could ever get past this.