The 2026 DSF Board elections are running right now — if you’re a DSF member, please check your inbox for a ballot. I’m prioritizing four things on my ballot:
1. Fundraising experience 2. Community management experience, particularly with the DSF (working groups, etc.) 3. A clear vision and specific goals for the DSF 4. Global and industry diversity
I started going to IETF meetings. Those events take place 3 times a year, with ~1000 people attending in person and another ~1000 remotely. A good chunk of those are paid to be there and some are employed by big companies like Apple and Google. This is the place where the fundamental fabric of the internet is constantly being improved. TLS 1.3, HTTP/3, MLS to name a few.
With this in mind I have no fucking clue what Moxie was on about when he said interoperable protocols are stuck in the 1990s.
#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
Just to add to the discussion, it would be great to see any counter-arguments for blog.cloudflare.com/even-faste…, if anyone has the time to contribute
One of the more interesting features introduced by TLS 1.3, the latest revision of the TLS protocol, was the so called “zero roundtrip time connection resumption”, a mode of operation that allows a client to start sending application data, such as HT…
@giacomo @lorenzo IETF protocol specs regularly include sections with privacy considerations just like security considerations. These point out such problems and guide implementers to get them right (eg. to only use 0RTT if user tracking is of no concern because cookies would be on anyway). If a browser implements that wrong, it's for other lacks but awareness.
@giacomo @lorenzo I did not review that particular spec, but for those I do, I'd raise hell before publication as #IETF if such problems were unaddressed, and know many other reviewers who would do the same.
Well @chrysn@chaos.social, I really appreciate your good intentions and will to fight for users' #privacy. But I was not talking about you or the few independent developers who still volunteer at #IETF these days. I was talking about IETF effects on the Internet standards as a whole. I'm afraid the impact of a few independent engineers is not going to balance the power of organized and well funded #BigTech lobbyists.
As an example, let's stay on topic and look at RFC 9001, "Using #TLS to Secure #QUIC". All that is said about the impoved ability of the server to identify (and thus track) the user are in two lines about session resumption (emphasys mine):
Session resumption allows servers to link activity on the original connection with the resumed connection, which might be a privacy issue for clients. Clients can choose not to enable resumption to avoid creating this correlation.
Now please notice the #hypocrisy: the wording is set up as if clients should opt-in, but it's pretty unlikely that users will be given a choice between a personal data leak at protocol level and an imperceptible increase in connection time, in particular with 0-RTT where " Endpoints cannot selectively disregard information that might alter the sending or processing of 0-RTT".
So while I'm pretty curious about @bagder@mastodon.social's perspective, I see that #Google managed to get a protocol designed to thwart user privacy and reduce its own server costs (even just the energy consumed during TLS hadshakes, amount to thousands dollars each day).
This way, if EU would decide to forbid tracking cookies at all, Google would get a competitive advantage over all other #AdsTech companies.
Now a properly working IETF would have rejected such shit, knowing that it would have been leveraged against people (and democracies) though #Chrome browsers and #Android defaults.
> Now a properly working IETF would have rejected such shit
I think this shows that you don't really understand how IETF works and the how its specifications are made. Please keep me out of further comments in this thread.
@archos 🤷♀️ já za to vážně nemůžu .... jsem dostala kapra od kolegy ..... a i když jsem dnes chtěla tu Svatomartinskou husu koupit ... tak se to prostě nějak samo zvrtlo 😂 🤦♀️ 😋
Appears my Sonos stopped playing in the middle of the night (sleep sounds) because I had automatic updates off and it was behind on updates. As soon as I did updates this morning it worked again
rpi3. There is ESP32 (re)implementation but it's janky and more DIY than usual, especially since it'll need audio board. I also use old smartphone as a driver too but it's annoying that it lowers volume to "preserve my ear health"
i use MPD to stream to snapcast, another MPD instance JUST for homeassistant tts, also to snapcast and finally i have ROC stream from my desktop to snapcast in case i want to listen to youtube in bedroom or something.
I'm currently looking into way to play off jellyfin as if it were mpd, but so far no dice. It can stream to DLNA Renderer (gmediarenderer) but it's jank and doesn't work with scrobbling
mpd to snapcast sorta requires them being on same machine - it will be using a unix pipe (mkfifo), otherwise ROC is way more reliable and stable way of point-to-point transferring audio over LAN
@hj oooh shit man, I just got this working. Still running Bookworm on my Raspberry Pi so I didn't have a roc-toolkit package available, but I followed their docs to build and install it.
And then the problem was FreeBSD not having it packaged. So I went down that rabbithole, gave the devs some updates on their Github (packaged a missing library, fixed their build on FreeBSD) and whoaaaaaaa this works GREAT
I'm getting high quality low latency PCM stream over the network sucking the data directly from ALSA and playing out OSS directly on FreeBSD (Pulseaudio works too, but why bother)
and now I have my high quality audio again to keep me entertained while I'm working. The ffmpeg to Icecast solution I came up with worked, but it fucking sucked to be honest with like 5 seconds of latency
The build system has support for non-linux/non-macos *nix targets, but we didn't test it, besides Debian/Hurd. We're looking for someone who have FreeBSD installed and could run build and test, and...
@hj I was sharing this progress and someone said "what about that openbsd sndiod, you can stream audio with that" so I started looking into it (it's inferior to roc-toolkit) and sure enough I see a mailing list post by @lanodan :)
Enjoyed this Techcrunch piece about the new show Pluribus from the creator of Breaking Bad. Fun fact, the star of the new show Rhea Seehorn and I used to study for a statistics class together at GMU. I had such a secret crush back then (okay maybe still a little).
"If you watched all the way to the end of the new Apple TV show “Pluribus,” you may have noticed an unusual disclaimer in the credits: “This show was made by humans.”
"That terse message — placed right below a note that “animal wranglers were on set to ensure animal safety” — could potentially provide a model for other filmmakers seeking to highlight that their work was made without the use of generative AI."
"And just in case the disclaimer wasn’t clear enough, creator Vince Gilligan (best known for “Breaking Bad”) was even more emphatic in a Variety feature story about the show, declaring flatly, “I hate AI.”
"He went on to describe the technology as “the world’s most expensive and energy-intensive plagiarism machine” and compared AI-generated content to “a cow chewing its cud — an endlessly regurgitated loop of nonsense.”
Going by various posts that I've seen lately, I'm just feeling glad that I don't use JAWS. I don't use Windows at all for the day job. I do have it on my personal laptop, but I don't use it enough to justify paying for JAWS, and I'd rather give my money to the NVDA devs. And it reminds me of one of the reasons I got into FOSS in the first place. That being said, I get that a lot of people rely on JAWS scripts to get their work done or are just accustomed to it, so encouraging someone to just switch to something else isn't always a great option.
@startrek2025 That makes sense, and I think that that's typical. I use Orca on Linux when I'm not in the console, and sometimes switch to NVDA if I'm having trouble with a web site, and also have Voiceover on my phone, so I feel like I have enough screen readers without it.
A person begs on the street. I give them some money.
K1: why did you do that?
Me: because they need it
K1: [friend]'s mother says these people aren't poor, they have a lot of money
Me: if you had a lot of money, would you beg in the wet and cold?
K1: no... *thinks* ...but what if though?
Me: you're right, we can't know it. But giving the money doesn't hurt me. And if I gave nothing and that person went hungry, it would be far worse than giving too much
"Der verbreitete Gedanke, dass Kollektiveigentum zum Scheitern verurteilt ist, hat sich fest in den Köpfen der Menschen verankert. Aber stimmt das überhaupt?"
Up to now I haven't really understood why weddings are notoriously so stressful.
But today I spoke to a colleague who's getting married next autumn and she has been to her venue recently to measure the length of the aisle so she can work out precisely how many steps she needs to take to end up on the correct foot when she reaches the front so she can turn the right way.
That's how. That's how one gets stressed about a wedding. #MatrimonyMusings
People in the future are going to be super confused by Windows versions.
"So there was Windows, right?"
"Well, mostly Windows 3.1."
"Which was the third version?"
"No."
"So then Windows 4 must have come after that."
"No, they jumped to version 95."
"So then Windows 96..."
"No, then they skipped to 98."
"Oh, but it was for the year it came out, right?"
"Kinda."
"But surely after that..."
"Well, after that they actually moved away from version numbers and gave them names."
"Oh, like MacOS!"
"Sort of..."
"What do you mean?"
"Well, the first version was XP."
"What does that stand for?"
"No idea."
"Did they just use letters after that?"
"No, then they named the next version Vista."
"Like... the stuff you see out of a window! Ok, so the version after that was Windows Outlook, right?"
"No, the version after that was Windows 7."
"7?!"
"Yeah."
"But... It wasn't the seventh version of Windows even."
"Yeah, but the version after 7 was 8."
"Okay, back on track!"
"Not really. The next version was 10."
"Because it came out in 2010?"
"No."
"Fuck."
"Then came Windows 11, and they stopped releasing new versions for a while and just added LLM panopticon nonsense until everyone switched to Linux in the 2030s and then when the second coming of Jesus fried everyone's hard drives..."
"Yeah, yeah, I know, Windows II: The Empire Strikes Back..."
Ich möchte nicht still bleiben, wenn beim #Bürgergeld Stimmung gemacht wird. Es geht um die #Demokratie. Linnemann war es, der behauptet hat, „Hunderttausende“ wollten gar nicht arbeiten. Niemand kennt diese Zahl. Wer solche Zahlen erfindet, betreibt verantwortungslosen Populismus. Die Folgen sind fatal: Aus Empathie wird Verachtung Aus Miteinander wird Gegeneinander Und Solidarität wird brüchig. Langzeitarbeitslose Menschen brauchen Chancen, Respekt und Perspektiven statt Misstrauen und Druck.
Dear #IzzyOnDroid community, we need your help for keeping our repo as useful as possible. No tech knowledge needed for this one, so anybody who's got an #Android device and some spare time can jump in here:
Are you using any of those apps, or would be willing to install one (or more) of them to see if they are still useful? Please then report there, or here to this #serviceToot – so we can get that issue solved 🙏
This is a spin-off from #10 where I'd like some input from the team, concerning how to handle the following unmaintained apps:
* [x] [`com.projects.musicplayer`](https://apt.izzysoft.de/packages/com.projects.
would, theoretically, in a way – if it existed. That thread was opened 5 years ago, has been last updated 1 year ago – and the functionality never became reality. It's quite hard to do that properly without requiring accounts – which neither F-Droid nor we want (accounts). I doubt it will become reality any time soon, so it doesn't really help us _now_ – while reports here and in the issue can 😉
@daniel Thanks a lot! At least we know now the app is still working as described, and even on Android 16. I personally also use ScrCpy, as you mention 😉
Updated the initial post, linking to your review. We'll probably keep this app then.
Beat Addiction: Didn't work without unrestricted background access. The stats were impossibly wrong. When given full background & notifications access didn't work either. Totally abandoned. I'd remove it.
VideoCrop: Doesn't offer the crop controls with small video. Fails completely with bigger video. I don't see a use for it, maybe let anyone else try it.
PhotoPlay: Works. It's a frontend for Imdb or similar (actually for themoviedb.org) where you can make local lists.
The app description can be misleading though: "All of your data stays on your phone forever; nothing is sent to a server" my ass. Lots of calls to api.themoviedb.org and image.tmdb.org
The app can stay but its description should be more accurate.
@jandi Thanks once more, Jandi! As the repo seems to be unmaintained (hence the issue on our end), and there's no Fastlane set up upstream that could override it, we can of course update the description at our end. Of course it needs to contact the server it gets the data from, but "nothing is sent to a server" indeed isn't accurate (the queries are, but that's to be expected).
Adjusted it to "apart from the queries for movie data, nothing is sent to a server". That OK, or miss something else?
I'd specify the server. More info is better. Someone that wants to use this app may have opinions about the service (TMDB in this case) and decide accordingly. I have not seen spurious connections in my (light) usage so that's fine.
@jandi Hm, seeing the ToS at themoviedb.org/api-terms-of-us… – wouldn't that qualify as NonFreeNet? If so, we could raise that anti-feature and put that explanation there. Yupp, confirmed: other apps using TMDb are flagged such. Done then, thanks for digging in!
(note the anti-feature may show up with delay, as the indexer was already running here when I added it; but it should show up latest next day.)
#Linux und #Barrierefreiheit, insbesondere für Menschen mit Einschränkungen beim Sehen: habt ihr da Tipps?
Ich weiß, dass es bei @kde die Bildschirmlupe gibt und ich in den Bildschirm zoomen kann. Aber bei anderen Umgebungen? Und für den Zeitraum, bis KDE hochgefahren ist?
Eine Boot-Textkonsole mit 80×25 Zeichen halte ich für gut lesbar. Allerdings zeigt zumindest meine Kiste beim Bootvorgang eine recht kleine Schrift, bei der ich meine Brille brauche.
This is hard to read, because this is 1933 all over again. It is no longer a question if the US are sliding into fascism or have already arrived. They went full Nazi.
Bundesminister für Digitales in seiner Rede: »Zum ersten Mal übertreffen Maschinen den Menschen in dem, was uns bisher einzigartig machte: unsere Intelligenz.«
Auweia. Taschenrechner »übertreffen« mich auch – trotzdem sind sie keine Mathematiker. KI ist Statistik: Vorhersagen, imitieren, plausibel klingen. Verstehen? Null. Bewusstsein? Null. Verantwortung? Null. Wer hier von »Intelligenz« spricht, zeigt vor allem, wie wenig er davon versteht.
Rede von Dr. Karsten Wildberger Bundesminister für Digitales und Staatsmodernisierung bei der Pressekonferenz Industrial AI Cloud - strengthening Europe’s digital sovereignty
Part 2 of 2. The release note state the following: VT Recorder now supports manual fade control of a playing music bed. This may be useful for fading up a music bed temporarily while not speaking during a recording. A button for Fade Up or Fade Down appears beside the music bed Play/Stop button. A music bed may now be started at full volume rather than faded by unchecking the new checkbox entitled "Start Faded in", found in the Options. You can always get to the Options of course by typing letter C from within the VT Recorder. The shortcut key for the fade button is letter D.
There is a further note to this. Assuming a music bed is selected, it should be possible to: Press Enter to start the outgoing track. Press Enter again to begin recording. Press Enter again to start the music bed. Press Enter again to start the incoming track and cut the music bed. Press Enter again to terminate recording. That is the procedure. However, if the outgoing track has not finished, pressing Enter does not start the music bed. It does only start the bed if the outgoing track has completely concluded. I do not use this feature because I have other ways of playing music beds into VT's, but it struck me in my testing that this was plain wrong. You may wish to start your VT 30 or 45 seconds before the outgoing song ends, then start the music bed which should cut off the existing song. I can think of many situations where that could arise. This is still the case up to and including the final release of 6.2.
Part 1 of 2. StationPlaylist 6.2 Suite is available!
Notable Changes in SPL 6.2.
The below notes were prepared during many hours of testing the entire SPL 6.2 product range. They represent my thoughts only.
The most important question: If you are not managing a station, and you are just hosting a straightforward live show, should you upgrade to 6.2? If you do want to update, think carefully. Christmas is coming up and you want everything to be perfect for that. If you are going to update, due to the many script changes, you will want to set aside some considerable time to ensure that everything is as you want it to be. In addition, due to the health issues I have had this year I am taking an extended Christmas holiday so assistance from me will be slower during parts of December and January.
With that said, let's get to the notes.
Crossfading.
You will note that the crossfade transitions between songs and spots is significantly improved as a result of internal changes in 6.2. If you regularly scan files via the Track Tool as I do, such as pre-recorded show segments or news and weather bulletins, it is still advisable to do this. But generally speaking you will find improvement overall.
Voice-tracking locally or remotely.
Voice-Tracking can now record using .Flac format. This is very helpful for those of us who had previously recorded all VT's using Wav format. .Flac provides high quality audio without taking up as much space.
Accessibility.
I recently reviewed a competitive product for accessibility. While doing so, I realised how thankful I am that not only are all the options in SPL accessible, but StationPlaylist offers a far greater range of keyboard shortcuts. The developer is also willing to work with me to a large extent to improve issues, and there have been a number of those this time.
The most noticeable change relates to Studio and the fact that the column layout has been completely changed from all other versions I can remember. This has meant that many scripts have needed to be altered in some way and has taken a great deal of time and testing. I cannot even quantify how many hours the changes have taken to refine what we had before. I have tried to ensure that all functionality is the same as it used to be, but I could well have missed something. Improvements will be made over time. This is further complicated by the fact that the new SPL Remote application, referred to below, displays the column layout as it would have been in V6.11 so I have needed to make accommodations for that.
The Release Notes also state that there is a change to the newly renamed Time column. If a playlist is loaded, and you have not played any tracks, this column shows the scheduled times tracks will play out according to the time of the playlist. However, when you begin playing any track, the column changes to display tracks relative to the current system clock. This can be a serious disadvantage if you are voice-tracking a show since you do not get a true picture of how the hour is meant to look when it is broadcast. For example, if you have a track scheduled for 10:03 AM, and you play the track at 18:37, the entire view of the playlist changes to reflect the system clock. The scripts emulate the old behaviour so you are not disturbed by this misrepresentation. So as usual, SPL key then S will report the true scheduled time as if the tracks had never been played out, and SPL key then W will report the real time.
SPL Remote.
This is the new product which can be purchased from SPL. It allows you to remote onto an automation machine, or a computer back at the station, and carry out a live broadcast. You should have full access to SPL Remote. As far as possible, when you log onto a machine using SPL Remote, the experience should be very similar to that which you would receive if you were using Studio standalone. Many of the functions should work, such as to hear the remaining time of a track, elapsed time, and so on.
There is an advantage in using SPL Remote that people may not have latched onto. 1. Remote onto the station machine. 2. If JAWS is not installed on the station machine, it does not matter. You will still have access to all the functionality offered by SPL Remote, using your existing JAWS settings, even though JAWS is not installed. So you will be able to examine the playlist structure, check the remaining time, and so on, even though JAWS is not running on the automation machine.
Remote VT Changes.
Within the playlist viewer, the default presentation of information is to hear the scheduled time first, then the track details. However, some people prefer to hear the track or spot information first. To easily accomplish this, press the SPL key then X. Pressing this keystroke repeatedly will change the arrangement.
Issa
in reply to Daniel Gultsch • • •who is moxie? moxie marlinspike ?
also, any agenda for crypotgraphy sujbects?
Giacomo Tesio
in reply to Daniel Gultsch • • •#QUIC (and #HTTP3) exists to serve the interests and needs of #Google.
In particular 0-RTT is basically a low-level cookie that allows deterministic user tracking below and before #http: if it will ever spread, disabling or deleting cookies, even out-lawing them, won't be a issue for #SurveillanceCapitalism.
So these days what happens at #IETF is much more lobbying than engineering. Overpaid engineers lobby against the users to further cement the power of their corporations.
I wouldn't call these as "improvements".
These days, sadly, IETF is the place where the fundamental fabric of the internet is constantly being ^^enshittified**.
@lorenzo@snac.bobadin.icu
Electrostep
in reply to Giacomo Tesio • • •@giacomo @lorenzo
@bagder , you've written a book on the subject. It's the above claim of about #QUIC (and #HTTP3) true?
daniel:// stenberg://
in reply to Electrostep • • •Electrostep
in reply to daniel:// stenberg:// • • •@bagder @giacomo @lorenzo
Thank you for responding.
Just to add to the discussion, it would be great to see any counter-arguments for blog.cloudflare.com/even-faste…, if anyone has the time to contribute
Even faster connection establishment with QUIC 0-RTT resumption
The Cloudflare Blogchrysn
in reply to Giacomo Tesio • • •chrysn
in reply to chrysn • • •Giacomo Tesio
in reply to chrysn • • •Well @chrysn@chaos.social, I really appreciate your good intentions and will to fight for users' #privacy.
But I was not talking about you or the few independent developers who still volunteer at #IETF these days.
I was talking about IETF effects on the Internet standards as a whole.
I'm afraid the impact of a few independent engineers is not going to balance the power of organized and well funded #BigTech lobbyists.
As an example, let's stay on topic and look at RFC 9001, "Using #TLS to Secure #QUIC".
All that is said about the impoved ability of the server to identify (and thus track) the user are in two lines about session resumption (emphasys mine):
Now please notice the #hypocrisy: the wording is set up as if clients should opt-in, but it's pretty unlikely that users will be given a choice between a personal data leak at protocol level and an imperceptible increase in connection time, in particular with 0-RTT where " Endpoints cannot selectively disregard information that might alter the sending or processing of 0-RTT".
So while I'm pretty curious about @bagder@mastodon.social's perspective, I see that #Google managed to get a protocol designed to thwart user privacy and reduce its own server costs (even just the energy consumed during TLS hadshakes, amount to thousands dollars each day).
This way, if EU would decide to forbid tracking cookies at all, Google would get a competitive advantage over all other #AdsTech companies.
Now a properly working IETF would have rejected such shit, knowing that it would have been leveraged against people (and democracies) though #Chrome browsers and #Android defaults.
CC: @daniel@gultsch.social @lorenzo@snac.bobadin.icu
RFC 9001: Using TLS to Secure QUIC
www.rfc-editor.orgdaniel:// stenberg://
2025-11-10 00:06:47
daniel:// stenberg://
in reply to Giacomo Tesio • • •@giacomo @chrysn @lorenzo
> Now a properly working IETF would have rejected such shit
I think this shows that you don't really understand how IETF works and the how its specifications are made. Please keep me out of further comments in this thread.
Andrew Gallagher
in reply to Daniel Gultsch • • •