They are pole-ish.

One student told police the conversation became disturbing, saying it was apparent Worley “did not care at all”. Worley made statements about snorting cocaine off of a hooker and described multiple sexually explicit acts, after asking students if they knew what “iglooing” and “snowballing” were. One student told police Worley taught two kids how to give a man oral sex, “walking them through the process step-by-step”.

Multiple students overheard Worley tell the students that the lowest age he would date was 14-years-old.

If compiled languages bother you, then you’re gonna love assembly.

Lyman was the worst. I’m glad John locked him in the basement never to be seen again

A gui is helpful sometimes, but there’s a lot of cases where there’s no feasible way to make a good gui that does what the terminal can do.

Right tools for the right job.

For example, a gui to move a file from one folder to another is nice - drag and drop.

A gui that finds all files in a directory with a max depth of 2 but excludes logs and runs grep and on matching files extracts the second field of every line in the file? Please just let me write a one liner in bash

If you want to federate, then yes. Your instance needs to accept the activity pub messages sent by the instances you federate with. You would also need to send out the apub notices whenever you do activity on your instances

You can solve your “problem” by running your own instance and federate with whoever you want

I know some of those words!

Due to how federation works, the federated instance needs to accept and process the activity. Each application can define its own “optional” activity properties, but the activitypub specs define mandatory properties and some optional properties for coherence across the fediverse.

The way lemmy implements this is to use the activitypub-federation-rust library that the lemmy devs built. Through this, activities in Lemmy are sent using HTTP and have a failure retry:

It is possible that delivery fails because the target instance is temporarily unreachable. In this case the task is scheduled for retry after a certain waiting time. For each task delivery is retried up to 3 times after the initial attempt. The retry intervals are as follows:

one minute, in case of service restart
one hour, in case of instance maintenance
2.5 days, in case of major incident with rebuild from backup

In the case of votes, the activity is a “like” - some other federated applications understand this and will accept it, but others won’t. For example, peertube does not have a like activity, and I don’t believe they would handle it.

However votes are shared across instances. When a user “likes” something from another instance, Lemmy will notify that actor (the page) that the activity (a like) was emitted by another actor (you).

Hope that clarifies things. I’m still learning all this myself so if anyone can contribute or improve my answer, please do!