Misskey turns their off by default (you can easily turn it on within settings) & Mastodon requires you to implement the #ElasticSearch code on your instance. I use search on both of my solo instances.
Misskey does not have an official app, but #MissRirica replicates most (if not all) of the options on the web interface (something most official apps on other platforms can not do yet).
@darnell@atomicpoet The search one was a mistake (fixed), but the app column is specifically for first party apps. Also, I feel like I've talked to you already about this, but MissRirica does not replicate anything. It's a recompiled version of the web interface for mobile using Capacitor.
You can ask the admin of the Mastodon instance to install it as it is very useful. I wish it was enabled by default but I think it is intentionally left out.
@darnell@DuncanWatson@atomicpoet Elastic is not something you casually enable. It's very powerful but you need to be intentional about sharding, retention, etc. Very easy to quickly fill up your storage and take your instance down if you don't.
@darnell@DuncanWatson@atomicpoet It is also the case for Misskey and Calckey. That's nothing to do with the platforms, but elastic is elastic, no matter what is connecting to it. I saw at least one Calckey post recently where an instance went down due to Elastic.
@darnell@DuncanWatson@atomicpoet To be clear, I'm not saying you can't or shouldn't do it, but it's not a trivial amount of resources for storage, IO, and tuning. It's not a simple "just run another container" scenario.
@atomicpoet It's the one instance listed that seemed the best fit. Migrating might be dead easy but still some level of mental overhead. Maybe I'll give the HermHerm instace a go.
Add comment