u/stray_r

See https://www.reddit.com/r/transgenderUK/s/gYaw58zTDS

I am holding in my hand (metaphorically, I'm typing) a (literally) shiny new perks card with the name Stray (placeholder for my meat space name), disproving their claims that I can't get a perks card with my preferred name on it.

I further received a call from Monzo today, wherein they appear mortified that this has happened and stated "yes we take pride in our support of the LGBT community".

I don't have a resolution yet.

My Monzo card reads Mx Stray Redditor (well not quite but you get the idea). It has done since I changed my name from Handmedown Familyname V.

I need to refresh my card, it's close to expiry and looking quite tatty and the magstripe is broken even when I enable it in the app.

I thought I'd save money as well by trying a perks package that has things I'd buy anyway. On trying to order a shiny new card I'm offered a choice of "Legal Name: Stray Redditor" or "Preferred Name: Stray"

Ok, I can fix this, I try setting my preferred name to "Mx Stray Redditor" which is what I think they did when I did my deed poll. I'm messaged by someone (through the Monzo app) telling me they need me to reauthenticate with a picture of me and my ID. I'm asked to retake this photo repeatedly because my driving license is inconveniently shiny, and then they start trying to tell me that it's a change of legal name I need to do and not a change of preferred name.

My driving license of course says Mx Stray Redditor.

I assume that I'm dealing with someone that doesn't understand how titles work and that Mx is a title, and they realise that this information is already on all my existing cards and offer to send me out a new card. I explain that's what I was trying to order, and then they start insisting that only legal names can go on cards. Even after I show them the option to order a card with the options described above. I get passed through to someone else who doubles down on this. Despite being presented with relevant screen shots of the app and complete history of chat with support.

At least they didn't ask me for a GRC.

I'm really disappointed in Monzo.

I did what I set out to do. RAC Insurance (a trading style of BISL) now accepts the title Mx and presumably no longer collects or uses information on gender when creating insurance quotes. I think this is a win.

Go compare, and many other comparison sites now accept the title Mx, although some of the still ask for unlawful information. Go Compare still demands anyone using the title Dr record their details as Dr (male) or Dr (Female).

The Ombudsman thinks £150 is appropriate compo for unlawfully refusing service. This is less than a previous decision in 2022 (not me) and less than I got taking Trans(phobic)Union to the ombudsman (yet again, investigator's opinion was accepted, din't get as as far as ombudsman decision) for refusing to remove searches with multiple incorrect titles made on my credit file by BISL, which hasn't really been addressed here, and a lot less than I got from PayPal (opinion again) where they made up an incorrect title for me and transmitted it to Trans(phobic)Union. (Can you tell there's a theme here?)

I think this is a shit response from the ombudsman, who simultaneously "make findings on individual cases" and insist "the £150 sum offered by BISL falls within our range of acceptable compensation for distress and inconvenience"

Do I take the cash, buy a Blahaj and cake and send the rest to mermaids? or politely tell the ombudsman that £150 is an insult for refusing business on the grounds of characteristics protected by the equality act?

Highlights of a very long response from the ombudsman are below:

> BISL has confirmed that, at the time Mx Stray attempted to generate insurance quotes, neither the aggregator nor the direct site would have offered a Mx option. In addition, BISL has confirmed that the selection of one of the available title options would’ve automatically populated the gender field with either male or female.

...

> Lastly, as Mx Stray themselves has highlighted, their primary concern in this case is the principle at stake rather than the personal receipt of compensatory funds, as demonstrated by their suggestion during correspondence with our investigator that a charitable donation of sufficient magnitude would suffice. I have both admiration and sympathy for Mx Stray’s position here, which I surmise arises from a strongly principled stance on this matter and also a desire that any financial consequence for the business be significant enough to prompt meaningful change.

"An appropriate apology in this case would be a donation of £1000 to Mermaids UK" is my standard response to derisory "have a chocolate biscuit and go away" responses.

...

> Furthermore, and this is something to be celebrated, I understand that the meaningful change Mx Stray might’ve hoped to prompt has already occurred and that the relevant systems have been updated to include Mx title options. Given the timing, it is not unreasonable to assume that Mx Stray’s feedback may have played a part in bringing about this update. Whilst it would not have been in my power to direct BISL to do so, I’m delighted to see that these adjustments have been made to better serve the needs of non-binary consumers. Going forward, other non-binary consumers will benefit from this update, and from Mx Stray’s having drawn this matter to attention.

I have a few Pis running a raspberryPi OS (Trixie) derivative for 3d printers. They accumulate collections of large (10-1000Mb) text (gcode) files that respond very well to compression (about 3:1 in a zfs dataset on my server).

I know compression speeds up read and write performance on slow drives by reducing the amount written, and it's worked wonders with mechanical hard drives.

But there's a write amplification of copy on write file systems that makes them maybe not so good for SD card based systems, but I'm not sure if this would be mitigated by running compression?

I'm wondering whether it's better to run the entire SD card as btrfs with compression on every subvolume, or to make a separate partition on the SD card with compressed btrfs to deal with the large files and leave the root fs as ext4.

Obviously the *right* answer is to run a thin client pc with an SSD, or a pi5 with an SSD hat. I can do that to some extent but a used HP T530 or T620 costs more than a new pi 4.

I'd like to replace my Ring bell with something that integrates better into HA. This might be a step towards getting rid of echo dots that mostly serve as doorbells.

My Ring bell has knock detection, this is great because so many people won't push the bell and then wonder why I can't hear them. Replicating that or reproducing with a separate unit would be amazing.

I'm mostly interested in intercom functionality, I don't need the doorbell to video everything that comes close, my ring is set up only to record if someone presses the bell or knocks on the door.

I generally don't have the HA app working when i'm out of the house as the vpn to do that fights with my car, the bell having it's own app as well as HA is probably useful.

Replaceable batteries would be nice.

Anyone have sensible suggestions?

I've done a stupid or three. Trying to get some docker compose files converted to quadlets and running with systemd. I've got podlet working and i have a few things working, although they're running as system services and i'd need to figure out how to do them as rootless...

Bigger problem is I have spoolman up using sudo podman compose up -d compose.yaml is

services:
  spoolman:
    image: ghcr.io/donkie/spoolman:latest # Also available at dockerhub: donkieyo/spoolman:latest
    restart: unless-stopped
    volumes:
      # Mount the host machine's ./data directory into the container's /home/app/.local/share/spoolman directory
      - type: bind
        source: /home/strayr/compose_bullshit/spoolman/data
        target: /home/app/.local/share/spoolman # Do NOT modify this line
    ports:
      # Map the host machine's port 7912 to the container's port 8000
      - "7912:8000"
    environment:
      - TZ=Europe/London # Optional, defaults to UTC

all i've done is replace the provided relative source with an absolute path, but I've got nothing appearing in that folder. I've a DB being written to somewhere that is persistent, sudo podman compose down and a `sudo podman up -d" has the data I had in there previously. But where? because it's not happening where specified.

How do I find where the data is, and move it somewhere specified?

How do I fix this up to run rootless? Is there a handy guide? I don't need an ELI5 as much as an EL containers weren't a thing last time I really knew what I was doing here

https://preview.redd.it/wcspmisafvfh1.png?width=1930&format=png&auto=webp&s=8e2a440c3b8b885c4f6953ab4f01efb63850350b

I have Klipper Expanders and V0 Displays. Some of them are in awkward places so adding a jumper and pressing a button is much more of a pain in the ass than it seems.

I figured out how to set my pico based boards into (i think i have the wrong word as they become a flash drive but) DFU mode using

cd ~/klipper/scripts
~/klippy-env/bin/python -c 'import flash_usb as u; u.enter_bootloader("/dev/serial/by-id/usb-Klipper_rp2040_xxxxxxxxxxxxxxxxx)'

which is really handy, and I'm using katapult on my canbus devices so I was hoping I could use katapult's USB functionality to make flashing stm042 boards easier, but after flashing and resetting as shown in the image, I get no response from the board and have to jumper them back into dfu mode to put klipper on them. I have a fresh build of klipper using the same clock and interface settings that installs and runs, so i don't think I've made a mistake there.

Do i have any chance of getting this to work, or is there another tool that will do this?

I made this and have been successfully using it for many months now. I've lost track just how long.

It works really well with thick beds, fans beneath the bed to heat the chamber or curtain fans that blow over the bed for rapid cooling of PLA.

It's a braindead way of doing kalico's dual loop pid with klipper macros.

I'm retired and out of date, I know raid from the days of battery backed ram in hardware controllers and stacks of 9.1gb scsi drives going cronch cronch cronch...

I have 4 2TiB magnetic disks from an obsolete WD mycloud EX4 in a raidz1 pool. It's already decently improved but I'm wondering if I can bolt more bits of scavenged tech together without trashing stuff.

I can run one extra drive that isn't my zpool, it's my boot/system drive and is currently a dirt cheap sata BX500 of a pcie sata controller but I think i can drop in an pcie nvme controller instead.

I'm considering putting a ZIL and L2 ARC onto a chunk of whatever domestic SSD i end up using for a bit of a performance boost, but I'm kind of aware i might need to think about wear levelling particularly for the ZIL partition

• is there a locality effect of partitions on 'modern' ssds or is this completely abstracted away?

• Do i need to leave un-partitioned space for wear levelling to work properly or just not fill every last mb of every partition?

• Is this still a performance boost doing this with ZFS in 2026 or am I overcomplicating this? My main storage disks aren't fast.

Petition to make this the Three Word Slogan of the campaign