Why not link the source code from the website (or did i miss it?)

Which is not useful if those users are people who try out the platform and then abandon it, or worst bots for state actors.

Right now i don’t see any movement in the amount of donations (patreon, liberapay). so i am not kinda skeptical this will end up being meaningful growth.

They have a explanation here. they claim part of the problem was banning people who are harmless and not homophobes (they show at least one comment ).

Maybe it is better to avoid duplication of effort and contribute to OSGL.

You just need to add a “mature” tag to it and a option to filter by it. contributing to it is easy as far as i can tell.

The website is already linking to google play store and apple store. right now apps that are purely web don’t have a platform to read reviews on . plus neodb lib.reviews are open source although they might not yet be ready for the task yet.

Besides Lemmy mainly gets promoted by word of mouth (eg people recommending it on Reddit)

I doubt that, any data? similarweb shows the top referring site for now is openalternative.co (although at least one of the referring sites mentioned doesn’t seem to make sense for me ).

If people want to review Lemmy communities, it would make more sense to make a Lemmy community for that purpose.

I think people would want to see average ratings. reading a community page means you only read 1-3 reviews and that sample size is too small and potentially biased. you could just run into people who hate a instance for some particular reason (and it’s not hard for me to think of reasons like that).

Two ideas i like:

linking to a bunch of platforms that have reviews of lemmy, fynd does this:

A neodb instance (but maybe another platform would do) where you can read and write reviews about fediverse instances (but that would require at least one volunteer to moderate it).

It costs real world money to keep that data. tbf i don’t think you would find a service that does not delete inactive accounts. iirc when i did a market survey to find a new email address basically all free providers didn’t guarantee keeping your data if the account is free and inactive.

Using custom libraries sounds like a problem that is easy to miss. sure the super diligent developer will be fine but its like saying there is no point in linters because people just don’t read coding guidelines.

Looks like a few services already have a mechanism like i described in place. e.g. Kubernetes throws a “APIRemovedInNextReleaseInUse”.

Allow people who fund the platform vote on features (that are pre approved ). who contribute more get more in return.

“time well spent”. and maximizing the “average quality of content”. maybe by allowing custom feeds. or feeds that are based only on the votes of trusted users. with governance models supporting how those feeds are managed like how KDE and GNOME nonprofits are managed. maybe vote on best post/comment of the day/week/year/decade with leaderboards for that.

Linus law of trail and error. allow people to easily extend the software .with plugins and ideally a store with reviews for addons like in firefox and chrome. making experimentation easier and safer (without risking adding a bad feature to all users of the software). vote on features implemented rating for example how satisfied you are on a scale of one to ten.

information over speculations . use A/B testing to see what works in practice. maybe use “counted statement” for example “this is useful” or “this is important” beyond lemmy and reddit upvotes and downvotes.

Right now a life changing post from world class expert and a funny cat picture with someone who spend too much time online are treated the same by the software. this should somehow change.

We have lemmy apps that still aren’t supporting API changes added over a year ago. We even had one such case last week.

That sounds like something could be improve. is there some sort of warning mechanism in place?

Say when using a lemmy client. the client either specifies its a production build. or if its not then the lemmy server reports where deprecated API’s are used.

Not sure that is the correct approach. break frequently break often seems better (that’s what PHP and java seem to do as far as i can tell, unlike python 3 which caused a lot of drama).

notify a API is deprecated. give some time for users to update to the new API (1 year?) and then remove it.

Of course after version 1.0 there might be less breakage so it won’t be a be problem.

Why not provide a option to use an a desktop app?. maybe also add a flatpak. self hosting seems kinda complicated and i am not sure what are the benefits of that.

Also a demo instance would be nice.

Probably this. honestly after googling it does not seem open source.

This isn’t what i had in mind. i meant more like changing the line to something like:

We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, donating money and helping find and fix bugs.

With “donating money” maybe replaced with “funding”.

I think liberapay has that feature.

We’d like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs

I feel like people giving their hard earned money for lemmy also should get a show of appreciation.

If there is interest then we can add more filters, for flair/tag, etc. But from the server logs it doesn’t seem like many people use RSS.

I feel like sometimes just usage data does not capture what power users do which is important. they might be the one who contribute stuff like high quality content, more money and code to the project.

Maybe there should be something like an invite based group for the people who contribute the best content for piefed or just people who contribute to the patreon (i think this can be set up automatically).

i myself use RSS but not for feeds of fediverse software . i did contribute some feedback to lemmy which ended up being accepted (the ability to block an instance, a few RES features which should appear on lemmy 1.0).

Why is it not a part of the project itself if you don’t mind me asking? i would imagine plugins are for the more opinionated or experimental features.

Honestly if you are interested in working on this domain. something like “amazon for red hats” sounds like a better idea. where you are able to subscribe to a organisation and he can gather feedback on what work people want the most (features and bug fixes). but only people paying money are allowed to vote. with data on which organisation are growing in their revenue and number of subscribers which is another indicator (like liberapay view income history section). and of course ability to write reviews and give ratings but again only for paying customers so there will be no review bombing.