𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍

       🅸 🅰🅼 🆃🅷🅴 🅻🅰🆆. 
 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 𝖋𝖊𝖆𝖙𝖍𝖊𝖗𝖘𝖙𝖔𝖓𝖊𝖍𝖆𝖚𝖌𝖍 

Ceterum Lemmi necessitates reactiones

  • 4 Posts
  • 253 Comments
Joined 3 years ago
cake
Cake day: August 26th, 2022

help-circle
  • Hold on a tick.

    Specifically blacklisting a group of users because of the technology they use is, by definition, “targeting”, right? I mean, if not, what qualifies as “targeting” for you?

    And, yeah. Posting a sign saying “No Nazi symbolism is allowed in this establishment” is - I would claim - targeting Nazis. Same as posting a sign, “no blacks allowed” - you’re saying that’s not targeting?

    I know we’re arguing definitions and have strayed from the original topic, but I think this is an important point to clarify, since you took specific objection to my use of it in that context; and because I’m being pedantic about it.


  • No.

    Use S/MIME or PGP and directly encrypt emails to your recipient. This is the only E2E encryption available to email.

    The best metaphor for email I’ve found is that you’re writing your message on a postcard and handing it to your neighbor closest to the destination, who hands it to her neighbor, and so on, until it gets there. There are usually fewer hops, but also your email is broken into packets which could go through god knows how many routers, each of which can read your email.

    E2E requires setting up a private key; RFC 821 provided no such mechanism. Your only option is out-of-band negotiation, like PGP.

    There is a good proposal out there that sets mail headed announcing that you accept encrypted emails, and includes information about your ID, which clients could parse and verify against public key servers; it hadn’t really gained a lot of traction, as it causes issues for data harvesters but also at the end user side. Like, how is notmuch and mairix supposed to handle these? They’d need permanent access to your private key to decrypt and index the emails, and then now your index is unencrypted.

    There’s been a fair amount of debate about this, and it’s a lot of work that would need coordinating between teams of volunteers… it hasn’t made much progress because of the complexity, but it’s a nice solution.


  • I know that none of them use a VPN for general-purpose browsing.

    Interesting. The most common setup I encounter is when the VPN is implemented in the home router - that’s the way it is in my house. If you’re connected to my WiFi, you’re going through my VPN.

    I have a second VPN, which is how my private servers are connected; that’s a bespoke peer-to-peer subnet set up in each machine, but it handles almost no outbound traffic.

    My phone detects when it isn’t connected to my home WiFi and automatically turns on the VPN service for all phone data; that’s probably less common. I used to just leave it on all the time, but VPN over VPN seemed a little excessive.

    It sounds like you were a victim of a DOS attack - not distributed, though. It could have just been done directly; what about it being through a VPN made it worse?








  • I am really confused. Every shell over used has had a command history. zsh takes it to the next level, with optional history syncing between running terminals. Histories are always persistent, unless you unset HISTFILE. I’ve got my HISTSIZE set to an absurd 10,000 commands, with uniqueness enabled. Ctrl-R lets you autocomplete type-ahead search through history. Tools like fzf can make it marginally better, but ^r has nearly always been enough. You have !? history searching; !nnnn for referring to commands by number, the history command to actually print out all of you history which you can then grep.

    Most of this has been available in shells at lest since the mid-90’s, when I really started using Unix in earnest.

    So I’m really confused about why you think shells haven’t had persistent histories. What’s new or different about this thing to which you refer?

    man bash or man zshall and /HIST, and that’ll get you started.


  • Canonically, moving during transport is pre-TNG, even. It first appeared in one of the TOS-cast feature films - maybe even the first: “The Motion Picture.” I don’t recall off the top of my head. But pattern buffers themselves I think weren’t “invented” until after the TOS generation. Probably introduced to address the horribly transporter accidents that could occur, as in the films. Anyway, I don’t think they had the buffer technology before TNG, and I don’t think it affected one east or 'tother whether people could move and talk during transport. I think that was more a result of the capabilities of period FX.


  • I can second tsmu. However, it does require some thoughtful use.

    I usually compare it to GMail, which was the pioneer of eliminating folders. notmuch also does a good job here. tmsu isn’t quite as effortless - granted, it has a harder job in having to support multiple file types, not all of which are automatically indexable - but for tmsu to be effective I find I have to make extra (non-trivial) effort to manually tag files. Rather than, say, gmail and notmuch, where I only care about tags when I’m searching. buku is similar, although it’s somewhere in between; you can get by without manually tagging, but it isn’t perfect, and manually tagging is still better and isn’t a much extra work.



  • If Jekyll isn’t your jam, then Hugo probably won’t be, either.

    I have a simple workflow based on a script on my desktop called “blog”. I Cask it with “blog Some blog title” and it looks in a directory for a file named some_blog_entry.md, and if it finds it, opens it in my editor; if it doesn’t, it creates it using a template.md that has some front matter filled in by the script. When I exit the editor, the script tests the modtime and updates the changed front matter and the rsyncs the whole blog directory to my server, where Hugo picks up and regenerates the site if anything changed.

    My script is 133 lines of bash, mostly involving the file named sanitization and front matter rewriting; it’s just a big convenience function that could be three lines of typing a little thought, and a little more editing of the template.

    There’s no federation, though. I’m not sure what a “federated blog” would look like, anyway; probably something like Lemmy, where you create a community called “YourName”. What’s the value of a federated blog?

    Edit: Oh, I forgot until I just checked it: the script also does some markdown editing to create gem files for the Gemini mirror; that’s at least a third to a half of the script (yeah, 60 LOC without the Gemini stuff), which you don’t need if you’re not trying to support a network that never caught on and that no-one uses.