This is your periodic reminder that heroes don't scale, and extraordinary measures are not a sustainable pattern. Be sure as you move up the stack in your career that you learn to let go of things, enable others to be successful, and delegate. You can still audit the details regularly, but don't let yourself become a bottleneck to everyone else's progress.

@srol @zubakskees the odd thing is `a` and `p` tags also seem to do this and they are in the documentation, unless I am misunderstanding. https://docs.joinmastodon.org/api/guidelines/#formatting

I hate meeting people who immediately start throwing riddles at me like "what do you do for fun" and "how are you"

@Chigaze Those made up scenarios are just vaccines for your brain.

Ok, so here's a major milestone for both me and the studio I'm working in: we've just released a free version of our upcoming game Halls of Torment!

Grace it on Steam and give it a shot. I would love to hear your thoughts on it.
#gaming #Godot4 #GamingOnLinux #indiegame

https://store.steampowered.com/app/2316660/Halls_of_Torment_Prelude/

@timo Thanks for the suggestion! I was only vaguely aware of this use so I started experimenting with how I could do it. The web finger and host meta is obviously straightforward but the current implementation relies on the mastodon profile api. So as far as I can tell I would have to guess which domain was a mastodon one based on the pattern of aliases, which I am not sure if that is reliable. Are there other examples you know if I could look at?

@jwz That makes sense, I totally understand the sentiment in your blog post. When debugging our issues and just looking at tiny sample size of the requests for verification, it was a completely unexpected volume of servers from all just over the place.

@jwz Thanks for trying it out and reporting the issue. Looking at the backend calls this tool is making it's actually getting a 403. You can see that with a curl command as well. I noticed that it is verified on your instance, but not mine and presumably others because of this issue. I wonder if maybe there is some bot detection going on there like the one we talk about in our article. Either way, I think this tool could message this issue better so thank you again for reporting it.

We added #verified links for #WashingtonPost journalists a little while ago, but check out this excellent write-up from @zubakskees on some of the unexpected hurdles we had to overcome, which was just published to #medium

https://medium.com/washington-post-engineering/heres-how-the-washington-post-verified-its-journalists-on-mastodon-7b5dbc96985c

Are you F1-curious? You're in luck!

I've been doing an F1 podcast geared toward beginners since 2014 with my good friends Danny O'Dwyer and Rob Zacny, and we just posted our annual introductory episode that explains everything!

The first race of the season is on March 5th. Buckle up!

Listen here: https://www.f1.cool/blog/216
Mastodon: @shiftf1podcast

I was reading about the silent film era and thinking about how silly the word "talkie" is, and was then forced to really consider, for the first time, the word "movie"

I'm pretty sure Mastodon is the first social network I've been on that didn't immediately ask me to betray all of the people in my address book.

I don’t understand the attraction of being able to talk to computers using breezy casual conversational language; I’ve been telling these little digital bastards what to do for decades using extremely precise formalised language and they still get it wrong

@blaine @atomicpoet Maybe I am misreading, but I think not federating by content is not how many people think about their feeds. I think the personas comments above are spot on. If I'm on my lunch break I want to see my moms status updates, a friends photography, and F1 news. If I am at work I want to see coding tips, CTO statuses, tech news. I think consumers organize by interest or mood and creators are the ones that benefit most from tools tailored to the content. Federation allows for both.

Hiring TWO WHOLE ROLES at The Post!

Engineering lead for audiovisual storytelling: https://washpost.wd5.myworkdayjobs.com/washingtonpostcareers/job/DC-Washington-TWP-Headquarters/Audiovisual-Storytelling---Engineering-Lead_JR-90274250

Front-end features engineer for elections: https://washpost.wd5.myworkdayjobs.com/washingtonpostcareers/job/DC-Washington-TWP-Headquarters/Election-Features-Engineer--all-levels-_JR-90274253

The Post is an awesome place to work and you should definitely apply!

Reach out w/ questions.

@thilo That is very cool! The ability to separate the routes into individual functions or put them on edge with just a flag seems magical. In the past, I have often just gone with the monolithic express function for the DX gains over manually breaking out functions unless there is a clear performance issue... I was already starting to feel the same with the single function I was getting in Svelte Kit... but this seems like a best of all worlds for many situations.

Personally, I wish that the "code red" response that ChatGPT inspired at Google wasn't to launch a dozen AI products that their red teams and AI ethicists have warned them not to release, but to combat the tsunami of AI-generated SEO spam bullshit that's in the process of destroying their core product. Instead, they're blissfully launching new free tools to generate even more of it.

I've certainly used the #ServerlessFramework or #AwsSam (or ECS / EC2) professionally many times, but there is so many decisions that something like #SvelteKit handles for you like #Typescript, dev server reloading, local environment vars, bundling for #serverless, etc. It is so painless to add these frameworks to a service like Vercel or Netlify and get #ContinuousDeployment with zero effort. Do we have full-featured opinionated frameworks like that for an #ExpressJs like setup?

I've been playing around with the #ActivityPub protocol in a prototype project and without thinking about it made it in #SvelteKit despite the fact that it has zero UI. I think it is pretty natural to think that is a "bad idea", but I am also struck by how ridiculously easier it is to make an API in a framework like that and throw it up on #Vercel or #Netlify than any traditional way.

All technology is an absurd game where you jump from one slowly sinking platform to another as hardware changes, operating systems update, underlying libraries evolve, protocols upgrade, and features get added. It's honestly amazing anything ever works.