1. 2

    Also youtube-dl will download entire channels. I’ve done this for null byte’s channel

    1. 0

      We should all take a look at peertube. It’s matodon for video https://joinpeertube.org/en/

      1. 8

        We should all take a look at peertube. It’s matodon for video https://joinpeertube.org/en/

        1. 1

          It’s mastodon for videos, alright. Just like with mastodon, the people and foundations and so on that I want to follow is just not there. It sucks to be honest. I’m keeping the hope alive, though.

          1. 2

            You should ask them to move to mastodon. Actually would be nice to have some kind of petition asking people to move to mastodon.

        1. 0

          Sell me zsh. A few friends use it but they’ve not been able to clearly convey its advantages over ye olde bash that is just… everywhere.

          1. 4

            auto completion works even if you don’t type the string from the beginning. i.e. you have a series of folders

            /backup_images

            /backup_files

            /backup_videos

            you can do an ls and start typing videos and it will tab-autocomplete to the right folder. It was the one feature that signaled to me, you made a good decision to switch.

            1. 2

              If bash is good enough for you then you probably have no reason to switch.

              In the past I used zsh for some of its fancier features: I could do more expressive expansions to make my prompt pretty or do clever directory chomping; I found its completion much faster than bash, but that’s only useful if you use flag or subcommand completion; menu completion can be useful. I think also the history settings in zsh were or are more featureful than bash, but I’m not entirely sure what bash’s current features are like.

              I’ve been using bash just fine for the last ~10 years on personal systems but I do have zsh on some servers so that I can do more clever things with prompting.

              1. 2

                The main reason I used zsh was to handle correctly files with special chars in them ([ \t\n] for example). It also has “real” lists and associative arrays. Mainly it was often better to write scripts. After I also found that print in zsh is often better than echo. For example print -P "%Bsomething bold%b". Also things like ${fic:t} instead of basename $fic, ${fic:s/x/_/} instead of echo $fic | sed 's/x/_/' and a lot of small niceties.

                I no longer use zsh as my main shell, I switched to fish. Still I always preferred zsh over bash. But it was a long time ago, perhaps bash is better now.

                I use fish for basic usage (completion is great), but when I script I generally use zsh.

                1. 1

                  I’d start with the zsh-lovers document.

                1. 2

                  Got mine. Added a healthy donation to EFF as well. :party_parrot:

                  1. 1

                    https://niu.moe/@voodoologic

                    I’m going to keep using it b/c I’m creating my own private mastadon for friends and family.

                    1. 39

                      We need a name for this pattern around network protocols: “Embrace, Capture, Break away, Lock-in”

                      • Embrace a communication standard
                      • Capture: attract a large user base
                      • Break away: break backward compatibility and/or provide a worse UX for those outside of your walled garden
                      • Lock-in: corner in the userbase

                      Google did this with Google Talk vs XMMP, email (try running your own mailserver), AMP, RSS…

                      1. 14

                        Email is still mostly unmolested if you understand the security and spam context; it’s not that google made it impossible to run your own smtp server, but in order to do so and not get flagged as spam, there are a lot of hoops to jump through. IMHO this is a net benefit, you still have small email providers competing against gmail, but much less spam.

                        1. 15

                          Email is mostly unmolested because it’s decentralized and federated, and a huge amount of communication crosses between the major players in the space. If Google decided they wanted to take their ball and go home, they would be cutting of all of Gmail, Yahoo mail, all corporate mail servers, and many other small domains.

                          If we want to make other protocols behave similarly, we need to make sure that federation isn’t just an option, but a feature that’s seamless and actively used, and we need a diverse ecosystem around the protocols.

                          To foster a diverse ecosystem, we need protocols that are simple and easy to implement, so that anyone can sit down for a week in front of a computer and produce a compatible version of the protocol from first-enough principles, and build a cooperating tool, to diffuse the power of big players.

                          1. 9

                            So how do you not get flagged for spam? I want to join you. I run my own e-mail server and have documented the spam issue here:

                            https://penguindreams.org/blog/how-google-and-microsoft-made-email-unreliable/

                            The only way to combat Google and Microsoft’s spam filters is sending my e-mail, texting my friend say, “Hey I sent you an e-mail. Make sure it’s not in your spam folder.” Usually if they reply, my e-mail will now get through .. usually. Sometimes it gets dropped again.

                            I have DKIM, DMARC and SPF all set up correctly. Fuck Gmail and fuck outlook and fuck all the god damn spammers that are making it more difficult for e-mail to just fucking work.

                            1. 3

                              Forgive the basic question: do you have an rDNS entry set for your IP address so a forward-confirmed reverse DNS test passes? I don’t see that mentioned by you in your blog post, though it is mentioned in a quote not specifically referring to your system.

                              It’s not clear who your hosting provider (ISP) is, though the question you asked them about subnet-level blocking is one you could answer yourself via third-party blacklist provider (SpamCop, Spamhaus, or many others of varying quality) and as a consequence work with them on demonstrable (empirical) sender reputation issues.

                              1. 8

                                Yes I’ve been asked that before and haven’t updated the blog post in a while. I do have reverse DNS records for the single IPv4 and 2 IPv6 addresses attached to the mail server. I didn’t originally, although I don’t think it’s made that big a difference.

                                I’ve also moved to Vultr, which blocks port 25 by default and requires customers explicitly request to get it unblocked; so hopefully that will avoid the noisy subnet problem so often seen on places like my previous host, Linode.

                                I think a big factor is mail volume. Google and Microsoft seem to trust servers that produce large volumes of HAM and I know people at MailChimp that tell me how they gradually spin up newer IP blocks by slowly adding traffic to them. My volume is very small. My mastodon instance and confluence install occasionally send out notifications, but for the most part my output volume is pretty small.

                                1. 8

                                  Email is inherently hard, especially spam filtering; Google and Microsoft just happen to be the largest email providers, so it appears to be a Google or Microsoft problem, but I don’t think it is.

                                  E-mail was once the pillar of the Internet as a truly distributed, standards-based and non-centralized means to communication with people across the planet.

                                  I think you’re looking through rose-tinted glasses a bit. Back in the day email was also commonly used to send out spam from hijacked computers, which is why many ISPs now block outgoing port 25, and many email servers disallow emails from residential IPs. Clearly that was suboptimal, too.

                                  Distributed and non-centralized systems are an exercise in trade-offs; you can’t just accept anything from anyone, because the assholes will abuse it.

                                  1. 4

                                    Cheap hosting is very hard to run a mailserver from because the IP you get is almost certainly tainted.

                                    Having valid rDNS, SPF & DMARC records helps.

                              2. 13

                                It’s also not really a Google issue; many non-Google servers are similarly strict these days, for good reasons. It’s just that Google/Gmail is now the largest provider so people blame them for not accepting their badly configured email server and/or widely invalid emails.

                                I’ve worked a lot with email in the last few years, and I genuinely and deeply believe that at least half of the people working on email software should be legally forbidden from ever programming anything related to email whatsoever.

                                1. 2

                                  In other words, Google didn’t have to break email because email has been fundamentally broken since before they launched GMail.

                                  Worse, newer protocols like Matrix and the various relatives of ActivityPub and OStatus don’t fix this problem.

                                  1. 7

                                    Matrix, ActivityPub and OStatus don’t fix Email? Well it’s almost as if they are trying to solve other problems than internet mail.

                                    1. 3

                                      You completely and utterly missed the point.

                                      Mastodon, Synapse, and GNU Social all implement a mixture of blacklists, CAPTCHAs, and heuristics to lock out spambots and shitposters. The more popular they get, the more complex their anti-spam measures will have to get. Even though they’re not identical to internet mail (obviously), they still have the same problem with spambots.

                                      1. 11

                                        Those problems are at least partly self-inflicted. There’s nothing about ActivityPub which requires you to rehost all the public content that shows up. You can host your own local public content, and you can send it to other instances so that their users can see it.

                                        Rehosting publicly gives spammers a very good way to see and measure their reach. They can tell exactly when they’ve been blocked and switch servers. Plus all the legal issues with hosting banned content, etc.

                                        1. 3

                                          You’re acting as if that ONE problem (abusive use) is THE only problem and the rule and guide with which we should judge protocols.

                                          While a perfectly reasonable technocratic worldview, I think things like usability are also important :)

                                          1. 9

                                            In general, you’re right. A well-designed system needs to balance a lot of trade-offs. If we were having a different conversation, I’d be talking about usability, or performance, or having a well-chosen set of features that interact with each other well.

                                            But this subthread is about email, and abusive use is the problem that either causes or exacerbates almost every other problem in email. The reason why deploying an email server is such a pain is anti-spam gatekeeping. The reason why email gets delayed and silently swallowed is anti-spam filtering. The reason why email systems are so complicated is that they have to be able to detect spam. Anti-backscatter measures are the reason why email servers are required to synchronously validate the existence of a mailbox for all incoming mail, and this means the sending SMTP server needs to hold open a connection to the recipient while it sifts through its database. The reason ISPs and routers block port 25 by default is an attempt to reduce spam. More than half of all SMTP traffic is spam.

                                            If having lots of little servers is your goal, and you don’t want your new federated protocol to have control under a small number of giant servers, then you do need to solve this problem. Replicate email’s federation method, get emails emergent federation behavior.

                                    2. 5

                                      XMMP has a lot of legitimate issues. Try setting up a XMMP video chat between a Linux and macOS client. I’d rather lose my left arm than try doing that again.

                                      1. 7

                                        Desktop Jingle clients never really matured because it wasn’t a popular enough feature to get attention.

                                        These days I expect everyone just uses https://meet.jit.si because it works even with non-XMPP users and no client

                                        1. 0

                                          I just got jitsi working w/ docker-compose meet.dougandkathy.com – not headache free, but no way I could build it myself

                                        2. 1

                                          Audio, video and file transfer is still very unreliable on most IM platforms. Every time I want to make audio or video call with someone we had to try multiple applications/services and use the first one that works.

                                          1. 0

                                            Microsoft Teams does this pretty well, across many platforms. Linux support is (obviously, I guess) still a bit hacky, but apparently is possible to get to work as well.