Notices by Michael (michael@mstdn.thms.uk), page 2

@jessi @BeAware

I’m really not sure whether it’ll work with Sharkey. Does sharkey have a mastodon compatible api?

@BeAware @leberschnitzel yep. This problem is exactly why FediFetcher was invented, and it works amazingly well to address it. But I might be a little biased 😉

Have a look at the readme, and let me know if you have questions.

@jwildeboer sadly at least mastodon doesn’t work like this at all.

In mastodon only self-replies by the OP are part of the activity pub replies collection, which is the reason that replies don’t federate well, and why we need FediFetcher.

@jerry I actually did push to production 3 times today - and it’s only lunch time 🤷♂️

Anyone here familiar with the #Peertube API?

According to the docs there should be an endpoint that gets the ‘comments threads' of a video, but that API only appears to get top-level comments. Is there no way to get replies to comments on Peertube, without requesting them one-by-one?

https://docs.joinpeertube.org/api-rest-reference.html#tag/Video-Comments/paths/~1api~1v1~1videos~1%7Bid%7D~1comment-threads/get

(This is for #FediFetcher - trying to fetch Peertube comments)

Related to the above: Does anyone have a list of the most common Fediverse services, ideally with 'marketshare’ (of active users, or something like that)?

Context being that FediFetcher now supports a dozen services (any that implement the Mastodon, Misskey, Lemmy, or Peertube APIs), and I'm wondering what other services would be valuable to implement.

#FediFetcher #Fediverse #fediadmin #mastoadmin

I've just released #FediFetcher 7.1.4.

This adds a small number of minor improvements, so definitely worth upgrading to. Visit the release page for full details:

https://github.com/nanos/FediFetcher/releases/tag/v7.1.4

Working on FediFetcher might be somewhat addictive 🙈

Today I present v7.1.3 with a new feature that was requested almost exactly a year ago: FediFetcher can now fetch data from your lists 🎉

It also fixes a bug introduced in 7.1.0.

For all details including update instructions view the release page:

https://github.com/nanos/FediFetcher/releases/tag/v7.1.3

#FediFetcher #MastoAdmin #SingleUserInstance

@rapha3l I'm not really sure, to be honest, but I got a feeling that it's sort of both.

What I know for a fact, is that it's the same as if you entered the remote post's URL into your Mastodon instance's search bar. But I'm not 100% sure what doing this does to federation.

AFAIK, 'federation' isn't a binary matter. I.e. it doesn't appear to be a question of two instances exchanging everything or nothing.

As far as I can tell, federation (at least in the context of Mastodon) is based on who follows whom and what. That's why, for example, even though I follow several people on mastodon.social, I still need to fetch many replies from there.

So, I think that's what's happening here: The two instances will be federated in that they are aware of one another, but they won’t be exchanging every message going forward.

That is my understanding anyway. I hope someone will correct me if I'm wrong.

#mastoadmin #fediverse #fediadmin #activitypub #mastodon

Oh the irony that Meta’s Threads out of all services has a robots.txt that just blank disallows everything 😅

https://www.threads.net/robots.txt

@nixCraft originally my hard drive.

Then some source control system that I never understood and that as far as I could tell ran on a PC that was under my boss’ desk. A nightmare this was!

Then I convinced the boss to let me install and configure git (including some post receive hooks that would automatically deploy to production) and ssh on one of our dedicated servers (we were an IIS house at the time, so neither came pre-installed).

I was so proud of myself at the time, but I think GitHub came about a few months later, so my system didn’t live for very long…

I have just released v7.0.5 of FediFetcher.

This is another small release. The only new feature is that there is now a —log-level configuration option that you can use to quiten it down a bit. Thanks @andrew for contributing this!

Additionally it contains a couple of security updates.

More info including update instructions can be found on the release page:

https://github.com/nanos/FediFetcher/releases/tag/v7.0.5

#FediFetcher

I cannot believe that I’ve just switched the heating back on. This weather is unbelievable! 😩

@mttkng @linus not to brag, but FediFetcher has a few more than 3 stars on GitHub though 😁

Woha, this is unexpected: in a future update mastodon will automatically turn off open registration if no mod has logged in for a week or longer:

https://github.com/mastodon/mastodon/pull/29318

This is great news, and should hopefully significantly cut down on abandoned servers being used to send spam!

(And this is in addition to also having open registrations off by default on new servers.)

Great news!

#mastoadmin #spam

Oopsie. Just back from a 1 hour downtime caused by my hard disk running out of space in the middle of the working day 🙈

Back now thanks to pg_repack. Insane how much space the indexes waste on mastodon!

#mastoadmin

@pfefferle really good to know, thanks! Can you tell me the URL of a Wordpress blog that has the mastodon compatible plugin installed? I’d love to pull the node info from there, so that fedifetcher can support it.

Hoping the hosted version will support it too, soon 🙏😉

@pfefferle no worries at all!

Does the WordPress integration support the mastodon, pixelfed, or misskey API?

@troed

@pfefferle @troed

Hm. I haven't looked into WordPress’ AP implementation yet, so I don't know if FediFetcher can support it. But generically what I would say is that FediFetcher does the following:

1. Using a combination of the .well-known/nodeinfo and .well-known/host-meta endpoints it determines the host software (https://github.com/nanos/FediFetcher/blob/95b644d4319a8755684f5347ef47ce6b2a38cae1/find_posts.py#L1101)

2. It then uses that info to determine if the host supports the mastodon, misskey, or lemmy API (https://github.com/nanos/FediFetcher/blob/95b644d4319a8755684f5347ef47ce6b2a38cae1/find_posts.py#L1205)

If the server identifies as supporting any of these APIs, FediFetcher fetches comments using the detected API. Otherwise it will not try to fetch comments, because it only supports these three APIs.

So, from my POV the questions are:

1) Does the WordPress AP integration support any of these 3 APIs?

2) Does the WordPress AP integration use either the nodeinfo or host-meta endpoint to identify itself?

If the answer to both of these is ‘yes’, FediFetcher can easily support the WordPress AP integration. Otherwise it gets more complicated.

@pfefferle @troed

LOL. I think that the WordPress AP integration is broken:

https[://]blog.troed[.]se/.well-known/nodeinfo

returns a properly formatted nodeinfo response pointing to

https[://]public-api.wordpress[.]com/wpcom/activitypub-1.0/sites/861438/nodeinfo

But that URL returns a 404, so until that's fixed there is nothing that FediFetcher can do.