I'm a nonbinary queer person from Germany. I do stuff with #3dprinting, #electronics, #woodworking and since recently #metalworking. Other interests of mine are feminism, queerness and inclusive communities.
I love reading about other people's lives and thoughts. But interacting with them consumes a lot of energy - often more than I have. So don't be surprised if I won't do it that much :)
masto meta, boost visibility question answered
Ok, with the help of @schokopflaster I managed to figure this out:
Boost visibilty is (only!) tied to the default toot privacy setting and has nothing to do with locking your account.
Now, why the poll Gargron posted asked if tying it to the account locking setting was fine (to which a clear majority said yes) instead of what actually was changed I don't know, but it certainly added confusion for me.
Still wish this was properly documented.
masto meta, boost visibility question
Does anybody know how the visibility of boosts works in practice?
I found this https://github.com/tootsuite/mastodon/pull/9851, which I read as it should be tied to the account privacy setting, aka when your account is locked boosts are automatically private. But that doesn't seem to be the case.
There was discussion of tying it to the default post privacy setting here https://mastodon.social/@Gargron/101749616287239685, but I have no idea if that got implemented?
Soldering a small batch of temperature/humidity sensor breakout boards.
Board tabbing done as per @esden's KiCad panelization tutorial, works perfect! https://diode.zone/videos/watch/28bc7434-2bc1-4448-9c38-89e1dcc79dc4
I hate software projects who at some point completely changed their APIs but in no way whatsoever care about the fact that 80% of the available documentation still references the old ones, without any hint that nothing you read there works anymore.
Last year I had to dig into beaglebones developer mailinglist to find out that what I was trying to do couldn't work anymore, today I found that information only after looking at the mbed source code. Grr.
Since @toni pointed out that these are probably automated CW's by a crossposter I'd like to add:
If you see such a post and would like to boost it - don't. You can answer to the toot, delete the mention and write your own CW for it referring "the toot above", that works quite well. Or write your own toot mentioning the twitter source. But please, don't just spread it further as is with the useless "Birdsite" CW. Thanks.
I see more and more posts with a CW that says only "Twitter Crosspost" or "Birdsite" etc lately.
And when expanding the toot it's most of the time "RT email@example.com: [Tweet about some horrible thing that absolutely needs a CW]"
Please don't do this.
A CW is a CONTENT warning. Posting stuff from twitter is ok, for me such a CW is needless. What needs to be CWed is the CONTENT you post, no matter the source. Substituting the latter with the former is dangerous for people who need CWs.
de trans rights, TSG Reform (+/~)
Die Antidiskriminierungsstelle des Bundes hat zum TSG-Reformentwurf Stellung genommen und relativ knapp alles nötige gesagt:
Behaltet doch einfach das aktuelle Verfahren nach PStG beim Standesamt bei, für inter und trans, ohne ärztl. Bescheinung, Selbsterklärung reicht.
Und dieser ganze Müll im Entwurf den die Cissen sich ausgedacht haben nur um weiter Gewalt ausüben zu können fiele einfach weg weil der dann komplett überflüssig ist.
de trans rights, TSG Reformentwurf (-)
Uff. Die Bundesregierung plant völlig überraschend das TSG zu reformieren und der Entwurf liest sich (neben paar kleinen Verbesserungen) heftig scheiße.