Fabio Manganiello

Fabio Manganiello's avatar
Fabio Manganiello
fabio_at_manganiello.eu@momostr.pink
npub1xw9y...75ln
:platypush: #Automation addict @ #Platypush 🤖 #AI builder (when ethical, local and used in moderation) 🔓 Compulsive #FOSS contributor :arch: Prone to unsolicited "btw I use #Arch" statements 🏡 #SelfHost all #tech! 🔬 Open #science and open #data advocate 🎶 #Music geek 🎸 #Guitarist 🛹️ #Skater 🏄 #Surfer 🚲 Brains travel on #bike 👪 #Dad of a small geek ⭐ (Allegedly) pragmatic #socialist 🔎 #searchable 🇺🇦 🇵🇸 🇸🇩 Liberate all the oppressed 🇮🇹 ⇒ 🇳🇱 🏠 Home: https://fabiomanganiello.com 🛠️ Forgejo: https://git.platypush.tech/blacklight 🛠️ Github: https://github.com/blacklight ⚙️ Platypush: https://platypush.tech 🔐 PGP: https://keyoxide.org/D90FBA7F76362774 🇵🇸 Gaza Archive: https://gaza.onl 📝 Blog: https://manganiello.blog 🎧 Music: https://manganiello.music 🗨️ Matrix: [@fabio:manganiello.tech](https://matrix.to/#/@fabio:manganiello.tech ) 🗨️ XMPP: [fabio@manganiello.tech](xmpp://fabio@man
Digital sovereignty isn't an abstract concept to repeat for the purposes of political propaganda. Digital sovereignty is a real goal that must be achieved through concrete steps. You can't talk of digital sovereignty and independence from the rogue US tech sector while you literally sell the platform responsible for the online identification of your citizens to an American platform, without even evaluating the feasibility of turning a success story like #DigID into a pan-European project which lies exclusively in European hands.
Cancel Machado's Nobel Prize now. And give it to those who actually fought (and are still fighting) for peace in Gaza, Ukraine and Sudan. And to those who actually hate fascists instead of cozying up to them. Someone who likes so much to lick the filthy ass of a convicted felon bent on military threats against the whole world (and even his own people) doesn't even deserve a prize printed on toilet paper. Machado will be forever be a shameful stain in the history of the Nobel Prize.
After 2.5 years a feature on top of my wishlist is finally coming to #ntfy 🎉 ntfy will soon provide the ability to update and delete notifications. This solves many use-cases that so far forced me to piggyback on non-open solutions like Tasker on Android, or implement my own Java intents: - Notifications with progress statuses (the same notification can soon be updated with the new state, rather than creating a new one) - Media notifications that change when the track or the playback state changes (but the impementation of Android media notifications is still missing from ntfy, I'll probably take a look into it at some point) - Notifications that can be automatically dismissed when they no longer apply The discussion has been very productive and has gone a long way since my initial proposal. The proposed implementation exposes updateable notifications as sequence IDs on a given topic: ``` # Create a notification with sequence number 1 on $topic curl -d "created" https://ntfy.sh/$topic/1 # Update the previously created notification with a new value curl -d "updated" https://ntfy.sh/$topic/1 # Delete the notification curl -X DELETE https://ntfy.sh/$topic/1 ``` The custom `X-Sequence-ID` request header is also supported. If you want to test the new API (note that it may be still unstable and subject to change) you can compile ntfy from the `303-update-notifications` branch. If you would like to join the discussion, feel free to comment on the issue.
If you use an alternative #Tidal client, and playback suddenly broke today, don't worry - you're not the only one. Tidal today apparently pushed a change to their streaming backend that broke the MPEG-DASH specifications (namely, `AdaptiveSet@group` should only be a number, but they decided that they wanted to make it a string). Any alternative client that uses Python's `mpegdash` library is probably broken - and I guess that that's the case for many other ISO-compliant impementations too. I have pushed a fix for mopidy-tidal, and also one for python-tidal that makes sure that we won't swallow manifest errors next time. If you use mopidy-tidal, the advice is to use the latest version from git while we synchronize a new release. (Btw, I bash the Tidal devs, but of course it's not that I remember a 250 pages specs by heart. But when working on such old and widely implemented protocols, I'd at least make sure that I've got a big nice battery of tests to verify that my implementation doesn't break a standard `mpegdash` implementation).
My periodic reminder to blogs and news outlets that, if you have #RSS or Atom feeds, you should remember to exclude those URLs from your frontend-based verifications. If you want to control traffic on machine-to-machine endpoints, use standard throttling and rate limiting - not CAPTCHAs nor other frontend challenges. My Miniflux list needs to be periodically pruned from dead links because, as websites increasingly add Anubis, hCAPTCHA etc. to their pages, they often forget that they also have some RSS paths to maintain - and that aggregators break if you return some random HTML to them.
A quick communication to our wonderful friends in #Gaza. A few of you may have experienced limitations/suspensions on your accounts, especially on the main instance. First of all, I want to reiterate that this isn’t anything personal against you or a sign that `@staff` is not sympathetic with the #GazaVerified initiative - they’ve shown quite the opposite so far. Actions against accounts are only taken when several reports (usually for spam) are received and the moderation team is left with no choice. However, these restrictions are usually lifted when we talk to instance admins and explain them the situation, and those of you who are impacted pledge to use mentions more responsibly. Mastodon is still a platform that welcomes you, and we’ll make sure that this will keep being the case. Second, a common message I’ve heard in your appeals is “but we only tagged our friends and people sympathetic with our cause“. After so many reports, I started finding it increasingly unlikely that any of us would ever report you for spam - and repeatedly. So I’ve taken a closer look at some of the lists of users that some of you commonly tag and I’ve started to notice some patterns that may explain the reports (or at least some of them). Unlike centralized platforms like X or Instagram (or even Bluesky, where most of the people are on the main server), instances matter here. So my username (`@Fabio Manganiello`) is different from `@fabio`, or any `@fabio@something.com`. Those are different people with accounts on different servers. I’m bringing mine as an example, but I have noticed several occurrences where some of you probably tagged people by typing `@username`, saw a couple of options in the dropdown, and unsure on who is the right one you included a few of them. When you send that message, those people will get a notification - and they may not be me nor any of your friends. If someone keeps getting notifications from strangers to donate to an initiative they’ve never heard of, and without any way to tell if you’re genuine or not, after a few times they may simply report you for spam. And that explains limitations and suspensions. So please, when you send messages that include many mentions, always make sure that the handles you have included match those on our profiles. That may prevent a lot of unsolicited notifications to people who may not be very sensitive with your calls for help. Finally, we do our best to boost your voices, and we’ll keep doing so. But we also want you to have your own voice heard on a social media platform that is actually open to listen to you, with no need for our boosts. If you build your own following then you won’t need a few of us to boost your posts - people will follow you because of what you say or show to them. I built the @gaza_verified_accounts bot exactly to boost your voices, so anyone who follows that bot sees all of your posts, even if they don’t follow each of you individually. If you post your genuine stories that actually move people, then that bot is likely to be followed by many - and your own voices heard by many. One last thing, you don't have to tag @gaza_verified_accounts@mastodon.social or @gaza_verified_campaigns@mastodon.social explicitly. Those are automated accounts and I never check their notifications. It isn’t easy for me to deliver these messages by the way. I can only imagine in a remote corner of my mind how tough things must be for you. I can only imagine how I would behave on the Internet if it was my own life to be in peril, and if I had to fight for basic necessities on a daily basis. I feel like I shouldn’t be here preaching technical details about social media or netiquette to people literally going through hell. But I’m here to make sure that your voices are heard, that they touch as many people as possible, and that they keep being heard. Stay strong, we’re on your side ♥️ @Aral Balkan @npub1d6t8...vdlg