Marco Dalla Stella @mdallastella@functional.cafe

So, I'm working on this parallel workflow execution framework in #clojure using a #datalog implementation (datalevin) as temporary store.

Basically you define a job with some tasks, the relations between tasks and the framework took care to execute them in the right order (topological sorting and so on).

Parallelism and concurrency are achieved with clojure.core.async.

Using datalog as query language gives some help managing jobs and tasks relations: it's almost like having a graph db.

Of course we are going to release it #opensource when ready.

I can write about it a little bit more if anyone is interested.

That's quite surprising, I always thought it was media attachment the major reason for disk space eating. Wll surprise:

mastodon at functional in ~/live 
$ RAILS_ENV=production tootctl media usage
Attachments:    6.37 GB (854 MB local)
Custom emoji:   920 MB (0 Bytes local)
Preview cards:  38.4 GB
Avatars:        6.18 GB (7.09 MB local)
Headers:        13.1 GB (12.2 MB local)
Backups:        0 Bytes
Imports:        0 Bytes
Settings:       0 Bytes

Hi everyone, for a bit of instance transparency: here's the actual list of other mastodon/pleroma instances that are currently block (at different levels) by functional.cafe:

• freefedifollowers.ga (suspended)
• kiwifarms.cc (suspended)
• freespeechextremist.com - (suspended)
• lets.saynoto.lgbt (suspended)
• newjack.city (suspended)
• baraag.net (silenced)
• raki.social (suspended)
• shitposter.club (silenced)
• switter.at (suspended)
• pawoo.net (suspended)

You can find the differences between silenced and suspended here

#functionalcafe I probably found the home timeline issue, let's see in the next hours... #hopeforthebest

Hi #functionalcafe friends. As you surely have noticed, there were some issues with the instance lately. I'm trying my best to figure out what the hell is wrong with it.

I made some changes tonight, let's see how it goes.

Please, don't be afraid of contact me if you see something strange. You can direct message me or any other way.

There's some ways to contact me on my profile.

Thanks.

More and more "Mr. Knowitall"-like people nowadays.
Everybody seems to knows how to solve world-wide problems and who is to blame for those.
Strangely, tho, the ones to blame are always someone else.

"They call me Mr. Knowitall
I will not compromise.
I will not be told what to do.
I shall not step aside.

They call me Mr. Knowitall
I have no time to waste.
My mouth it spews pure intellect.
And I've such elegant taste."

https://www.youtube.com/watch?v=WFcUJ1tDqDA

Looks like old toots (2017) have problems to be serialized by Mastodon, that's what crash the migration...

Ok, guys, first issue, looks like the migrator doesn't support Mastodon v3.x.x yet:

https://gitlab.com/soapbox-pub/migrator/-/issues/8#note_393162611

Guys, I'm making the first migration test, if everything goes smoothly, I'm planning to do the full migration tonight.

A quick clarification about the instances list I posted yesterday: it is not a list of dead instances, my bad. As @loke pointed out, https://mastodon.sdf.org/ is alive and well.

The process I started on monday was checking all remote accounts of this instance (about 115k). These accounts are followed by or follow one or more accounts of #functionalcafe.

The remote account can be unreachable for different reasons: the instance is down, the ssl certificate of the instance is no longer valid or the remote user doesn't exist anymore.

At the end the process (tootclt accounts cull[1]) spits out a list of all the instances involved.

[1] https://docs.joinmastodon.org/admin/tootctl/#accounts

If you are curious about which instances are no longer reachable from #functionalcafe, I put a list here:

https://gist.github.com/mdallastella/9b00f08e51b2a0d7c1d585cad86f35c2