there's a threshold in organization size that business folks will have so much influence on the tech that the tech just goes bad -- I think the solution is to architect software & organization structure such that they enable tiny startups within enterprises
the example seems to say this should work [https://social.ayco.io/api/v1/statuses?id[]=112486535533351427](https://social.ayco.io/api/v1/statuses?id[]=112486535533351427) but... it doesn't 🤔
My DAC light indicator changes color when hi-res music is playing, I tried some “hi-res” files I found on the web but I think they just edited the metadata because my DAC doesn’t light up the right color.
Here’s my latest case study for a server-rendered HTML of a Mastodon feed with only one progressive enhancement web component (github’s relative-time) — it turned out (surprisingly) pretty good if I may say so myself 🥹
I often do "lateral reading" when I have to learn something. That is, for example, I follow a tutorial and it briefly mentions a configuration property, I will then search more resources that focus on this property
I learned this from some fact-checking documentary before and it is really useful.
I'm hesitating from writing a <time-ago> web component for https://ayco.io/threads ... I know the ideal situation is to not calculate the relative time on the server (for more accurate html info, faster response, simpler), and instead I should progressively enhance this on the browser -- I have to do this at some point
firefox pixel indicators messing with me right now... is there a known issue about maybe inaccuracy in how they show these lines? I know it could also be because I just woke up, I can't handle math right now
After almost two years of being here as my main social channel, I’m seeing that #mastodon & the #fediverse platform reward users’ efforts the more we intentionally curate and engage with our timelines