What happened to all the `Cody`s? There were an absolute shitton of them when I was in school and they've all disappeared.

youtube-dl taken down?

https://www.techradar.com/pro/youtube-ripping-site-finally-goes-dark-following-court-ordered-ban

doesn't look like it to me lol

https://github.com/ytdl-org/youtube-dl

https://github.com/yt-dlp/yt-dlp

and remember, it's in a whole bunch of repos at this point. good fucking luck.

greg kroah-hartman: Please let us know if this patch breaks anything, we rushed it because it was important

me: It breaks nested virtualization

greg kroah-hartman's email bot: go fuck yourself

today was a godawful fucking day but remember, I'm not allowed to be sad on fedi anymore.

New Viktor lore just dropped

nostr:npub108zt8c43ulvdwnax2txurhhr07wdprl0msf608udz9rvpd5l68ascvdkr5 well mine should be painfully obvious

nostr:npub1mh5a6mhm4u78glqxhltq7uexv6kddphycthlguvn0ux8ch72tc8q6q233h But it's mEmOrY sAfE!

Be so good at what you do, it causes mental anguish in your lane opponent.

nostr:npub1lareccazvjjjn9x7cprulux8lhlc3n969la32fc96ld68ccjv67qguq5vr I'm gonna triple check with a locally-installed instance that for-sure has this code present. But again, there was a super-holy-shit security update that would have taken the vast majority of instances past this commit, and I should have immediately seen a dropoff.

I will not be sharing publicly what I think they forgot.

nostr:npub1lareccazvjjjn9x7cprulux8lhlc3n969la32fc96ld68ccjv67qguq5vr You should also be aware that this commit is a *direct* reaction to as:Public. I knew about it and I believe I commented on it the day it went live.

So they broke a whole bunch of unrelated services and at no point deployed their own copy of as:Public to see if it even stopped the thing they set out to stop.

I will continue to fight for real security, real safety, real usability, and a real replacement for X/Twitter, even if Claire won't.

nostr:npub1lareccazvjjjn9x7cprulux8lhlc3n969la32fc96ld68ccjv67qguq5vr If the comments saying that this is already a part of the recent (early July) security patches for Mastodon, they must not have done it right. as:Public has only dropped off from instances that outright blocked anonymous timeline access.

The Recorder is getting relay endpoint functionality Soon(TM), and the Collector will be getting the ability to use API tokens in the next release.

Finally, our internal testing has revealed that only 3-5 large instances are required to get 90+% of the coverage we get from 20 or more instances.

Filter dropped a new single https://music.youtube.com/watch?v=dPsYvCSR-I0

I *am* just a little upset that I will now have to compete with Mastodon's native full-text search.

It seems every time I have a good idea and start building an app around it, Eugen just kinda mainlines it.

nostr:npub1ajw6axeack23437kedc8pkwghneenrkh9ljfxxgxumr6t6k4rtvqecaj8d nostr:npub1f8ledq6ja34pn4504vdzzlrv70cu63hvzz5tka229prma42c677qkk7frq I am not allowed to make comments on this sort of thing anymore.

What I will say is that people understanding that public things may be indexed is a universal good for their health and safety. This is because the inverse, telling them that their posts definitely can never ever be indexed, gives them a false sense of security, causing them to post publicly things they may not want searchable.

nostr:npub1ajw6axeack23437kedc8pkwghneenrkh9ljfxxgxumr6t6k4rtvqecaj8d nostr:npub1f8ledq6ja34pn4504vdzzlrv70cu63hvzz5tka229prma42c677qkk7frq I can't see what's being referenced.

nostr:npub10k3qtae5z3fu0mxfyk44hcchuv5cujsp5kpu5aqdrmr04sf0qxuqhw7au2 .... but why?

nostr:npub1tj5fw9d0cpzxe5mtrsnp4mtu2dq50hk05e93y33r0ea6kjd05swq9hl33p I mean, Terry got it done