Fabio Manganiello

Fabio Manganiello's avatar
Fabio Manganiello
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.