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:

 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.

 Like

Liked Roy Tang 🇵🇭 (@roytang@indieweb.social)
Post details
I love RSS, but one thing I don't like is that readers typically homogenize the appearance of posts from different sources, which is fine that's how aggregators work. But I miss seeing the flair of individual websites so I often find myself clicking thru entries to see their site designs. I kind of want a stylesheet element in the RSS feeds and feed readers could have a toggle where you can view each feed's entries with their custom styles. I understand how that could break things though.

 Like

Liked jacky (@jalcine@todon.eu)
Post details
Management's role isn't necessarily to break unions but to keep workers compliant with company objectives. If the company is open to a union, they'll only impede it (and keep lower management out of the loop) so much so to make it a burden for workers to manage. If they're more offensive, they'll do what Apple, Trader Joe's, GM, Microsoft, Walmart and other conventional businesses do: take a complete about-face from whatever purported values the company is about and use their own legal prowess to weaken the constitutional rights workers have (it's only a crime if you're tried and sentenced when it comes to companies weakening unions).

 Repost

Reposted Sara Safavi (@sara@hachyderm.io)
Post details
Attached: 1 image Ok I’m doin the thread I said I wanted to do last week. (feel free to mute unless you enjoy a little second-hand drama as a Monday morning treat) Attn #devrel people! Are you job hunting? Does this pic of search results look familiar? Have you ever seen a bunch of job postings like this from Canonical and thought “gee I should apply to one of these”? I’m here to tell you: IT’S A TRAP! 🧵

 Reply

So I think go get -u ./... should get you most of the way? I'd usually reach for Renovate and would create a config file that allows grouping all the dependencies in a single branch, then you can check tests etc pass before merging. But you can also apply those changes purely locally - am travelling today but can shoot over an example tomorrow?

 Reply

Not Lukáš, but wondering what the use case is? Are you looking to get a way to easily bump dependencies? Trying to work out where you may be able to go mod tidy down duplicates/unnecessary deps?

 Like

Liked chort ↙️↙️↙️ (@chort@infosec.exchange)
Post details
How it often works is DevEx & Marketing push out some half-baked thing as a free service driving to drive adoption and generate interest. Generally there aren't many Engineering or Ops resources assigned to these things. Monitoring is next to nothing. No one even thought to consider fraud prevention measures. Many times InfoSec isn't informed at all. When a free service that allows arbitrary hosting, or arbitrary email/SMS content goes out, the first ones to adopt it are often criminals. The end result is you're playing catch-up for months to years to get the proper level of resourcing dedicated to closing the exploitable holes. No one wants to do that for a product that isn't directly generating revenue. The thing is, if you can't afford to assign resources, you should never deploy it. If it's connected to the Internet and connected to your brand, you're going to suffer reputation loss when it's abused, and it WILL be abused. Once I got a free service (temporarily) shut down because I showed our CMO how many complaints we were getting about it from people targeted by abuse. You'll have a hard time convincing random PMs or DevEx folks to limit the project they're working on for their quarterly goals/promotion opportunity. Marketing and Legal leaders will definitely care about reputation damage if you can make a strong, evidence-backed case.

 Like

Liked Stephen B (@belwerks@mstdn.ca)
Post details
Attached: 1 image My wife sent me this screenshot today from her Facebook feed. It depicts a "remember 17 years ago" flashback featuring a friend of hers. The "then" image shows his face while the "now" side is blank... Because he died a decade ago. "Technically Wrong" came out in 2017, filled with numerous accounts of similar situations. This isn't new, but tech giants still continue to roll out this kind of half baked crap with no care for how it might impact the people using their products.