ray@lemmy.ml to Open Source@lemmy.mlEnglish · 6 months agoMobilizon flies out of Framasoft's nestjoinmobilizon.orgexternal-linkmessage-square5fedilinkarrow-up139arrow-down12cross-posted to: fediverse@lemmy.world
arrow-up137arrow-down1external-linkMobilizon flies out of Framasoft's nestjoinmobilizon.orgray@lemmy.ml to Open Source@lemmy.mlEnglish · 6 months agomessage-square5fedilinkcross-posted to: fediverse@lemmy.world
minus-squareiagomago@feddit.itlinkfedilinkarrow-up5·6 months agoMhhh. I don’t know how to feel about this: it seems like Mobilizon isn’t getting as much traction as other federated services.
minus-square[moved to hexbear]@lemmy.mllinkfedilinkarrow-up15·6 months agoEvent planning platforms are never going to compete with massive social communication platforms, they’re entirely different ends of the stick. As long as Mobilizon continues to work, that’s all I ask for.
minus-squareNuclearDolphin@lemmy.mllinkfedilinkEnglisharrow-up12·6 months agoI think the ActivityPub sphere needs to transition from “fedi replica of X service” to “Y component that would be useful to existing fedi services”. Event planning is one of them. Simple, encrypted one-to-one DMs is another. Moderation tools is a big one too. Would be a shame if each software has to independently reimplement the same features desired by each flavor of threaded reply service.
Mhhh. I don’t know how to feel about this: it seems like Mobilizon isn’t getting as much traction as other federated services.
Event planning platforms are never going to compete with massive social communication platforms, they’re entirely different ends of the stick.
As long as Mobilizon continues to work, that’s all I ask for.
I think the ActivityPub sphere needs to transition from “fedi replica of X service” to “Y component that would be useful to existing fedi services”.
Event planning is one of them. Simple, encrypted one-to-one DMs is another. Moderation tools is a big one too.
Would be a shame if each software has to independently reimplement the same features desired by each flavor of threaded reply service.