31–40 of 43 posts
Does anyone still use screensavers? I have set my machines to turn off the screen as soon as that was an available option.
That's super cool, congrats on releasing it ! It's a feature that some people periodically ask me to add in Aerial, but I never got to it. Piping from yt-dlp to AVFoundation is definitely the way to go. I was gonna warn you about a bug in macOS 15+ where your screensaver stays around after you go back to the desktop, but for some reason your code seems to avoid that issue. I'm not quite sure how , as you don't hook s…
interesting you pointed that out because i ran into that exact problem! look at the animateoneframe function, there's the workaround
FYI that works 99% of the time, but for some people it sometimes crashes (because we exit our host container - legacyScreenSaver.appex - and sometimes if you do it at a wrong time things just hang).
> Disclaimer: This project was entirely vibe-coded. I've never written Swift before in my life Something I've wondered - but not had much empirical evidence for - is if entirely vibe-coded projects are difficult to maintain. I, too, don't know swift so I cannot look over the codebase to gauge this. I am curious if any swift savants out there can weigh in. Furthermore, I will follow the project and keep an eye out for…
> is if entirely vibe-coded projects are difficult to maintain Vibe coding is too “Hail Mary” to me, but if you’re into it, I would think the best way to do that is by giving a LLM the git history of the project with each commit contain the prompt that created it and, if a human tweaked things, requiring that human to provide a good commit comment. Then, you could give a LLM the git repo, instructions on what change…
Is this enough? Personally, I have a what very well may be a bad habit of mine that doesn't necessarily check git commit messages. When I'm working in a code base, I just never think about scrolling through those hoping to find where this bit of code was changed. I'd much rather have comments in the code itself. It seems better to me to save the maintainer time and effort. Maybe I've just taken too seriously the idea of "assume the maintainer after you will be a serial killer that knows where you live. don't make them angry by being lazy"
How’d they get Claude listed as one of the contributors? Is that due to changes coming in to the repo from a Claude/github integration?
Does anyone still use screensavers? I have set my machines to turn off the screen as soon as that was an available option.
Also, from a time long ago in a galaxy far away where we had production CRTs that were color calibrated, we would not turn them off either. They had a saver mode as well by running a not quite black signal to them, but not enough to burn in phosphors. It was even meant to "even" out some of them.
So because I'm that old that has used CRTs for such a long part of my life, screen savers will always be just part of the routine.
Does anyone still use screensavers? I have set my machines to turn off the screen as soon as that was an available option.
As much as I disliked open plan offices, I did enjoy trolling my coworkers with fake blue screen of death and kernel panic screensavers. Windows 95 "Pipes" also got a lot of nostalgic shoutouts when I used that for a while.
That's super cool, congrats on releasing it ! It's a feature that some people periodically ask me to add in Aerial, but I never got to it. Piping from yt-dlp to AVFoundation is definitely the way to go. I was gonna warn you about a bug in macOS 15+ where your screensaver stays around after you go back to the desktop, but for some reason your code seems to avoid that issue. I'm not quite sure how , as you don't hook s…
interesting you pointed that out because i ran into that exact problem! look at the animateoneframe function, there's the workaround
You check if the screen is locked, and if not, kill the host. But screen is not locked in System Settings. So basically, you're killing the host process every 2 seconds (and macOS, at least in Tahoe, restarts it, it doesn't in previous macOS versions).
That's also what causes your issues with "Options" not working (because you killed the instance that was linked to that button). The way we workaround it usually is to hook a system event.
You can check https://github.com/AerialScreensaver/ScreenSaverMinimal
Look for handleWillStopNotification and com.apple.screensaver.willstop
Nice work! Excellent, advertising-free live streams to choose from here: https://www.youtube.com/@MontereyBayAquarium/streams I often turn on the kelp forest (sound muted) as a pleasing backdrop on my living room TV, but they're all pretty neat.