Its 2019. No List of "must reads" in #childlit should be free of books about people of color written by people of color: theguardian.com/books/2019/jul… There children's books about refugees not just Paddington Bear as a metaphor #literacies #EDU407Sum19 (quickthoughts.jgregorymcverry.com/s/r0q36)
Check out this Meetup: CSS.la workshop on CSS Grid meetup.com/LearnTeachCode… #Meetup #SantaMonica via @Meetup
Animated interactive of the history of the Atlantic slave trade.: slate.com/articles/life/…
Putting my spinner luggage through the true @indiewebcat test.
Humanity is so utterly, thoroughly fucked… 😶😢
Get off WhatsApp. “Facebook announced earlier this year preliminary results from its efforts to move a global mass surveillance infrastructure directly onto users’...
Following my last post about automatic updates in Dobrado I've already had to make a few changes to how it works. I realised that if there were any mistakes in a new build, then the problem would be dutifully rolled out to all subscribers without a chance to prevent it.

The fix was to create a second updates feed, this one is available at: https://dobrado.net/testing. Now when an update is built, a post is created in this feed. I still write the post to the original updates feed at https://dobrado.net/updates, but these posts are now saved as a draft with a scheduled publish time. At the moment that time is set to 24 hours later. Of course my publishing tools didn't have a concept of draft posts so I had to add that too... next I need to add UI support to make this feature available to users, at the moment it is only used by the Autoupdate module.

Lastly I added support for removing updates. This needs to happen so that the current version number can be re-used rather than leaving the current broken version in place. Sites that are subscribed to the testing feed will also need to re-apply the update at the current version number, and this is done by the build server removing the matching post in the feed. When the Autoupdate module sees that the post was removed from the feed, it will remove the matching version of the update. This means it will be able to install that version again when it is eventually re-published. The draft post also needs to be removed on the build server, but after that anyone subscribed to the updates feed will never know there was a problem.

So now I have a couple of servers subscribed to the testing feed, and the others that I really don't want to break when I build an update are subscribed to the normal updates feed.
We had that choice some years, maybe decades ago. By now the choices are only about the shape of the descent. Imho better focus on the choices we can make today that still matter.
Marshall Kirkpatrick https://twitter.com/marshallk
“Either we radically transform human collective life by abandoning the use of fossil fuels or, more likely, climate change will bring about the end of global fossil-fue...
As hobbies go ... I’m an amateur. twitter.com/seamusblackley…
Just now, the dormant yeast I collected this week from Ancient Egyptian artifacts (with help from @drserenalove and @rbowman1234) is being fed grain for the first time in...
I'm not eating ice cream every day - you are! (@ Salt & Straw in San Francisco, CA) swarmapp.com/c/k1pt4kFnmqA
lol i bought candy as a gift and ended up eating it myself. Now I have to go back to the store. whoops. 👀
Spent all weekend working in the house. The kids now have their own rooms! William’s is basically done, with Colette’s still requiring a lot of work. Then, the playroom becomes a guest room and office for yours truly (my eventual reward). 🏠🔨

TWP and Information Literacy: An Action Plan

Carry on packed with every thing I need for a month in the -UK. Headed to London tomorrow.
tarsnap.com is the bee’s knees when it comes to backups. I could see someone making a service on top of it to make backups easier for people. (v2.jacky.wtf/post/df12b9ee-…)

https://www.tarsnap.com/ is the bee’s knees when it comes to backups. I could see someone making a service on top of it to make backups easier for people.

Anyone got tips for # **Rust** that involve a way to do debugging outside of print debugging? Print debugging is pretty undefeated and a universal way to test but it’s not maintainable. JavaScript has the Chrome/Node debugger, C++/Python with gdb… v2.jacky.wtf/post/ba6dba91-…

Ooh, just found about https://rr-project.org/! #rust

Anyone got tips for #Rust that involve a way to do debugging outside of print debugging? Print debugging is pretty undefeated and a universal way to test but it’s not maintainable.

JavaScript has the Chrome/Node debugger, C++/Python with gdb, Elixir with Erlang’s thing.

Yerrr