Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Julian Oliver (julianoliver@mastodon.social)'s status on Saturday, 16-May-2026 10:23:30 JST Julian Oliver

   in reply to

   @dalias I host sensitive data on some jurisdictionally appropriate (for threat model) DCs, & for clients (usually NGOs), FDE or with strongly encrypted data partitions on bare metal, a good IDS, & administered over self-hosted VPN. In other cases I host at home or in studio.

   Hosting on-prem has its own unique & considerable risks if doing at-risk work, especially if that work is in the jurisdiction you live in.

   In such cases better OpSec is to host over the border, in a resistant jurisdiction

2. Embed this notice
   Janneke (janneke@todon.nl)'s status on Sunday, 01-Feb-2026 20:04:50 JST Janneke

   in reply to

   @civodul
   Love it, count me in.

   In fact, I love it so much I even created a pull request for it's siblings peek-error and pke!

   https://codeberg.org/guile/guile/pulls/67

3. Embed this notice
   Dr. Quadragon ❌ (drq@mastodon.ml)'s status on Friday, 12-Dec-2025 08:52:42 JST Dr. Quadragon ❌

   in reply to

   @Truck As for "I don't want containers" - I understand. Neither do I.

   But truth be told, we kinda brought them on ourselves. It's because of lack of standardisation also. Every distro is trying to be its own platform. They're mostly the same, but they're different enough to be incompatible on packaging level. This distro uses APT, this distro uses RPM. Some distros follow Posix/HFS, some deviate. Some install onto the base system, some install into /usr/local subtree. There has never been a high-level meeting of, say, Debian, Redhat, BSD and Arch communities to decide that we can't afford fragmentation like this, let's decide on unifying our tools.

   And those little wrinkles kept accumulating, until the most obvious answer for a universal Linux package turned out to be a container fat enough so those wrinkles don't matter anymore.

   It's sad, but that's the cursed world we have to live in.

   In a way, I see flatpak as a stepping stone to something better than this.

   @lanodan @lritter

4. Embed this notice
   Mother Bones (_l1vy_@mstdn.social)'s status on Wednesday, 11-Jun-2025 15:01:42 JST Mother Bones

   in reply to

   #Via Lorenna Cleary
   @LorennaCleary
   June 10, 2025, 6:42 PM

   "In LA the horses are headed in.

   In Santa Ana protesters square off against an unknown force. They are not city cops and I can’t tell if they’re ICE either. But then we can’t really identify ICE. It’s all the same now."

5. Embed this notice
   valhalla (valhalla@social.gl-como.it)'s status on Wednesday, 29-Jan-2025 02:44:16 JST valhalla

   This afternoon I've received 5 sensors of a certain type¹ I've bought in the weekend.

   They were in individual plastic bags (purple), I've put them all in a single plastic bag, and put the bag back in the box they came in.

   In the last hour or so I've taken one of them out, connected it to the microcontroller on a breadboard I use for these things, programmed it to use it, it worked. Then I decided to take another microcontroller whose sensor² was broken, and change it with one of these.

   So I picked up the soldering iron, all of the accessories, and changed³ the board that connects the microcontroller and the sensor, soldered headers to *another* one of the new sensors, and update the firmware, and everything worked.

   And now I wanted to put away the remaining ones in their right place, and I can't find them anymore.

   They aren't near in the box, they aren't near the upgraded microcontroller, they aren't in the plastic box where they are supposed to end up

   Aaaand thanks everybody, while writing this I looked under the soldering mat (which I had put back into its place) and the sensors were there!

   ¹ BME280 on a breakout board, but that's not the issue
   ² SHT20, it had started to give absurd humidity values
   ³ it's an I2C device. There are 4 pins. *why* is everybody putting them in different combinations??? why can't they settle on something like always putting them in the same order??? (maybe the one used by easyC / StemmaQT, since it's already out there?)

6. Embed this notice
   SwiftOnSecurity (swiftonsecurity@infosec.exchange)'s status on Sunday, 12-Jan-2025 12:32:12 JST SwiftOnSecurity

   in reply to

   In this non-enterprise scenario there are basically 6 broad layers this problem could be. Application, Security, OS, Network device, or Server. Many paths. It can be paralyzing, this is where experience comes in.

   In large incidents you may encounter varying levels of "hot potato" between departments where no path is selected because there is no incident command. You can learn to be that person.