Notices by Gytis Repečka (gytis@fedi.lt)

@tokyo_0 Are they maybe paid by Meta to do this? 🤔

@itsfoss @peertube Upgraded to v6.0.0 few moments ago - it was pretty smooth 👍 Thanks :peertube: for detailed release notes 🥳

@aral I never trust Ubuntu upgrades anymore - they break even on minor releases these days 😔

AI "superstar" Sam Altman fired from OpenAI (company behind ChatGPT) yesterday (Friday), according to the board, because he: "was not always truthful with the board". There is no better way to summarize the whole AI hype in tech industry, really 😄 #news https://edition.cnn.com/2023/11/17/tech/sam-altman-departs-open-ai/index.html

@filipe @aral Yeah, but should perhaps see if :gitea: grows evil or not. While it's still exactly binary compatible it's only a matter of which brand you want to see 🤓 While Gitea was initially forked from Gogs, it evolved a lot - Gogs functionality is far behind, really.

@dansup @Mrfunkedude The way how PeerTube does it? :peertube:

@aral Something new this Trump of Tech did or just regular? :elon:

@feditips Are underscores preferred over camel case to separate words for screen readers or there is no difference?

@jwildeboer I bet most of their marketing specialists don't even have a clue what fediverse is 🤷♂️

@aral @jan Yet it is often problem when developers use database just to persist data without proper guidance from database experts. Maybe it's not the case with Mastodon (although mentioned query suggests), but I've seen far too many projects where devs just do "dump all" and "select all" with terribly narrow understanding of "if it does not perform - just add another index" 🤓

@aral @jan It is insanely bad query programming to have 3.5k IDs in WHERE clause 🤯 Considering table is properly indexed and vacuumed, I would split them into 100-200 microbatches and if each involves pinging a separate server of a follower account, even make those batches smaller. LIMIT and OFFSET should be the start from database side and then some task queueing from backend 🧐 #postgresql #sql #performance :postgresql: