• 0 Posts
  • 20 Comments
Joined 9 days ago
Cake day: January 21st, 2025
  • paequ2@lemmy.todaytoNo Stupid Questions@lemmy.world•Isn't having your own domain name for email very bad for privacy? And how do you pick a good domain name that doesn't sound goofy?English
    7·
    16 hours ago

    Good questions!

    But problem is, all my email address would be @mydomainname.com instead of @protonmail which millions of people use. Isn’t that just linking all your account together.

    I mean, yeah. You can’t setup sockpuppets on the same service. It’ll be obvious it’s the same person. And if someone is tracking you across services, it’ll be way easier to find you. This is a con.

    I would recommend not picking a domain with your real name, like smith.com or john.com. Even though it does seem popular to have me@johnsmith.com. It won’t solve the issue you noticed, but it’ll mitigate it a tiny bit.

    its hard to even pick a name that sound good

    Also, true. Ideally, you pick a common word with normal spelling that doesn’t have a homophone that’s not embarrassing to say to random people on the street. It would be awkward to be applying to a job or a loan and have to say your email is “john@piggy.park”. Also, you will have to speak your email over the phone at some point, the shorter and easier it is the better.

    I would also recommend picking a domain with either .com or .net TLDs. Some companies blanket destroy your email if it comes from some weird TLD like “.party” or “.xyz”. Omg, specifically, .xyz I think has been linked to tons of spam. Bigger companies will handle this more gracefully (put it in spam). But smaller companies, like my local garbage company run by normies, will just not deliver the email. (And debugging why emails don’t get received is really hard and annoying.)

    Unfortunately, a lot of people squat domains, so finding a short, simple, easy domain is really hard. I’m curious what other people do. Maybe other people just have me@reallylongdomainthaticanactuallyget.com? Or maybe other people have had better experience with john@mail.club? Or maybe some people don’t care that their domain is john@boss.baby?

    Ultimately though, having email independence is valuable enough for some folks to be OK with the downsides.

  • paequ2@lemmy.todaytoSelfhosted@lemmy.world•Lemmy selfhost hintsEnglish
    27·
    4 days ago

    Shortcut: use Tailscale to create your own private network and avoid hosting on the big, bad Internet. Otherwise, you really have to be careful on how you protect your services.

    Minor downside (or upside) is that you’ll have to install the Tailscale app on each device you want to make part of the network.

    This made hosting at home a lot easier for me.

    Update: Ah! I misread the post. Tailscale doesn’t make sense for this use case. My bad! 😅

  • paequ2@lemmy.todaytoProgramming@programming.dev•sourcehut is super confusingEnglish
    6·
    6 days ago

    Create a new repo locally.

    git init
git add .
git commit -m "Initial commit"

    Then to create a new remote repo, you can do this.

    git remote add origin git@git.sr.ht:~user/my-new-repo
git push origin main

    You’ll get a message that says.

    remote: 
remote:         NOTICE
remote: 
remote:         You have pushed to a repository which did not exist. ~user/my-new-repo
remote:         has been created automatically. You can re-configure or delete this
remote:         repository at the following URL:
remote: 
remote:         https://git.sr.ht/~user/my-new-repo/settings/info
  • paequ2@lemmy.todaytoSelfhosted@lemmy.world•A collection of 150+ self-hosted alternatives to popular softwareEnglish
    1·
    6 days ago

    Interesting! I didn’t realize this! https://www.gnu.org/licenses/why-assign.en.html

    only the copyright holder or someone having assignment of the copyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors.

    So it seems like the FSF does this in order to be able to enforce GPL. Buuut, these guys really gotta be the exception. I feel like the probability of the FSF selling out and going full corporate evil is pretty low…

    a good idea to have a CLA so that’s no conflict that the project owns the code.

    That’s exactly the problem though. The project owning the code, instead of the contributors owning the code.