RymdLord

joined 1 year ago
[–] RymdLord@beehaw.org 1 points 10 months ago

I reason it this way. If like they say in the video email is one of the most critical parts of privacy (I 100% agree with that) then why don't they support the only privacy currency? Also why pay for email well simple I both want the features that paying gives you but anything free either you are the product or others are indirectly paying for me. I want my email provider to not spy on me and sell my data so why not give my money to a provider that proves that they protect it? I chose Tuta.com instead of proton because of this. And to make it clear Tuta.com doesn't allow monero payments but their official reseller proxysto.re does allow monero! Also it's not hard to add monero as a payment option :)

[–] RymdLord@beehaw.org 7 points 10 months ago (2 children)

They have searched for Victor

[–] RymdLord@beehaw.org 1 points 10 months ago

It's one of the most asked for features since 2018, and there isn't even a minute for it?

[–] RymdLord@beehaw.org 1 points 10 months ago (2 children)

If email is so important for privacy then why can't I pay for it in a privacy protecting way?

[–] RymdLord@beehaw.org 15 points 10 months ago (1 children)

I like the policy of "Be Nice" even when I get annoyed that I can't down vote. Tho a ultimatum like this would make me switch to another server. Why? Well first of all Lemmy is supposed to be federated imagine if Google did this with gmail, it would not end well. Secondly even if I like content from Beehaw communities I do enjoy and contribute to other instances, and would not follow BeeHaw if it where to defederate. The reason I chose and have stayed on BeeHaw is that ultimately it was my choice to use this instance and follow the rules, defederation would not allow me the freedom to be anywhere but on BeeHaw, and that sounds like the walled garden that I left behind. And those platforms end up hurting people allot. I would hate for BeeHaw to end up like it, and would way less be there to see it happen.

TLDR: I want the freedom to chose the rules I want to abide by and would not support this. And would migrate to another instance if this where to go forward.

[–] RymdLord@beehaw.org 7 points 10 months ago (1 children)

This is correct! Also wanted to recommend Jellyfin instead of Plex Or Emby

[–] RymdLord@beehaw.org 2 points 11 months ago

I have used it and cannot recommended it. If I was you I would buy a Google Pixel Tablet and then Install GrapheneOS or CalyxOS on it.

[–] RymdLord@beehaw.org 1 points 11 months ago

Yeah I would always recommend hosting locally and then if you want external access use wireguard

[–] RymdLord@beehaw.org 1 points 11 months ago

Calm down. Don't expose anything without allot of consideration. Also why do you want to expose it to the internet?

[–] RymdLord@beehaw.org 0 points 11 months ago

What? I'm so confused what IPs are allowed on your VPN "client" and "server". I think something is very wrong.

[–] RymdLord@beehaw.org 1 points 11 months ago* (last edited 11 months ago)

Well experience and the concept of pods

Edit: Just reread my response and thought it was quite bad so with this edit I hope to fix it. To answer your question regarding a one node setup with K3S compared to Docker Swarm is the following. When you later might want to expand your cluster or swarm K3S will be more flexible due to how it is built (Its architecture). Also you get the advantage of what is called pods that have way more isolation when setup correctly. Also if you use something like Harvester by Rancher or Proxmox you can turn one server into several this would allow you to have a several nodes and therefore also load balance and higher availability. I suggest you check our Kubernates(K8s) and K3S documentation and get to know the architecture of it! And the last and probably bigest advantage is that you will learn K3S and therefor K8S, this is a skill that is sought after in the IT industry!

I hope this is a better response :)

 

Its only beehaw that doesn't load. Can someone help?

view more: next ›