Hi, everybody. I just switched my Mastodon instance from `social.kalvin.my` to `mastodon.kalvin.my`, reinstalled Mastodon because of federation issues and performance with the `threads.net` Fediverse server. I hope this is my last personal single-user Mastodon instance.
#Mastodon #Fediverse #Threads #Federation #SelfHosting #KalvinMy #SingleUserInstance #OpenWeb #Decentralization #TechLife #PersonalDomain #DigitalIdentity #AdminLife
aaand I'm out of the #singleuserinstance world. It was fun at the beginning, and it became just toil as my usage of mastodon diminished.
I'm moving back to @g3rv4@hachyderm.io
Does anyone know a client compatible with #GoToSocial that would allow me to hide boosts from specific instances or users? I am using https://relay.fedi.buzz to get posts from a few instances, and even though it is good, it floods my boost timeline, obscuring boosts from people I actually follow 😔
#singleuserinstance #help #feditips
What are some general advises for self-hosted instances? E.g. how to federate with more instances, how to find people, etc? I know about https://relay.fedi.buzz and I actually use it to follow some hashtags, but maybe there are more advises?
#selfhosting #gotosocial #singleuserinstance #federation
Federation test 2. Anyone see this (again)?
#FederationTest #SelfHosted #FediAdmin #SingleUserInstance
A reminder for all GitHub Action users of FediFetcher:
In about 4 weeks time the GitHub Action will likely cease working, unless you perform a manual update at least once every 60 days.
If you are currently running FediFetcher via GitHub Actions, please consider migrating to another option by 20th June:
https://github.com/nanos/FediFetcher/wiki/Migrating-From-GitHub-Actions
Let me know if you have any questions or need help!
Calling all FediFetcher users who are currently running FediFetcher as a GitHub Action:
Following recent changes by GitHub, and a poll, which showed that only a single respondent actually relies on GitHub Actions without any alternative way of running FediFetcher, GitHub Action support for FediFetcher has been deprecated.
If you are currently running FediFetcher as a GitHub Action, please refer to our new guide on migrating FediFetcher from GitHub Actions:
https://github.com/nanos/FediFetcher/wiki/Migrating-From-GitHub-Actions
You should have until 20th June to perform the migration, but if you don't migrate before then, FediFetcher will likely cease working for you shortly after.
If you have any questions, please free to open an issue on GitHub, or reply to this post.
And if you are that one person who doesn't have an alternative way of running FediFetcher: Please get in touch! I'd love to help you if I can.
Sorry to spam y’all, but if you are using FediFetcher and running it as GitHub Action, I’d really appreciate it if you could vote in this poll:
https://mstdn.thms.uk/@michael/114420962728564499
Thanks!
Every time I see a defederation notice, I’m glad to run my own little instance.
What a mess for users to be forced to be soldiers at childish wars between admins.
It turns out that the issue wasn’t ES using excessive RAM, but rather the off heap memory growing from other processes. When the total RAM exceeded that available on the VPS, ES was killed.
Setting -Xmx2048m seems to result in a stable configuration with ES happily humming away.
• Set ES_HOST=https://localhost in .env.production
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance, which has 8GB RAM. So I I initial set -Xmx3g, but ES kept failing with exit code 137 (excessive memory consumption). I successively increased -Xmx to 4g, 5g, 6g, but with no luck.
After checking the logs, the heap size was not growing and the cap was being enforced properly.
For those interested, setting up #ElasticSearch was fairly straightforward. I mostly followed the official instructions at https://docs.joinmastodon.org/admin/elasticsearch/, with two minor modifications:
1. I installed OpenJDK 21 (latest version in the Ubuntu repository)
2. I installed ElasticSearch 8.
Two things tripped me up:
(a) ES v8 requires TLS by default, even when binding only to localhost. This means that:
• When using curl, you have to use --cacert to specify the path to the self-signed certificate generated by ES & prepend localhost with https://
Curiosity got the better of me and I ended up rescaling* my server and installing ElasticSearch. Let’s see how much I use it.
—
* FYI 2 vCPU & 4GB isn’t anywhere near enough for a #SingleUserInstance of #mastodon + #ElasticSearch.
https://colquitt.xyz/@daniel/113975100843242921
❓Some questions for those of you on a #mastodon instance with full-text search enabled:
1. How often do you use it?
2. What do you use it for?
3. Does it offer something above being able to search for hashtags?
I don’t have it enabled at the moment, but I’m suffering from #FOMO. However, I’d have to beef up the VPS for my #singleuserinstance to enable full-text search and I’m not sure it’s worth it?
🚀 Boost for reach, please!
I’ve just released version 7.1.13 of FediFetcher.
This is a pretty minor release with mostly quality of life improvements. Full details are available on the release page:
https://github.com/nanos/FediFetcher/releases/tag/v7.1.13
Huge thanks to itspluxstahre, @ben, and Sorixelle for your contributions to FediFetcher!
Service-Hinweis: Durch ein manuelles optimize table der Tabellen storage, contacts, apcontacts, post-content, item-uri, post-user, post-tag, post-searchindex, post-media, inbox-status, post-thread-user und contact-relation (das waren die speicherintensivsten) ist die Datenbank meiner Friendica-Instanz soeben auf 2/3 ihrer vorherigen Größe zusammengeschrumpft.
Service-Hinweis 2: Tabellennamen mit Bindestrich müssen in der MySQL-Konsole in Backticks stehen (z. B. `post-user`).
I've just released FediFetcher 7.1.7.
This version adds an instance-blocklist option, so you can completely block FediFetcher from even attempting to connect to bad instance.
It also contains some performance improvements, so definitely worth getting this one.
Full changelog and update instructions are on the release page:
I've just pressed the release button on FediFetcher 7.1.6.
This version brings support for Iceshrimpt.NET, and the ability to configure FediFetcher via environment variables.
https://github.com/nanos/FediFetcher/releases/tag/v7.1.6
Massive thanks to all the contributors! This is another release where almost all changes are contributed by the community, which is amazing to see! 💪
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:
