I've got an old Mac-Mini 2012 laying around. It was a gift. I never wanted to switch to Mac on this solid, but not very powerful machine. Over xmas last year I booted the thing, and it was unbearable slow, even with the original version of the OS on it. After an macOS update, it was unusable.
I put an SSD in (thanks YouTube for the guidance) and booted it with Debian and on top of that installed CasaOS (web-based home server OS/UI). Now I can access my music (thanks Navidrome) from on the road (thanks Wireguard).
Docker is still a mystery to me, but I already learned a lot (mapping paths)
My domain has been running on a Mac Mini 2012 since new using Mac OS. Internet services are generally constrained by the available bandwidth and don't need much processing.
Zen Browser (FF) on Win and Firefox on iOS (for sync) works well for me. Edge for all M365 related stuff. Still use Chrome for web dev. Not sure what to move on in that regard...
I'm a relatively new web dev and I've been quite happy with Firefox's Web Dev tools. What does Chrome's dev tools give someone that Firefox's doesn't? I can edit css on the fly, see where a css rule is being overwritten, debug javascript, etc.
I use FF but Chrome's dev tools have a lot more going for it including memory profiling and performance tools. On the other hand, Chrome's network panel is awful and it's a chore to see the domains and full URLs involved.
Workspaces allow you to give Chrome permission for read / write access to given folders. You just set it once per project and then Chrome remembers.
Basically, you can press "ctrl S" for save, straight from the dev console. In FF, you have to manually designate the save location each time. It may seem like a small thing, but it's an entirely different workflow.
For frameworks that don't use plain stylesheets, it may not be useful.
Is it easier to build a browser for MacOS? Arc was Mac only for the longest time, until they released a crippled Windows version. DuckDuckGo browser started Mac only.
I put that on our website, since I love RSS. We are not a tech company, though, so none of the potential applicants use it. I think some scraper/job boards consume it, but that's it. I built it mainly for fun and to signal virtue :)
I'm using Huffduffer for a while and it's really good, since I can create a podcast feed from any available audio on the web and it extracts audio from several (video) platforms and stores it for a month.
> Huffduffer takes the pain out of podcasting found sounds.
This is perfect. I love that it fits seamless in my audio/podcast flow. I was listening to articles via Pocket before, but it's not as good as your product.
I suspect this will cost money sooner or later (text2speech and audio storage) - what are the plans here?
Honestly we don't have plans around making $ figured out. It started as a side project, and I feel the first step is to figure out if we built something valuable. If there's significant demand, we'll think of ways to monetize.
Could you elaborate on whats missing from Pocket? And 2) Is there anything on your mind we could add to make audiblogs 10x better for you?
I just love how natural the voice sounds (don't even need other voices) and that it shows up in my podcast player so I don't have to switch to another app.
The voices in pocket are not as good I think.
I guess what's missing in the podcast feed, is a direct link to the source article. But else, it's perfect.