Software engineer and history nerd. Strongly pro Capitalism. Opinions are mine. He/him.
| https://twitter.com/tetodorov |
| https://twitter.com/tetodorov |
In this post, we show how the Carrier and AWS teams applied ML to predict faults across large fleets of equipment using a single model. We first highlight how we use AWS Glue for highly parallel data processing. We then discuss how Amazon SageMaker helps us with feature engineering and building a scalable supervised deep learning model.
Three ships have been tracked safely making the journey to Ukrainian ports as NATO warplanes circled overhead. Despite a lot of threatening talk in recent weeks, the Kremlin took no action.
@kikobar @mekkaokereke @darnell There’s no need to run instances of #Threads because Threads will soon federate via #ActivityPub.
And by federating via ActivityPub, they get data from #Mastodon, #WordPress, #PeerTube, #Kbin, etc. – unless, of course, those ActivityPub-enabled servers choose not to federate.
(Sidenote: Meta can still get that data via RSS, but it’s probably better for them to receive via push request than pull request.)
Most social media companies don’t want to be publishers. They’d rather be platforms. And if you’re building a platform that merely integrates with an already existing social network (the Fediverse), you have all the more reason to say you’re not a publisher.
This way, when those politicians call Zuckerberg down to Washington, and ask him why he’s hampering their freedom of speech, he can just say, “No, we can’t hurt anyone’s freedom of speech – that congressman we kicked out of Threads a month ago can set up a Mastodon server if he wants…”
Of course, I can talk about the many other benefits of not being a publisher but that would take much too long.
How Threads’ privacy policy compares to Twitter’s (and its rivals’)
Here’s what is collected by Threads, as well as by Twitter, Bluesky, Mastodon, Spill, and Hive Social.