About those billionaires "paying taxes"…

https://www.theguardian.com/news/ng-interactive/2026/oct/16/billionaires-fight-california-prop-40

> 2026
> sargon makes a video about gamergate

this is like boomers never getting over star wars

@akana see my previous posts - it _is_ broke. in a very limited way in that it's shifting oddly from 5 to 4 and 4 to 3, but _not_ 3 to 2 (it's not a limiter issue) or 2 to 1, or at all in the _other_ direction.

this makes sense if the shifter control is worn or if something is not releasing right somewhere and given everything else I've done it like has to be somewhere north of the actual derailleur. particularly since when it _does_ shift, which just needs a little nudge and not always in the obvious direction, it's perfect.

(also I can make 5 to 4 and 4 to 3 work perfectly, but then in 2 it ticks against the 1 gear and the 3 ticks against the 2 year, indicating it's gone too _far_ in that adjustment direction.)

hey uh

sorry to burst your bubble nice shaman lady but

woman character can't get your girl pregnant

@clacke I secretly greet everyone with "hej", but I pretend I'm saying "hey".

@TerryHancock@m.filmfreedom.net

Looking at the project file in an editor, it looks like the hash is meant to be unique to the project.

So then the question is why has it used the same hash on multiple Kdenlive files? Surely every "save as" should change the ID..?

Also, if this can happened, why can't it just generate a new hash if there is a collision?

For that matter, why the opaque hash? Why not use something human readable, like the file name? Maybe with an appended number if there's a collision? This just seems like it's needlessly obfuscated.

So what if I just change the ID in the file? Can it be anything? Does it have to stick to decimal numbers? 🤔 Would be tempting to use something easier to identify.

To abandon facts is to abandon freedom. If nothing is true, then no one can criticize power, because there is no basis upon which to do so. If nothing is true, then all is spectacle. The biggest wallet pays for the most blinding lights. - On Tyranny, Timothy Snyder

#quoteoftheday

@midwan
Ok... But there are no binary releaeses and nothing on haikut depot?

@Ernesto310 Yes, that is on our roadmap!

RE: https://mstdn.party/@perdidonavida/117508457081302335

What a beautiful statement:

"For 3 weeks, we ceased all our internal struggles among the leftists and we acted as a single organism."

We can all learn from the Brazilians!

My fellow Americans: let's not fumble this.

@moira i mean, i say, if it aint broke dont fix it

so i greased the hell out of the rear shifter controller (which is right grip) and that shifting oddity has in fact improved.

the cable looks pretty much fine is there ever a reason to break it when there's _not_ anything obviously wrong? could it be doing some kind of weird stretching? it seems so unlikely.

#BikeRepair #BikeTooter

Niifebuvxial

@ghostdancer @tortuguito @ximo 😂😂😂

@herzenschein I may not have a blog post in me about it, but I can tell you what sources I used!

First off, I was writing this in Rust, so I used the wayland-client crate, which doesn't necessarily use libwayland at all, because it also has a pure-Rust implementation of the protocol available.

There's a convention in Rust projects of having an "examples" directory, and conveniently, wayland-client has a simple_window example, so I studied that pretty carefully.

That was tricky, though, because there have been some recent breaking API changes in the wayland-client crate, and it took me a little while to notice that the example I was reading was written against current git, not against the last release, which is what I was using.

Eventually I got it to display a window but after displaying the initial contents it wouldn't redraw, so I looked for a different example. At that point I found https://wayland-book.com, which I think might be exactly what you want since it is a tutorial using libwayland. (I hadn't realized I needed to tell the compositor that the whole window was damaged to get it to repaint anything; that was a one-line fix.)

The other source that I used a lot was the Wayland Explorer, https://wayland.app/protocols/, which just makes it easy to browse the documentation for the core protocol and many extensions. It also reports which compositors support which extensions, and that's super helpful.

I got from empty source file to working demo in a 12 hour period yesterday, counting breaks and all, and I made a number of choices that were probably harder than necessary so I could learn more. I did mostly know what I was looking for beforehand though, so whether you find it easier or harder than I did could go either way. I think especially the book and the explorer might help though!