• 7 Posts
  • 229 Comments
Joined 3 years ago
cake
Cake day: June 8th, 2023

help-circle


  • Sometimes I feel embarrassed, because people see me, see that I’m female, and I worry they automatically assume I’ve got a rotting crab factory somewhere.

    You can stop worrying, this never happens. Nobody is going around assuming people will probably smell like fish at normal social distances because of their sex. That’s not a thing.

    Do people think vaginas in general might smell like fish, like if you go and stick your nose in one? Yeah, that’s a common factoid or comparison. But anybody who is looking at you and thinking of what your crotch might smell like at a distance of 2cm is not someone you want within 100m of you anyway.

    If it really bothers you, take up some kind of smelly shampoo or perfume or something. Then you can know you are thought of as “the person who always smells like peaches” or whatever.






  • Meshtastic’s not really a company exactly. MeshCore exists if you don’t like it.

    Semtech does IIRC have patents on and make all the LoRA chips. But the patents will expire eventually, and the LoRA chips they make are well-behaved modules that do what you tell them and not locked-down bits of nonsense that are a pain to work with. The data sheets for the modules are easy to find, and you’re not stuck messing around with firmware blobs you need to load into things. You can get boards with the Semtech radios on them from a whole bunch of manufacturers. You’d be hard-pressed to find a competing radio tech with modems available at a similar price point that we “should” be using instead.

    And while the ability to use any link for e.g. Reticulum is nice, it also means that without coordination you have no idea what link you should use, and so you can never see anyone because you have no idea what technology or even what LoRA channel to look for peers on.

    And Meshtastic now can go over UDP anyway.


  • In terms of the transport, sure.

    But if you put the password in a URL, the user’s browser is going to turn around and store that plaintext password in its history, then sync it to the user’s other devices, and then pop it up on their screen in the address bar autocomplete, perhaps when the user is screen sharing or streaming to hundreds of people. The browser does not expect a password to be stored there and will mishandle it.




  • dist-upgrade must die.

    I spent like three hours I didn’t have the other day trying to bring a Debian Unstable system up to date, it decided to stop every few packages to tell me it failed because the t64 libraries conflict with the regular ones and nobody taught apt how to figure that shit out for me and install the right ones.

    Even Ubuntu is like “oh hey there’s a new release, you’re available for three hours straight to, every two to fifty minutes, explain to a TUI dialog that you don’t have an opinion, right? Oh also can you resolve this merge conflict on this config file we think you edited, but you didn’t, by being shown the diff once and then opening nano?”

    This is not an acceptable way for this to go.