I'd like to fetch their content. The last time I tested bird.makeup, since I followed unpopular people, it didn't fetch their statuses (understandably, they can't burn the api credits for these accounts).
Is anybody else running it for their instance? the docs seems sparse. I'm thinking it won't even be accessible to the outer world (I'd just add an entry to the server’s host file).
How do you balance between a wide range of content and massive following (I'm at > 800) and handpicked timeline?
I know there are lists and there are relayServers (I'm operating a #GoToSocial instancen), but I still miss a lot of posts in the flood called timeline.
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)
I think of selfhosting a single user instance with Hetzner. What VPS do you think would be sufficient/fitting? Please keep in mind, that I don't want to spend that much money on it.
Oh and I will probably run glitch-soc...
I've noticed a lot of chatter about setting up Elasticsearch for Mastodon 4.2's new full text search over the last few days, including what hardware is required, how difficult is it, etc.
So I thought I’d write down my experience, including the hardware I'm running Elasticsearch on for my single user instance:
This means nothing for you as a current user because it is deployed already and running 😅
For new users, this means that CSP restrictions will no longer prevent you from authenticating the application.
It also made the signup page significantly slimmer (the mastodon client library is no longer embedded into the page) since the verification process is now done server side.
As always, the privacy policy is "we don't read any of your message content, we don't store any of your messages anywhere" and if you de-authorize the app we forget about you completely.
Latest release candidate of @gotosocial finally adds federated #hashtags! This brings the number of missing "must-have" items on my wish list down to just one:
There are a few other things I'd like to have working before switching my primary Fediverse account from @KelsonV to a properly-set-up #GoToSocial#singleUserInstance, but that's the only big one left.
Follow moving accounts to their new location. (This is another big one.)
Mark account as moved
Polls
Fix Federation with Takahē (not sure how much is on which side at this point). I need to check in on what @activitypubtestsuite has been doing!
Federation with Lemmy (but that's on Lemmy to implement signed fetches)
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 ...
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:
In order to make it cheap, I chose an ARM machine with #IPv6 only, and it did throw me a few curve balls... but hey, it only costs €3.29/mo to run!
I wrote about it, mostly so that the next time I have to do it again I have it documented, but if it's helpful to someone else that would be awesome :)
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.
@jay Three things you can do to enliven your small-numbers instance (we do all of these):
1: Set up a "Librarian" account that follows others of general interest whether you in particular care about them or not. Our librarian follows a lot of news, art, and science, but use it with particular abandon to fill out your Federated feed.
2: Check said Federated feed, have the Librarian follow people boosted and lively.
3: Use the relay functionality to relay hashtags via the hashtag relay server:
Posted another blog post about getting #Bookwyrm ( @bookwyrm ) installed on my local Synology NAS at home. I used Cloudfare tunnels to bypass the port forwarding issue, and to make the SSL certificates easier to deal with. I’m still finding my way around Bookwyrm, but feel free to find me at https://books.cdrum.social/user/cdrum
This release brings no new features, but simplifies and unifies configuration of it: Instead of a large list of command line flags / environment variables, FediFetcher is now configured using a JSON file.
You don't need to update to this version immediately, but if you are running FediFetcher as a GitHub Action, you'll need to update and create a JSON file with options eventually, as configuration through Environment variables will no longer be possible going forward.
THIS IS A BREAKING CHANGE, so please read the release notes for detailed instructions, and let me know if you have any questions.
FediFetcher is a simple Python script that can help you pull missing responses from other #Fediverse instances into your own #Mastodon instance. It can also backfill profiles of new followers and followings.
It can be run as cron job, container, or even a GitHub action, meaning you don't need any infrastructure at all.