@dansup love this!

@dansup I'd say if the purpose of verification is trust, it should not be a paid feature. Otherwise it's only possible for people/orgs with enough money.

I can imagine other forms of monetization. More branding/customization features for instance. Or a special "I donated" badge. A "donaters" page where your name is listed. Things like that?

@dansup I'd say if the purpose of verification is trust, it should not be a paid feature. Otherwise it's only possible for people/orgs with enough money.

I can imagine other forms of monetization. More branding/customization features for instance. Or a special "I donated" badge. A "donaters" page where your name is listed. Things like that?

@dansup I said "no" mostly because in a federated context it's going to be impossible to enforce this. If I'm missing a way that would enforce this, I might change my vote to "yes"

@signalapp does that also support markdown formatting? I'm so used to that in apps such as Slack that I _really_ miss it in Signal

@dansup hell yes!

@dansup thank you for all the work you do on Pixelfed!

@dansup ooooh, I would be very interested!

@dansup ugh, me too

@dansup I'd make that the default option but also allow for immediate deletes if people really want it.

@dansup bappy birthday!

@dansup tried that. Unfortunately, I still get the same message

@dansup I am probably thinking too simple, but using something like an adapter pattern could perhaps allow for backwards compatibility at least for a while?

I can really understand new fancy features to break on older servers, but basic functionality such as posting a picture. Purely looking at this as a user, this is not a good experience

@dansup groups is definitely something I'm missing here, but I'm not sure if the Pixelfed platform is the most logical place to add it to be honest

@dansup I really need to finish setting up my own pixelfed server