Sebastian Krzyszkowiak @dos@librem.one

@sos @q3k @Perroboc What analogy? I only quoted the petition verbatim, haven't made any analogies. It specifically asks for "no involvement" from the developer, so what liability are you talking about? It's not even applicable to "thing breaks" scenario at all. Did you want to reply to someone else?

@sos @q3k @Perroboc If I sell something that's understood to be a working product, then it's my friggin duty to not "remote disable" it "before providing reasonable means to continue functioning of [it] without the involvement from [me]". Anything else should be outright illegal, and that's not limited to video games. How is this wording even slightly controversial?

@sos @q3k @Perroboc Honestly, I'm reading your concerns and questions and I'm baffled. I just read the whole text of the petition in both PL and EN and I simply can't fathom how possibly could you come up with such malicious interpretation of it? Have you skimmed it too fast perhaps?

The petition is quite reasonably worded and I'm fairly certain that what's proposed is not going to negatively affect me as a game developer in any way, so I just signed it and encourage everyone else to do so too.

@rysiek @szbalint > Question is, which.

A different set for each user 😜

@whitequark I actually quite liked PD 2.0 when I read it, at least when ignoring the deprecated Type-A/B stuff. Felt more approachable than regular Type-C state machine.

PD 3.0, however, made me weep.

@mazzoo Depends on your definition of "widely". It is somewhat common, with many implementations available - though often under the name AppleMIDI.

@mazzoo Are you aware of RTP-MIDI?

@kornel Pity it doesn't seem to exist - though it looks like the trailer has managed to go somewhat viral, so in the end its development may actually start one day ;)

@aanee What I'd recommend is to get an already working device and to find a component with available datasheet and missing functionality in its kernel driver. There should be plenty of such bite-sized low hanging fruits out there, which will let you gain enough experience to work on and debug more complex stuff with devices that aren't ported yet.

I don't know how a "porting for dummies" guide could even look like, this kind of stuff tends to be highly device-specific.

@filiplachert @jon It's clearly an attempt to make the lives of people who messed with them harder. There's not much more to it.

@mntmn In fact, there should be no need to copy anything; seems like all you'd need is exposed in libphosh, so you may be able to do it with just a few lines of glue code.

@mntmn I guess you could cut PhoshBackground out of phosh and end up with just that.

"The Art and Secrets of #Karambola" - a digital 92-page #artbook heavily illustrated with yet unpublished sketches, drawings, paintings and locations from the game - is now out!

Agata (@holypangolin) reveals her thoughts on the curious fruity characters’ personalities and backstories, as well as some difficult decisions she had to make during the design process.

Buy on #Steam or @itchio:

https://store.steampowered.com/app/3172920/The_Art_and_Secrets_of_Karambola/

https://holypangolin.itch.io/the-art-and-secrets-of-karambola

#gamedev #indiedev #art #mastoart #indiegame #itchio

@whitequark @hailey ah gotcha

@whitequark @hailey I had been there many years ago, confused about why shouldn't I keep debian/ dir upstream even though I was the one packaging my own thing in Debian. Only after getting more familiar with how things work I realized it makes perfect sense given the Debian's processes. I don't think it's fair to characterize it as "hostile".

It may still be valuable to maintain debian/ upstream though, but distinct from the distro packaging (usually for CI or for self-compiled dev builds).