IndieWeb post types
This content type is full of IndieWeb post types, which are all content types which allow me to take greater ownership of my own data. These are likely unrelated to my blog posts. You can find a better breakdown by actual post kind below:
I'd thoroughly recommend https://gatling.io/ as we're using it across both Java-based and non-Java-based APIs, and have found it pretty great.
I know we're not using nearly the power it affords, but it's very good!
You don't need to know that much Scala too, it has a straightforward DSL before you get there
Not sure how I'm going to cope next week without a litre of sangria and a steak a day 😅
Between and I took 7030 steps.
Thanks, both you and https://david.shanske.com have recommended Pushover and it seems to be OK price and rate limit wise so I think I'll look into it. It helps that I don't need to create an Android app myself to receive notifications, unlike https://pushy.me
Thanks that looks like a reasonable one. I couldn't see anything specific pricing wise for it, but the official pricing looks like I'd be in a free tier 👍🏽
Yes! I've got a list of my blogs that I follow explicitly at https://www.jvt.me/blogroll/ but also use several aggregation sites to pick up other content
What are folks using for free/low cost notifications for personal projects? I know https://indigenous.realize.be uses https://pushy.me and until now I've used https://pushbullet.com, but given https://www.jvt.me/mf2/2020/01/yelaf/ I may need to replace it with something more substantial
No worries - they're every two weeks! They're also more self-directed so being a less-experienced member there is more than ok, but depending on who's there it may be more conversations about what you're doing rather than technical help
This looks awesome, great stuff! If you want to come work on it with like minded folks, I organise #HomebrewWebsiteClub Nottingham, next event on Feb 5th https://events.indieweb.org/2020/02/homebrew-website-club-nottingham-8IgcYeAQhIKX
Anybody can write good bash (with a little effort)
I used to write a lot of shell scripts before realising that what I was trying to do was treat shell scripting as a "full" scripting language (I won't define here what I mean by "full").
Its not - reach for a higher level scripting language like Ruby or Python when things are getting more complicated, and allow shell scripts to glue things together, or be for quick tasks maybe a few lines long.
When you do write them, this advice is great but it's definitely worth gaining understanding of when you should and shouldn't use them.
Recommended read: Anybody can write good bash (with a little effort) https://blog.yossarian.net/2020/01/23/Anybody-can-write-good-bash-with-a-little-effort