I meant @b0rk@twitter, damnit.
@federicomena the signals I see are the most obvious like Liberapay and the such
But also the idea of collecting structured data about software projetcs.
So that we could collect some information about who is using what in order to do what
We could match that with who is working on what payed by whom and how
Things like Guix and the fsf directory could help with this
Maybe some more initiatives that i don' t know exist
I've been bad at doing this lately.
Hi! I have a Patreon, which I'm using along side of my Twitch channel and Liberapay, to build up support for myself.
I'm unfortunately incapable of keeping with a normal job, due to #CFS, but I'm looking at alternatives. One is to provide content online, mainly Twitch streaming right now.
If you want to make a contribution to me I appreciate any support!
Also, Gtk4 is going to be a big API/ABI break again. There is *fantastic* stuff in there, but we are in for another round of applications that get more and more stale with respect to the baseline platform.
What do we do?
Think of all the stuff that still uses gtk2.
Gtk2 is not unmaintained, but it's in life support mode, thanks to people who actually get paid to do it.
Apps that haven't (been able to) switch to gtk3, they are maintained by people who *don't* get paid to do it.
Meanwhile, end users absolutely depend on those apps. We don't have that many "big" applications in free software, and we don't have an infrastructure for people to pay for them.
This is fucked up.
periodic reminder that the dymaxion projection is h*ckin great
Backporting shit like %patch80 -p1
I was thinking about the Fibbonacci sequence this morning, like you do, and realized that (a) you can run it backwards (f(n+1) - f(n) = f(n - 1)) and (b) if you run it backwards past the start of the sequence, you wind up with the same sequence but with alternating signs: 8, 5, 3, 2, 1, 1, 0, 1, -1, 2, -3, 5, -8... I'm sure this isn't novel but I thought it was neat.
One of the many killer features of magit... I'm in a source file, and "M-x magit-blame" does the blame but leaves the cursor where it was. I don't have to look for the line I'm interested in among the "git blame" output.
Added a couple debugging printfs to something and gcc was like, "warning: printf args don't match blah blah". Yes, I fucked it up.
But it was a WARNING. It may as well say, "warning: your code will crash, or you are setting yourself up for pwnage".
C makes dangerously incorrect code way too easy.
What's the go-to procedure for mocking up GNOME interfaces these days? Asking for a friend....
Thanks to @alatiera we will soon have a Rust parser for SVG's stroke-dasharray property, to replace the shitty and incomplete C parser we have 👊
Made this chickpea salad for lunch - https://www.recipetineats.com/middle-eastern-spiced-chickpea-salad/ It is quite 💯
Added a DIY headphone stand to the underside of my desk
Hey everyone! I'm a Colombian journalist working with Radio Ambulante, a podcast that seeks to connect Latinamerica through non-fiction stories. I also teach a class called "Innovations in media" at a local university. I'm looking forward to learning from all of you :) #introductions
New blog post: Preserving Threading In Google Group or Mailman Mailing List Replies with Thunderbird: https://www.harihareswara.net/sumana/2018/01/26/0
Have you ever wanted to reply to an old mailing list post that wasn't in your inbox, *and* preserve threading?
GNOME co-founder. Amateur woodworker, cook, cyclist, cartographer, gardener.
Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!