It’s still early so I think migrations are still possible. So any evaluation regarding this (Lemmy) and Kbin? It looks like both are similar.
@[email protected] Regardless, it doesn’t really matter.
Are you guys from the /r/philippines subreddit and trying to find a new home? Or, you just want to start a new #Philippines community in the #fediverse network?
If it is the latter, then we already have well-established communities like @[email protected] @[email protected] @[email protected] _
So, keeping @[email protected] is perfectly fine, you don’t really have to move. The more communities we have in other instances, the better. Redundancy and continuity.
It means that, if one community hosted in a different instance goes offline (temporarily or permanently), the other Philippines communities in other instances are still intact. Those affected can move to the other existing communities. It happened before (an instance went offline, temporarily) and it almost happened again (permanently).
However, if you are the /r/philippines subreddit, since you have an existing community you are migrating over to the fediverse, then yes, choose the instance you want to be hosted on. One where you can get a guarantee that they will do everything they can to stay online for the next 20 years. Otherwise, you risk breaking the community if the instance suddenly goes offline.
Does that make any sense? _
For me, strictly about features, go for #Kbin. _
test - posting from kbin.social
Kbin is one of the Reddit alternatives I set up during the weekend. Gave up because of the constant outages and Cloudfare. Feel free to check it out anyway if you want: https://kbin.social/m/Pilipinas.
There are other #Kbin instances. _
di ko pa masyado gamay yun fediverse, so if someone can explain why this is happening
fedia.io
is an instance of kbin and I can accessphilippines lemmy.world
instance from fedia - here is the link:https://fedia.io/m/[email protected]/active
pero I cannot do the same from the main kbin instance (
kbin.social
)https://kbin.social/m/[email protected]/active - error 404
EDIT: looks like kbin needs to “know” the instance before it can access it, but takes a while para ma-discover nya (i think searching the community will initiate the process). so di na sya mag-404 pag click yun link above
The #Kbin flagship server, kbin.social, is currently being hammered by bots and thus, the Kbin developer enabled CF features to combat those bots, which unfortunately is affecting federation requests.