@dragfyre I'm about to start Book Three myself :)
@ceoln check his instance rules, and if he's violating those, report him and check the box to forward a report to his server admins. If not, just block the user or his whole domain.
By the way, if you are starting up your own fediverse server, it may be tempting to blindly copy someone else's block list, but some corners of the fediverse have been a bit over eager with full instance bans, in my opinion, which tends to break the whole federation model (imagine if you couldn't email anyone with a certain university's email domain because your email provider disagrees with the university policies).
If an instance is putting a lot of irritating stuff in your server's global timeline, it might be better to just mute them from the global timeline.
@albertcardona It's a deliberate block on their end. Generally, when an instance blocks us, we take that to mean they don't want us to communicate with them, and we try to respect that wish, so we haven't asked them to reverse their choice. On the other hand, *he's* always welcome to reach out to *us* (we don't block them back), especially if he thinks there's a reasonable prospect of reconciling our instances. I can speak with their admin out-of-band to try and smooth things over, but I'm not going to initiate that without some indication he's okay with hearing from us.
@padraig as an exception-to-the-exception, replies to one's own post *do* appear in the timelines. They carry a "Show Thread" link, unlike top-level posts.
@realcaseyrollins @nice-verse You're welcome!
I'm afraid I don't really know what version of the Bible it uses - it might be the "New English Translation" if that's a possibility? It doesn't look like either the ESV translation given me by a friend or the NABRE one they used at a study I attended with my girlfriend some years ago.
@realcaseyrollins there are several, but most look defunct. Here's an hourly one that's still active: https://nicecrew.digital/@nice-verse
@realcaseyrollins Control-Tab/Control-Shift-Tab also works in fullscreen mode, at least in Firefox. No tabs or X shown at all in the interface when you do that.
Now I'm thinking I should do my next presentation as HTML instead of LaTeX+Beamer. Something to try!
@bartulem Interesting! A new generation of SCIgen is here to give publishers hard choices to make.
Also, you have 64k characters on QOTO! Your posts will be easier to read if you don't artificially segment them like that.
@peterdrake apparently this is by design - there is a school of thought within Mastodon that someone shouldn't know that he's blocked, because it's desirable for him to spend his time fruitlessly trying to fix what appears to be a network problem, as a sort of tar-pit approach to wasting bad actors' resources. A more transparent behaviour was [implemented](https://github.com/mastodon/mastodon/pull/10420), but rolled back after objections. I suppose we could implement such a notification on QOTO's local fork, as long as we stay responsible about getting rid of people who engage in block circumvention.
@markmccaughrean Check out QOTO too - we have a STEM focus and are always happy to welcome new users!
At first a bit confused about #Mastodon servers, how to choose and their significance. Thinking about it as domain kinda helps: public servers a bit like the gmail/hotmails of email, organization servers in the future like blue checkmarks. In the meaning, “yes, this is a real person, part of this organization”, which could be government, university, health care, media companies or even any other type of private company - which could solve *some* of the problems Twitter has.
@CanXClV Mastodon is a microblogging platform, and large videos aren't really in its scope. But QOTO also has a Peertube instance at video.qoto.org which is designed around handling this type of content. The best part is that it's on the Fediverse too, so you can follow your Peertube account from your Mastodon one and boost your videos to your followers here, and they can reply just like a normal Mastodon post.
@aut Follows are part of ActivityPub. The other party gets a notification, depending on their settings he may have to approve your request, and if he blocks you it will remove you as a follower. If you follow someone, you get to see all his posts at the "follower only" privacy setting, and he may reciprocate by following you back.
Subscribes are essentially a way of scraping the other party's public feed. Neither he nor anyone else gets any notification, and the only way it is stopped is if we get blocked at the instance level. It tends to be more robust, because as long as the other instance allows QOTO to fetch its RSS feeds, it will work even if authentication or something breaks. But the tradeoff is you don't get to see "follower only" posts and he won't know to reciprocate.
Generally, if following isn't working at the technical level, it's worth trying a subscription. It's also a useful technique if you think following that person might expose you to harassment, because each person's follower lists are public. So if you think there might be a cyberbullying campaign targeting followers of a controversial account, it's safer to subscribe than to follow.
@freemo I think it's unlikely, since we can still see forcibly load toots by putting their URL into the search bar, but they don't otherwise seem to make it to us, unless they've been boosted by a follower on another instance. @rantingsteve
Hi @freemo we seem to be having trouble federating with interfaith.masto.host - any idea what might be the trouble there? Seems to show only isolated posts, but I don't think we're blocked. I'm not sure if they can see us either, but I'm tagging their admin @rantingsteve / @rantingsteve@vulpine.club in case he can see this, and there's something he can do to help.
@worldsendless it's more like custom privacy settings. You set up a circle that includes certain people and then select it from the privacy dropdown. It behaves as if you'd selected followers-only and, for that post, they were your only followers.
@freemo no objection whatsoever, the extra help would be very welcome these days!
@ktschuett LaTeX support is currently bugged due to some complications with the CORS permissions. There's a workaround, at least in Firefox, but it impairs browser security so it's not generally recommended.
> Clearly the result of the Musk takeover.
Well, partly. It's also partly due to the first half of the week being Divali, and a lot of the Indian spammers who make fake accounts for SEO purposes were on holiday. So when they came back at the end of the week, the rate of new account creation picked back up.