um… did my bio get deleted?

  • 0 Posts
  • 36 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle


  • Save yourself a lot of trouble and get a hardware SIP phone like the Grandstream WP826. I spent years struggling with software phones, most of them suck ass and the good ones aren’t very good.

    quick unboxing video

    Then make sure to enable voice transport encryption and set SIP transport to TLS (not UDP) and set keepalive timers to something below 3 minutes or so. The encryption settings are not just for security, using TLS for SIP transport has way fewer problems with incoming calls than UDP in 2025 network environments.

    There are some firmware issues with the Grandstream WP826 but they are steadily releasing new firmware updates every month or two. If you need absolute bulletproof reliability go for something more expensive, otherwise the WP826 or similar model will likely be good enough (I say that as someone who is easily vexed by shitty software/electronics)



  • There have in fact been huge discussions of this in the past, which maybe you’d already know about if you didn’t come in hot mouthing off about how things need to be changed to fit your preferences immediately, chop chop!

    Turns out the type of blocking you want requires a great deal more code than you (clearly) can imagine in order to be actually functional, as opposed to a fig leaf requiring the full cooperation of every server involved.

    This was discussed ad nauseam maybe about 5 years ago, with long hellthreads in microblogging fedi, complex deep-dive technical blog posts, the whole nine yards. No I didn’t save links and I wish I had because this and related issues (Mastodon’s fig leaf “privacy” settings, E2EE DMs) keep coming up.

    The answer is that what you are asking for can either be implemented as a porous fig leaf which falls apart the very first time some asshole spins up an instance which doesn’t respect it and vacuums up your posts en masse, or it can be implemented using cryptography which requires an enormous amount of work by extremely well-educated CompSci types to implement a standard, and then implement code libraries, and only then can the developers of platforms like Lemmy and Mastodon get started on implementing the actual feature. No one is paying anyone to do this, and it’s not clear that people with the necessary expertise are even available to develop the standard and the code, nor is it clear that everyone would adopt it if they did. So up til now, it hasn’t been done.


  • If I block someone on Mastodon or another Fediverse microblogging instance, they’re blocked. Because that part of the Fediverse was built by people who had been harassed and doxxed off other platforms.

    Evidently you missed the many (many) discussions that took place maybe 5 years ago by some of those exact builders about how this is, and remains, only a fig leaf which requires every server to cooperate in maintaining the illusion.

    I wish I’d saved links based on how often this comes up. There are fundamental issues with how federated systems in general and ActivityPub in particular work, and “real” blocking is one of them. People running other instances can modify the code however they want, and no technical measures have been implemented (because it turns out to be very difficult to do so) to prevent any node operator from removing the fig leaf.






  • Currently in a holding pattern because, while I got RAM & SSD for a new-to-me “1-liter” server before tariffs hit, I don’t have the server itself nor any money to buy one, despite looking for 9th or 10th gen Intel which will cost me only $120 to $150 barebones.

    Money to buy one is not coming in because the place where I live has nonstop noise & activity and I don’t have a separate room or any door I can close, which severely limits my ability to work as I have auditory hypersensitivity and an absolute need for solitude in order to recharge enough to think. 🤷🏻