IndieWeb post types

This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:

 Repost

Reposted JimmyB (he/him) (@JimmyB@mas.to)
Post details
@aral@mastodon.ar.al My little lad had a bad leukaemia when he was 20 months - in 2002. He had care at Great Ormond St - I calculated at the time (I’m an accountant) at somewhere between £250k and £500k, entirely free to us. And he lived. The US families sometimes didn’t fare so well. After they’d drained all insurance & resources their kids often died of something entirely treatable. Folks need to think very hard before voting for either #Tories or #Labour. @nhsactivistrn

 Like

Liked flere-imsaho (@mawhrin@circumstances.run)
Post details
there's the amusing line of thought regarding the “source-available” proprietary licenses, which maintains they're targeted against the abuse of the free software by the large saas companies. and of course it's bullshit. large saas companies are big enough to take over maintenance of the latest non-encumbered version, throw funds and people at it, and even provide the result to the public (cf. elastic search and opensearch). or, if they feel like it, they may just buy out the whole company with its product instead of paying licence fees – if they really need it and there's no other way to get the required expertise. the people who actually get shafted by the license changes and embrace of the proprietary model are the other open source projects that depend on the now-closed software, and small-to-mid-sized companies.

 Repost

Reposted Baldur Bjarnason (@baldur@toot.cafe)
Post details
I’ll let you in on a secret: I love sporadically updated weblogs. I subscribe to over 1200 feeds and most of them are sporadic or even technically “inactive”. Months often pass between updates It means that every post published was important to the writer Back in the days of snail mail, letters that began with “It’s been a while since I last wrote to you” were the ones people cherished the most You don’t need to post every day or even every week to have a blog that matters

 Like

Liked Matthew Miller (@mattdm@hachyderm.io)
Post details
In this latest, they say: "Redis has been sponsoring the bulk of development alongside a dynamic community of developers eager to contribute". I was just talking to @quaid about this, and he made an excellent point: if your company-sponsored open source project is still 95% company-developed, _you messed up several years ago_.

 Reply

Thank you for the shame-driven reminder 😅

I accidentally signed up for it over 4 years ago (and have been meaning to add the links) but as Jan mentions, I've still been part of the ring, but now I've finally gotten around to adding them!

 Like

Liked Josh Simmons (@josh@josh.tel)
Post details
I've been at the OSS Growing Pains workshop focused on governance these last couple of days, and I've never felt more confident that I'm in the right place. I'll be unpacking and riding on this experience for a while! Deeply grateful to @shauna@social.coop for the invite, and to have spent time with amazing humans like @HeatherLeson@fosstodon.org, @silona@fosstodon.org, and @ntnsndr@social.coop ✨

 Repost

Reposted Miah Johnson (@miah@hachyderm.io)
Post details
Remember folks. When VC is funding Corporation that releases a Open Source project its only a matter of time until they take it back. Their goal is to get their product embedded into your organization and abuse you for free work in the hopes they can eventually sell their corporation and cash out. Its always good for them, and rarely good for you.

 Reply

Ooh I've not seen that green one used with the orange one before does that make it even slower to get food out? 👀

 Reply

Got a link to the thread? May have missed it but sounds very interesting 👀

 Like

Liked rob pike (@robpike@hachyderm.io)
Post details
There's been a thread about dependencies lately and the challenge of convincing developers to look at the full dependency chain. I once maintained a C++ binary that included a PostScript interpreter, a JPEG decoder, a JavaScript interpreter, and a number of other utterly irrelevant pieces causing a huge factor increase in the size of the binary. The culprit: A single logging statement that invoked a general-purpose printer that could print web stuff. Switching to sprintf fixed it.