It doesn't block everything, but almost nothing is getting through for me.
963 karma · joined April 30, 2016
Socials: - bsky.app/profile/precioso.design - github.com/cprecioso - linkedin.com/in/cprecioso
---
[ my public key: https://keybase.io/cprecioso; my proof: https://keybase.io/cprecioso/sigs/1X7I415iPxyBFFOSmQxGPcv4TWbhRi-3AHEjw2gU-Zw ]
I'm linking my keytrace.dev: did:plc:h22ajfwlv7pvlhxqzi3dsiaj
It doesn't block everything, but almost nothing is getting through for me.
Next step is something like OpenBanking in the UK which does ask for common APIs.
Moreover, in async functions you can take advantage of regular `try`/`catch` when awaiting; it seems you're just swallowing errors in your functions, which I guess is fine for the code you're showing. But keep in mind that a better practice is to let those function throw and catch it with a try/catch at the callsite.
Lastly, when calling the functions to save and send the email, you can use `Promise.all` and parallelize them instead of running them serially, as they don't seem to depend on each other. If you're meaning to send the email only after it is saved, then you need to check the return value of the saving before that; because neither of the calls will ever fail; just return undefined.
I made it so I could follow some Spanish radio shows which have an audio podcast but upload extra content to YouTube, so I could follow right along my other podcasts. This way I get precise markers of where I left off, viewed/not views indicators, etc...
I've been using it for quite some time, with no problems whatsoever. However, I just released an update which lets you use it with iTunes; and removes the requirement for a YouTube API key.
I have a public instance at https://tubecaster.now.sh . It is heavily cached. You can use it to try the program, but please deploy it to your own server if you plan on using it further! Also, I might break something from time to time, so better not to rely on that public instance.
At any rate, tell me what you think and if you find it useful! Thanks!
Word processors don't have this concept, and what you see is (supposed to be) always exactly what you get. So Pages doesn't display dark documents because the output then should be a dark document.
The new website looks like a standard marketing page that is trying to sell me something I don't need, and they have also lost the third-party linking. I think the immediacy of its usefulness is completely lost now.
Also maybe there's an argument to be made about this being time invested in a feature (notch support that the OEMs were already implementing) rather than wasted.