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 Biped Earthling (@obeto@mas.to)
Post details
"Substack CEO Chris Best said he didn't want to "engage in speculation" about statements like “all brown people are animals."" Given another opportunity to answer correctly by the interviewer, “You know this is a very bad response to this question, right? You’re aware that you’ve blundered into this. You should just say no. And I’m wondering what’s keeping you from just saying no," He declined. So, fuck him. And fuck his site. I'll NEVER use Substack. #BlackMastodon https://gizmodo.com/substack-ceo-doesnt-know-if-should-ban-overt-racism-1850337647

 Like

Liked Alex Wilson-Davis (@probablyfine@tech.lgbt)
Post details
Some try to keep on top of their emails by aspiring to reach Inbox Zero. I try to keep on top of my code by aspiring to reach Branches Zero. If you're taking continuous integration seriously, you should have zero branches most of the time, and they should only exist (a) if you're not doing trunk-based development and (b) for as short a time as possible.

 Repost

Reposted Owen (spoopy aspect) (@owen@mastodon.transneptune.net)
Post details
If the Kubernetes material was honest about "your team will need recurrent annual training to remain current with this tool," adoption would crater overnight. That's not unique to Kubernetes, though it is fun to pick on them for it. _Nearly every_ significant infrastructure tool has this shape. Organizations that adopt these tools are unable to receive their value until their staff know how to use them, and that knowledge is deeply not self-sustaining.

 Repost

Reposted Marco Rogers (@polotek@social.polotek.net)
Post details
In my experience as a manager and leader, I spend a lot of time trying to get engineers to care more about business outcomes than technical issues. Not because I think the technical issues don't matter. But because I know if that if you're not trying to understand business outcomes, your judgment about the technical issues is going to be much worse. Many engineers fundamentally do not believe this to be true. And it's one of the things that sets them at odds with leadership.

 Like

Liked Cat Hicks (@grimalkina@mastodon.social)
Post details
wow 95% of LGBTQ+ adults registered to vote (according to this recent HRC survey sampling ~2400 in Aug 2024) I don't know their sampling methodology but that's pretty wild compared to any other voting registration stat I've seen. Similar to covid vaccine stats which are also wildly good for us. Makes me think about how folks only look to marginalized groups on the national stage to talk about disparity & trauma and not to learn from us as a dynamic, taking action, motivated success story.

 Repost

Reposted VM (Vicky) Brasseur (@vmbrasseur@social.vmbrasseur.com)
Post details
The UK helped usher in the coal era — now it’s closing its last remaining plant The Ratcliffe-on-Soar power station in Nottinghamshire is slated to close on September 30th, marking the end of coal power in the UK. It’s turning the page on an era of dirty energy that the UK helped usher in globally and now has to leave behind to meet climate goals. https://www.theverge.com/2024/9/23/24252195/last-coal-power-plant-close-climate-change-clean-energy

 Like

Liked Pelle Wessman (@voxpelli@mastodon.social)
Post details
What happens when the foundation behind a project isn't independent and empowered. The WordPress Foundation seems to not really be independent of Automattic or have any people working for it https://wordpressfoundation.org/about/financials/2023-financials/ Compare to @drupalassoc, @openjsf@social.lfx.dev and other more functional ones https://mstdn.social/@TechCrunch/113197135186493986

 Like

Liked unimplemented!("free the imagination") (@jalcine@todon.eu)
Post details
I left the Social Web working group because of the eagerness of allowing known endorsements of digital violence having a say in the development of it. And now it's also a big sponsor of the new Foundation. Since ethics, for most, tends to be a sort of T-shirt you can get a conference and not something that's a lived value, as with it all, I do not trust anything coming out of it and those places. https://www.jacky.wtf/essays/2024/pulling-from-fedi/ https://www.jacky.wtf/essays/2024/deinvest-open-web/

 Repost

Reposted unimplemented!("free the imagination") (@jalcine@todon.eu)
Post details
I left the Social Web working group because of the eagerness of allowing known endorsements of digital violence having a say in the development of it. And now it's also a big sponsor of the new Foundation. Since ethics, for most, tends to be a sort of T-shirt you can get a conference and not something that's a lived value, as with it all, I do not trust anything coming out of it and those places. https://www.jacky.wtf/essays/2024/pulling-from-fedi/ https://www.jacky.wtf/essays/2024/deinvest-open-web/

 Repost

Reposted @javi
Post details
<p>Ok, I should be sleeping right now, but what's happening is SO FUCKING CRAZY.</p><p>Long story short: WPEngine is suing Matt Mullenweg, Automattic and the WordPress foundation for slandering them. In return, Matt is suing them for trademark violation.</p><p>But, BUT, WPEngine has fired their first shot. And what a shot it is, friends:</p><img src="https://goblin.band/files/ccae0c7e-bcad-4df8-833e-198c82647f14" alt /><p></p><p><a target="_blank" href="https://wpengine.com/wp-content/uploads/2024/09/Cease-and-Desist-Letter-to-Automattic-and-Request-to-Preserve-Documents-Sent.pdf">Link to the full letter</a></p><p>Some extracts:</p><blockquote><p>Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers, and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X,YouTube, and even on the <a target="_blank" href="http://Wordpress.org">Wordpress.org</a> site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses</p></blockquote><p></p><blockquote><p>During calls on September 17th and 19th, for instance, Automattic CFO Mark Davies told a WP Engine board member that Automattic would “go to war” if WP Engine did not agree to pay its competitor Automattic a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis. Mr. Davies suggested the payment ostensibly would be for a “license” to use certain trademarks like WordPress, even though WP Engine needs no such license. WP Engine’s uses of those marks to describe its services – as all companies in this space do – are fair uses under settled trademark law and consistent with WordPress’ own guidelines. Automattic’s CFO insisted that WP Engine provide its response to this demand immediately and later, on the day of the keynote, followed up with an email reiterating a claimed need for WP Engine to concede to the demands “before Matt makes his WCUS keynote at 3:45 p.m. PDT today.”</p></blockquote><p></p><blockquote><p>In parallel and throughout September 19 and 20, Mr. Mullenweg embarked on a series of harassing text messages and calls to WP Engine’s board member and also its CEO, threatening that if WP Engine did not agree to pay up prior to the start of Mr. Mullenweg’s livestreamed keynote address at 3:45pm on September 20, he would go “nuclear” on WP Engine, including by smearing its name, disparaging its directors and corporate officers, and banning WP Engine from WordPress community events.</p></blockquote><p>They... they have text message captures. In the pdf. Matt Mullenweg was trying to extort them ... by text messages. They seem to have the entire thing in the writting.</p><p></p><blockquote><p>In the final minutes leading up to his keynote address, Mr. Mullenweg sent one last missive: a photo of the WordCamp audience waiting to hear his speech, with the message that he could shift gears and turn his talk into “just a Q&amp;A” if WP Engine agreed to pay up</p></blockquote><p>They finish requesting Automattic to "preserve, and not destroy, any and all documents or information in their possession, custody, or control that may be relevant to any dispute between WP Engine and Automattic". They are going to war, big time.</p><p>All this crap is just because they refuse to pay his protection money. And the guy has been stupid enough to put everything in writting.</p><p></p><p>Holy. Fucking. Shit.</p><p>HOLY FUCKING SHIT.</p><p>They are going to toast him alive</p> 📎

 Like

Liked Anders Eknert (@anderseknert@hachyderm.io)
Post details
@tomasaschan Thanks for both pointers! I'll have to try that tools.go method to see how it works in practice. Also, LOL, as I just before you posted referred to Jamie as *the* "dependency guy" in the other thread https://elk.zone/hachyderm.io/@anderseknert/113191706986003922 Ping @charlieegan3 — we should look into this for Regal @www.jvt.me@www.jvt.me @arichtman@eigenmagic.net

 Like

Liked Tomas Aschan [ɐ̆sˈkɑːn] (@tomasaschan@hachyderm.io)
Post details
@anderseknert @charlieegan3 @www.jvt.me@www.jvt.me @arichtman@eigenmagic.net Haha, I read that but didn't even realize it was the author of the post I linked. I just searched for something like "go tools.go" and took the first hit I recognized as one I read when learning how to use the pattern 🙈 The proposal had a few nice descriptions of requirements to make it work, too, so I recommend giving that a read too just to avoid some common mistakes that aren't super clearly pointed out in the blog post.

 Reply

Yeah not sure where that came from but as you say, you can pin to a tag/commit, and Go's module proxy stops you from having someone re-push the value of a tag, once it's had someone download a dependency.

You also only pin, as there's no way to do a range, so IMO that makes it nicer and more explicit than other languages / toolchains with respect to pinning

 Reply

Yeah I'm very much looking forward to // tool landing as that'll push more folks to using a tools.go style approach.

I'm seeing some folks who'll use a tools.go in a separate Go module so then it doesn't impact the top-level dependency tree, on top of Go' s inbuilt module graph pruning

Also as much as I recommend tools.go, there's still some things it can be awkward with ie golangci-lint tracked as a source dependency can lead to issues (dependency version clashes, Go version incompatibility), as well as it not being the recommended use case