Something’s wrong. I’ve been getting consistent notifications from my system that the scheduled job for #GetMoarFediverse was skipped due to the job still running. Could it be that I followed too many people in the last day? (Less than 5 new people I think). Or the #MastoHost issue with #ovh? 🤔 (and even publishing this post is sloooowww) #mastoAdmin #singleuserinstance

@aaron I have a simple single user instance with #MastoHost. Am happy so far. I underestimated initially, so went with the smallest plan. I had to upgrade to the next plan (USD 9 a month I think?) as i was doing probably too much with #Fedifetcher and #GetMoarFediverse . But since then things are fine based on my (current) usage. I wrote a blog post here https://cdrum.com/2023/06/10/experimenting-with-a-single-user-mastodon-instance-cdrum.social/

#MastoAdmin

It's time for my #introduction post on the new server :)

I'm Gervasio, I'm a runner, an aspiring magician, a father and a software engineer.

I live in #Uruguay and I'm working at a small startup (you can see a beautiful "coming soon" page at sumble.com) and before this I worked at #StackOverflow twice.

I enjoy #csharp, but right now I'm working on #python. I'm after interesting problems more than interesting technologies :)

I came to mastodon multiple times, but this became my home in the end of 2022. I tried to build a community (discovered I don't have the skills to do so) and then settled on a single user instance.

One thing I noticed when I was spinning up my server was that I couldn't discover relevant content, so I built #FakeRelay (an API to import content into a Mastodon instance) and then #GetMoarFediverse (as an example to use FakeRelay).

If you're curious about those, I recommend you first check out #fedibuzz, as it's simpler to run. If you still want to use FakeRelay, hit me up and I can get you started.

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:

https://wiki.pnpde.social/books/tipps-tricks/page/das-fediverse-in-deiner-kleininstanz #MastoAdmin

tl;dr:
🔸 Relay @Tealk
🔸 #GetMoarFediverse @g3rv4
🔸 #FediBuzz Relay @astro­@c3d2.social
🔸 #FediFetcher @michael

Building on this, I moved #GetMoarFediverse over to my Synology. Here’s the quick blog post. https://cdrum.com/2023/06/13/moving-getmoarfediverse-over-to-my-own-infrastructure/?utm_source=cdrum-blog #mastoadmin #synology https://cdrum.social/@cdrum/110529502079656291

@g3rv4 Hi threre, checking out the #FakeRelay + #GetMoarFediverse solution, and wondering if you’re still offering single user instance admins like myself access to your fakerelay.gervas.io service? My instance domain is cdrum.social. Thanks! Really appreciate it! ;-)

@yeri I found this blog post that I’m exploring. Two options - #fedibuzz and #FakeRelay / #GetMoarFediverse - along with #fedifetcher.. Will report back!

@muiiio they don't have to! you can use #FediBuzz (https://relay.fedi.buzz/) for an easy setup or #GetMoarFediverse (https://github.com/g3rv4/GetMoarFediverse) if you want to be more selective :)

I just found out about #FakeRelay and #GetMoarFediverse

https://github.com/g3rv4/FakeRelay
https://github.com/g3rv4/GetMoarFediverse

by @g3rv4 and these could have saved quite some time if I had known about them earlier...

Good news on #GetMoarFedivers! @cw, #GetMoarFediverse now can pull followed tags by using Mastodon's API.

That means it doesn't _need_ to connect to the database for it, making it available for people on hosted environments.

Thanks Chris!

There are some caveats, which is why I'm keeping the db connection alive:

* You need an API key for each user you want to pull followed tags from (this is a limit imposed by the API)
* You need to specify the API keys on the config file (will probably also receive them via env vars in the short term, so that it can be used on the GitHub action)

@jan On mountains.social I use #FakeRelay (https://github.com/g3rv4/FakeRelay) and #GetMoarFediverse (https://github.com/g3rv4/GetMoarFediverse) from @g3rv4. You can specify which hashtags and from which instances you want to inject into your federated timeline. That really works out. My current config can be see here: https://github.com/spiezmaestro/mountains.social_GMFAction/blob/main/config.json

and it's fixed! #GetMoarFediverse 1.0.51 now uses Mastodon's API to fetch hashtagged content

ugh, 4.1.0 is going to break #GetMoarFediverse... I guess this weekend I'll be using Mastodon's API for it

Hm. #GetMoarFediverse has been consistently throwing errors for me this morning.

Full log here: https://github.com/nanos/GMFActionDemo/actions/runs/4131877141/jobs/7139947657 (I think this is public, isn't it?)

@g3rv4, do you have any thoughts or suggestions?

Finally got around to configuring #FakeRelay and #GetMoarFediverse on this instance, the way I had it on my previous instance. Now I automatically get content with hashtags that interest me in my feed again. It is such a lifesaver for small #selfhosted servers. #mastoadmin

Thanks to @g3rv4 and his excellent work on #FakeRelay (https://github.com/g3rv4/FakeRelay) and #GetMoarFediverse (https://github.com/g3rv4/GetMoarFediverse) there is now a way to more specifically pull relevant posts into the federated timeline. The instance admin can define which hashtags from which instances are pulled, thus providing content more relevant to the people on the instance.

3/4

#mastoadmin

@eleder buenas! si, no es un problema... lo único que no podés hacer si usás #GetMoarFediverse es agarrar las tags seguidas por los usuarios automáticamente, pero si lo podés correr como una GitHub Action así no tenés que tener nada en tu infraestructura.

https://github.com/g3rv4/GetMoarFediverse

@deltatux @train huh, #GetMoarFediverse is broken how? I've heard of people using it on Oracle's ARM server.

At some point it was erroring, but I fixed that. I got a repro and verified a fix on Amazon's ARM servers (as I couldn't get past the out of capacity error on OCI)

Can you try again with the ghcr.io/g3rv4/getmoarfediverse:1.0.46-arm64v8 image? (as ghcr.io/g3rv4/getmoarfediverse:latest-arm64v8 could be cached)

I'm happy to see that @astro built #FediBuzz, it's even simpler to use than #FakeRelay and #GetMoarFediverse

You add the relays that follow the #hashtags you want, and that's it.

The only thing I haven't seen is it's source code, but it looks pretty pretty pretty good.

@coffe from my experience, my usage is around 20gb. Using #fakerelay and #getmoarfediverse to get content in. Seems to do a clean out every so often, hasn't gone above about 25gb...