It reads like the “if” clause only pertains to the second “every”, but it also applies to the first. In this instance it doesn’t make a real difference, but presumably the Englishfier doesn’t know that.
Here’s a random thing I made for RDAP a long long time ago. It has lots of bugs but has come in handy from time to time: https://rdap-explorer.chris-wells.net/
The tweet and video don’t seem to imply this _should_ be a comment.
I have been “learning to program” for 20+ years and would absolutely find this useful as a quick way to get basic information about a chunk of code I’m unfamiliar with.
Not that learning to read code isn’t important, just not always necessarily worth the time (:
"A person commits the offense of terroristic threatening in the first degree if… [with] the purpose of terrorizing another person, the person threatens to cause death or serious physical injury or substantial property damage to another person"
Terroristic threats can kind of be a misnomer. Back in my youth, my buddies were driving in a jeep and ended up getting in a scuffle with another truck drive. My friend threw an empty Gatorade bottle at the driver and he followed them while calling the police. The cops charged my buddy with terroristic threats.
They definitely deserved a charge, but I always thought Terroristic Threats was a strange one to choose.
> They definitely deserved a charge, but I always thought Terroristic Threats was a strange one to choose.
Is this a case where meanings have diverged? In modern colloquial speech "terrorism" means certain kinds of extreme political violence (e.g. bombings) especially that committed by Islamists (e.g. al Qaeda and ISIS). "Terroristic threats" feels like it's legal jargon that may predate that by quite a bit.
Terroristic threats are those made that threaten violent bodily harm or death to recipients, causing them to be "terrorized". Doesn't have to do with political terrorism, but the result of terrorization of the victims.
What the COO did was the definition of a terroristic threat, threatening bodily harm with his actions and, potentially, his words.
Bail terms are based off how likely you are to flee, of which holdings can be a factor, but it's not the only factor.
He's a resident of the area, likely with substantial ties. It's a fairly low-level charge likely to result in probation and therapy. There's very little chance he'd flee.
> Open source programs: If you are a maintainer on an open-source project, and would like to request Heroku support for your project, contact the Salesforce Open Source Program office at ospo-heroku-credits@salesforce.com.
Both the text version of this email (ospo-heroku-credits@salesforce.com) and the mailto it actually links (ospo@salesforce.com) appear to be invalid.
I tried both and got:
> We're writing to let you know that the group you tried to contact ($GROUP) may not exist, or you may not have permission to post messages to the group.
Yeah. I did some Internet sleuthing and found a potential contact for the Salesforce Open Source Program Office and reached out. We'll see if they get back.
So, after contacting Bob Wise via Linked In (as he graciously invited readers of his blog post to do!), I constructed a concise but hopefully persuasive email about why they might want to sponsor me, to eventually successfully get this form response...
> Thank you for reaching out to ospo-heroku-credits@salesforce.com in reference to requesting Heroku Credits for qualified and selected Open Source Programs.
> We are in the process of finalizing the selection criteria and will contact you when we are ready to start the process; we anticipate this as no later than Dreamforce.
> In the meantime, should you have any questions or feedback, please do not hesitate to contact us via the above email address.
["above email address" not sure what it means, the email was sent from a personal email address, which i won't share on HN]
So... not yet, in fact!
I had to look up what/when is "Dreamforce", looks like Sep 20-22.
Well shit. After the Heroku Dashboard issues I moved my OSS project demo instances and PR reviews process to Fly.io, then Render.com, then Railway, then back to Heroku because it was the only one that had a truly free and well integrated process.
I think my primary issue with Render.com was the shared database for PR previews. The way I am setup on Heroku is I run a demo instance that resets hourly and build PR reviews from the Heroku Dashboard when necessary. All with no cost. The shared database makes the PR reviews effectively useless because of the need for the ongoing demo database.
I was also turned off by the default service plan being a non-free one. I got a surprise bill in my first month of testing this because I had not specified the free plan in the service configurations.
Also one of the weirdly nice things from Heroku was the ability to run cron jobs for free. Lacking that I had to create a GitHub Action to handle resetting the demo data every few hours. Just an additional pain.
All valid points. I'm not sure this is what you're looking for, but we have Preview Environments[1] where every PR can have its own database. Happy to chat more over email (in profile).
Depends on your setup I suppose. I use FastMail for this purpose and it both automatically sets the `From` based on the `To` of the email I'm responding to and allows me to click in to the `From` email and type in whatever I want for the local part before sending.
I guess I’m confused. Isn’t that exactly correct?