Aside from relays and adding elastic search to a mastodon instance does anyone have any other things they do to enhance the user experience? #mastoadmin
"FediFetcher is a tool for Mastodon that automatically fetches missing replies and posts from other fediverse instances, and adds them to your own Mastodon instance."
Between setting up DigitalOcean Spaces [1] for uploaded media and enabling @michael's FediFetcher [2], my experience on a one-person self-hosted Mastodon instance has been greatly improved.
I know it's been a long time since I tagged a new version of FediFetcher, but it's time to do so again:
I just released version 7.0.3. This is mostly a maintenance release fixing a number of bugs, but we also introduce support for the Iceshrimp fork of Misskey.
Please check the release notes for full details including update instructions:
I think this is actually the first release where I haven't contributed any code myself. A huge thank you to the amazing contributors @toadking, @root, @zotan, @jonas, @jaytay, and IhoBas (sorry, I don't know your fedi handle)
@staringatclouds@thejessiekirk Its reasonably straight forward to run your own personal instance from a #RaspberryPi I’ve had this instance running now for ~8 months
Federation can initially be a bit of a battle, you can move over all your followers, using some #Relays will also help. I also have a second account on the server that follows more accounts to help pull in content. Also look at something like #Fedifetcher
I would definitely recommend running your own instance, it gives you the independence to run it how you want. Once setup its not much ongoing effort and the hardware can handle it. Also you don’t need a particularly high speed internet connection. If are still thinking of going ahead , I’m happy to answer questions or point you at the guides I used. #SelfHosted#MastoAdmin
With all the arguing about threads the one thing that actually annoys me is the current status quo, where federation is entirely one-sided: any reply just disappears into a black hole, nor can fediverse servers see replies to posts from threads.
It’s just that one post in total isolation.
I assume the answer is ‘no’ but wanted to ask anyway: does anyone know if threads has (or is planning to have) an API to at least fetch responses so it could be integrated with FediFetcher?
(Edit: I should probably rephrase this slightly: I'm mostly interested in whether you think FediFetcher should honour blanket bans through robots.txt.)
Arguments for are quite obvious imo. But there are a few arguments against as well: For starters I wouldn't consider FediFetcher a bot, as it doesn't really go out and crawl things, nor does it store or process anything.
What do you think?
I would really appreciate if you could leave a comment explaining your decision as well (either here, or on the github issue).
Sorry everyone. Did the rookie mistake of editing the intro text of the poll above 👆 which reset existing votes (what a weird thing to do without any warning!)
The question is: FediFetcher follow blanket bans in the robots.txt?
If you've already voted, would you mind voting agian?
This is VERY bad news for users of small instances like myself.
I do understand the reasoning behind it, and I'm not sure there is a good alternative. But it sure feels a bit like a deja vu from the self hosted email days ...
@christian yep. That Action was the inspiration for #FediFetcher ‘s Action and I’ve run GetMoarFediverse as Action for many months, and can confirm it works well.
I'm very excited to say that #FediFetcher is now on version 7:
The big news here, is that FediFetcher now supports Misskey and its derivatives, including #Firefish and Foundkey. Big thanks to @toadking for making this possible.
This means FediFetcher now supports all of these: Mastodon, Pleroma, Akkoma, Pixelfed, Hometown, Misskey, Firefish (Calckey), Foundkey, and Lemmy.
Go ahead and check out the release notes for all the info:
Every long thread I have ever tried to read on Mastodon has been broken due to missing posts, even when you try to view it on the original instance. What a clustered fuck
@loosenut I'm using a #FediFetcher tool to help alleviate this issue on pagan Plus. There's also combine.social but I've not tried that yet. It has a nice explination though!
I tried #FediFetcher by @michael; it does what #mastodon is supposed to do: Downloads external post #replies & fills in your #instance making it look/act like real social media. Unsuprisingly this hits like a train, populating everything from users' home feeds ad infinitum.
This is FINE for the most part. I'd prefer fetch-on-demand: a user clicks a post & FediFetcher pulls and shows, but likely Mastodon needs to implement that. FediFetcher works, more than I can say of Mastodon. I'll keep it.
Got FediFetcher up and running. This will hopefully put an end to the need to open remote posts on the remote server just to see all replies — an annoying problem when running a small Mastodon server.
Very promising so far, thanks @michael!
@passthejoe#Fedifetcher doesn’t support #Firefish yet. There is also less support for Firefish among 3rd party clients.
On the other hand it has a very customizable interface and by default it doesn’t store remote media locally, which helps with storage.
ThreadResolverWorker ArgumentError: wrong number of arguments (given 3, expected 2)
My hunch is that this is a Mastodon, rather than FediFetcher issue, but before I close it, I wanted to ask users of FediFetcher if you've seen this yourself?
It seems that with the exception of self-replies (threads), replies do not appear in the Local timeline. Is there a server setting that can change this? #MastoAdmin
I can endorse FediFetcher. It does take some cpu which is not usually a problem on single-user or small instance.
Michael - should #Threads or some other mega instance federate will #FediFetcher be likely to overwhelm the instance? If so, would it be possible to block FediFetcher from fetching from a specific instance if users would still wish to follow/be followed/post/reply to that instance?
⚠️ We are planning to release important security fixes for #Mastodon on July 6th, between 13:00 and 15:00 UTC. They will be available for the 4.1, 4.0 and 3.5 versions as well as a nightly release, to make the upgrade as small and painless for everyone as possible. Be ready to upgrade!
I use @michael's #FediFetcher to do this. You can run it as a GitHub action, server, or desktop computer. Basically, set it up and forget about it. It chugs along backfilling new follows/followers, replies to posts, and more.
I'm super happy to announce the release of #FediFetcher v6.0.0.
The headline feature is that FediFetcher now supports pulling in context and missing posts from #Lemmy servers! Thank you so much, @teq for your hard work.
Kleine Mastodon-Server, wie :pnpde_social: pnpde.social, "sehen" häufig nur einen kleinen Ausschnitt des Fediverse, weil eine begrenzte Anzahl von Usern auch nur eine begrenzte Anzahl von Verbindungen zu anderen Servern herstellt. Wir haben eine Reihe von Maßnahmen ergriffen, um mehr Inhalte vorzuhalten, die ich hier vorstelle: