• 0 Posts
  • 16 Comments
Joined 9 days ago
cake
Cake day: January 21st, 2025

help-circle
  • 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.todaytoLinux@lemmy.mlframework 13 AMD... yay or nay?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    4 days ago

    I don’t have problems with high DPI … only problems I’ve come across is … I DID have scaling problems with Wayland

    This is exactly my point. You did have problems with high DPI. You had to fix some random config and avoid Wayland.

    I don’t want to deal with this. I want to be able to use whatever software I want and have it work with minimal or no extra “fixing”. I value this over slightly neater pixels.


  • paequ2@lemmy.todaytoLinux@lemmy.mlframework 13 AMD... yay or nay?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    4 days ago

    Here’s a screenshot I just took from my Framework 13. Notice how some of the text is clear, but the entire menu to the right is blurry.

    Common “fixes” are “move to Fedora” or “just enable some experimental flag in some random config”. This all misses the point though: I don’t want to have to do any of that. I just want a system that works with the most amount of apps.

    Of course, it depends on what you specifically value. For me, I value broader software compatibility over slightly neater pixels. Some people might like it the other way around. That’s fine, but it’s something important to know.



  • paequ2@lemmy.todaytoLinux@lemmy.mlframework 13 AMD... yay or nay?
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    3
    ·
    edit-2
    4 days ago

    I currently own a Framework 13… and… after daily driving it for a year, I decided I don’t like it.

    The deal beaker for me is the high dpi display. Linux just isn’t 100% compatible with hpi displays. I’m tired of my apps either having blurry fonts or tiny text. Ironic because hi dpi displays are supposed to look better.

    With Framework, you’ll be pushed into using Fedora (it doesn’t solve all the scaling issues) or pushed to stop using apps you like because they’re using older GTK (some times there are no alternatives). You’ll also have to dive into debugging scaling issues.

    I just switched back to my Dell XPS 13 9310 FHD and it was a breath of fresh air having everything just work. Any distro, any apps, no scaling debugging, text is readable and crisp, app UI elements look properly sized.

    I only ever switched out the modular ports once, but honestly it would have been better to buy a dongle instead because that would work on any computer.

    Oh, and I tried the higher resolution screen. It didn’t fix the scaling issues.

    Oh, and, I actually had a display fail on me! After like 8 months, half the display went black. Thankfully, they were nice enough to send me a free replacement, but it definitely left me feeling like the Framework isn’t that sturdy or durable.

    The shell also dents easily. I dropped a small music player from desk height onto the top lid and it left a small dent. (I have like 3 dents on the lid.)

    Repairability is the one feature that the Framework beats everyone else on, but to me the cons outweigh the pros.




  • Lab-grown rocks

    When I was getting married a few years ago, I remember thinking fuck real diamonds lab-grown are literally the same thing. I remember getting some push back from some weirdos about how “real” diamonds are some how better or how people will think I’m a cheapskate or how people will feel bad for my wife…

    Well, fast forward a few years and literally nobody cares, thinks about, or has said anything negative about my wife’s ring. We are both 1000000% happy and satisfied with the decision to buy lab grown.






  • 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