

I would play games and work on my many many side projects. I’d have so much more time for that (and let’s be honest, maybe some games) if we had 4 day work weeks!


I would play games and work on my many many side projects. I’d have so much more time for that (and let’s be honest, maybe some games) if we had 4 day work weeks!


also worth noting that I’d have all the data in the Lemmyverse.net data, I could probably build a page that shows something similar to this graph.


Unless your using an LLM to make simple one-page HTML pages. In which case it likes to reinvent the wheel every single time. 🤣


This is unrelated to the post, China is using the same source material, they are just never going to be sued for using it 😁


are you saying that we’re not all here commenting, regardless? 😥🥹


My self hosted gitlab instance has better uptime over the last 12 months than a billion-dollar SAAS product 🤣


I mean their TOS literally says “… we can’t promise that any Copilot’s Responses won’t infringe someone else’s rights (like their copyrights, trademarks, or rights of privacy) or defame them. You are solely responsible if you choose to publish or share Copilot’s Responses …”


I check it every day before I use CoPilot 😁


I turned it off ages ago, and if you already had it off, it’s staying off. (for now at least)


The issue here is this is a client certificate, issued within the League client, for seemingly local<->local traffic. This ain’t no typical HTTPS ceritifcate, it’s bundled into the client build. See from the source “League client’s hard-coded certificate meant someone at Riot would’ve needed to remember it required updating before its expiration date.” So, not quite as easy as configuring an ACME CRON, but something that’d need to be remembered or have some kind of internal reminder for.


You think we’ll still have Google and DuckDuckGo to go back to?


LMAO they actually said that 🤣🤣🤣


Last I checked, those aren’t countries 😁


deleted by creator


There are some standards, used to ensure content is readable, and comprehensible by tools like screen readers. https://www.w3.org/WAI/standards-guidelines/wcag/
It’s just that most websites don’t respect them, as implementation can be a challenge.


This only affects sites that use the fancy new-fangled SSR rendering from what I’ve read. ReactJS (Client side) sites wouldn’t be affected.
My brand new 2026 Lenovo also has one!