SHARKTOPUS is a user on capitalism.party. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

SHARKTOPUS @sharktopus@capitalism.party

Lots of work starting to come together finally! If you have any interest in learning about Continuous Deployment or Kubernetes check out the early access for my upcoming book here: withku.be

All feedback, questions, comments, are greatly appreciated -nj

SHARKTOPUS boosted

#FreeRadical blog: "S3 URLs have changed; update your Content-Security-Policy"

I’m serving Free Radical’s images etc. from S3. When I updated to Mastodon v2.1.0, I noticed that all the page’s images were missing. Safari’s Show JavaScript Console menu revealed a lot of errors like: [Error] Refused to load s3-us-west-2.amazonaws.com/fre- [...]

blog.freeradical.zone/s3-urls-

(posted at Fri, 15 Dec 2017 22:26:57 +0000)

Welcome @sovereign to our fine mastodon instance!

working on some art asset generation stuff, very much work in progress but even after 1 training session it's looking pretty dope to me!

capitalism.party/media/uKCv0Zd

There are some stylesheet issues on the landing page buttons but I don't have any more time to mess with them for now

just a heads up, gonna take this instance up to the latest version later this week

What is consciousness, and could machines have it?

science.sciencemag.org/content

This article is a great overview to the computational consciousness perspective, get it off sci-hub if you don't have journal access!

turns out Babylon 5 is incredible

I read the warren v. district columbia decision a few days ago and I can't stop thinking about it

alright we're on 1.6.1 now, sorry for the delay and thanks @kunev for the reminder :P

your daily reminder that all models are incorrect

Rick and Morty is the best 20 minutes of television that's ever been produced

going to bring us up to 1.6 in a couple days, would do sooner but I'm currently traveling and wan't to be able to watch the site appropriately in case there are any issues post upgrade that require manual attention.

prevention steps for the future: added an additional node to the cluster, upped the replica count for sidekiq and streaming to 2 for better redundancy against single node failure. I have a generic monitoring/alerting solution written out, but haven't yet deployed it on this cluster, oops! Will get that deployed so I get better mobile downtime alerts on triggers like frequent pod restarts, 0 available replicas in a set, or no endpoints for a critical service.

and we're alive again. Finally caught what I believe was thrashing the nodes: "find /mastodon -path /mastodon/public/system -prune -o -not -user mastodon -not -group mastodon -print0 | xargs -0 chown -f mastodon:mastodon" in the entrypoint script.