1. 16

    I personally like the path that gnome is on. I get that not everyone does and that’s fine, but ever since gnome 3 I’ve really fallen in love with gnome.

    1. 2

      I used to be very anti-gnome (“you’re turning my desktop into a phone?!”), but I’ve been using gnome for like three months because I wanted to actually give it a chance after using contrarian window managers for like a decade. I threw on dash to panel, made it very un-gnomey, etc. Gnome 40 came out and broke basically every extension, but I didn’t have time to transition to anything else at the time, so I was forced to just run with them turned off. With nothing more than the Yaru-remix shell/gtk/application theme running I started to really like how default gnome 40 looks and feels with just one theme and a few extra keyboard shortcuts turned on. Pretty sure even after all the recommended extensions start getting fixed I might stick with this.

      1. 2

        The problem is that their hold over GTK means that every other DE is forced to either follow suit in whatever Gnome comes up with, or invest in expensive workarounds (see CSD).

        I encourage Gnome devs to do whatever they want, but as a non-Gnome-user it gets tiring to be at the receiving end of their “innovations” without having much choice. I just want to be left alone.

        1. 5

          It’s far from only GTK. Their hold permeates the stack and slowly but surely forces more and more of these things to fit a certain mold as their ‘vision’ (OSandroidX with glaucoma) can only really be fulfilled with strong coupling across a wide range of desktop-system services. What little competition is left will be forced to write adapters (eudev, elogind, …) until they architecturally become more or less the same but lagging behind, accept obscurity, or run out of steam entirely and join the retro-computing trend.

      1. 19

        I love Alacritty, the only thing I’m still missing is ligatures support.

        1. 1

          There’s a fork that keeps up-to-date with upstream that adds ligature support. I seem to remember seeing an explanation several months ago for why it (or something like it) hadn’t been merged in but I don’t remember and can’t seem to find it right now. The only discussion I can find about it is a brief talk in upstream’s pinned ligature issue.

          But it works for me with Iosevka. I have no idea how other fonts are working, but half of the reason I use alacritty is that this fork exists and is one of the only terminal emulators I could find (outside the ones bundled with DEs) that actually has ligature support.

          1. 2

            Thanks! I think that this is the reason? (harfbuzz only works on linux/bsd. On other platforms core text and direct write should be used.)

        1. 1

          How do you prevent self hosted mail from getting caught in a spam filter? I never quite understood how to prevent that.

          1. 6

            Easy, you don’t.

            There’s a lot of stuff you can do to reduce the likelihood:

            • setup DKIM
            • setup SPF
            • ensure DNS is setup (MX record for your domain pointed to your email server, A/AAAA for your mail server set (e.g. if your mail server says it’s name is mail.example.org, an A record for mail.example.org is connected to the IP it’s sending out from), optimally set reverse DNS to match
            • make sure the domain you’re using is clean (not something you normally need to care about of you’re using a domain you’ve owned for ages that’s particularly unique, but could run afoul of a blacklist if you’re buying an aftermarket domain or an available domain that’s changed hands in the recent past)
            • make sure the IP your mail server uses is clean (generally not a huge issue either, but some providers are notorious for having whole IP ranges blacklisted)

            But at the end of the day, Gmail, Outlook(/live.com/Hotmail/MSN), et al. are still gonna think you’re suspicious until they’ve started seeing users interact with you / flag messages you send as “not spam”.

            In my personal experience Gmail is more lenient than Outlook at “first time sender” type stuff, but all the big players generally care just as much about your domain/email server’s “reputation” with them as they do about the technical correctness of your setup.

            1. 7

              I’m going to say that again, and again, and again… That’s an argument for hosting your own email, not against it. Every self-hosted email user giving up and switching to one of the oligopolists is a win for the oligopolists.

              Dropping mail from self-hosted servers is a way for them to get more users (all while often cheerfully accepting spam from hijacked accounts on big services, including their own). Whether they are doing ot intentionally or not doesn’t matter—they are aware of the problem or could easily find out if they wanted to, but they are doing nothing to improve the filters to actually detect spam.

              1. 5

                Something I don’t think gets mentioned enough to go along with the domain part of this is that a lot of the new, hip, trendy TLDs are instant points dinged against you for the configurations of SpamAssassin et al that a lot of incoming mail servers use.

                I messed around with Mail-In-A-Box for half an hour or so on a fresh .space domain one time a little under a year ago and took a peek at a SpamAssassin score test to see why mail to my own Gmail was bouncing (not just getting filtered to spam), and it turns out you can be half done for from the start if you don’t have a domain on a tried-and-true TLD. Even with DKIM etc all configured and clearing SpamAssassin properly, my score was only in range to hit the spam filter instead of bouncing, and it still bounced on Gmail, although that may have had to do with the now-repeated attempts to get through, or maybe some caching of my untrusted status from when DKIM wasn’t set up properly(?). In any case, between IPs, TLDs, and resold domains, it’s wild how easy it is to end up in a situation where there’s nothing you can do about how spam filters see you, even if you’ve never sent spam in your life.

                1. 1

                  I had the same issue in the past when I owned arrrgh.pw (I know, it makes a pretty cool email !). Turns out .pw is simply blacklisted in most email filters, and I could never get a single mail delivered. Someone then told me it’s because these TLDs are cheap, and heavily registered for spamming purposes. Big mailers simply spamlist them by default just in case. The advice that came after that was to choose a domain that’s not cheap (~30$/year), and fo with it. I did that, and never had a problem with getting my mails delivered since.

                2. 2

                  make sure the IP your mail server uses is clean

                  That is why I send my mail through Mailgun for a small mailing list I host privately (ie the VM relays through them).

                  1. 2

                    In my personal experience Gmail is more lenient than Outlook at “first time sender” type stuff, but all the big players generally care just as much about your domain/email server’s “reputation” with them as they do about the technical correctness of your setup.

                    True. One thing that helps is to have a GMail sender mail you a few times to your own domain ; or if you have an account there, set it up to forward every email it gets to your personal address. I guess you could do the same-ish with Outlook, etc. Still annoying.

                    I once worked for a mail-delivery shop, and both Microsoft and Google provide tools for “professional senders” to monitor their IP addresses reputations, and ensure that the customers’ email blasts hit the inbox. You kind of have to be a pro player to be able to send “bacn” at will, but if you’re trying to share baby pictures with grandma, you’re out.