I’m working on open source projects :)

🔗 Links:

GitHub Reddit

🍪 Get me a cookie:

Go to Ko-fi GitHub Sponsor
  • 8 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle


  • Thank you for putting all this together!

    Potential conflict of interest: I help with !instance_assistant@lemmy.ca

    Having a separate list for extensions would work nicely, although I think it fits to have the extensions listed here. There are few actual browser extensions for Lemmy/Kbin/Mastodon. There are a lot of scripts, and we were working on incorporating the better scripts into the extension for the same reasons you mentioned above. Scripts are harder to manage and review

    My thoughts on the questions.

    1. “last stable version” sounds like a good way to sort it, for readers. It might become cumbersome for you to manage unless you can automate it somehow.
    2. I’m leaning towards flagging or removing out of date apps because of potential security issues. Could you contact devs after a few months to ask if it is being maintained?
    3. A big list of every app would be interesting for data. It isn’t helpful for users, so I agree with keeping them off
    4. I have a donation link. I don’t think it should be included in guides or lists either
    5. I like the formatting, as a reader. Consider if it becomes too cumbersome for you and your team to manage. I’d rather have a list that stays up to date and doesn’t cause headaches for the maintainer






  • I was chatting with a friend, and she mentioned how she tries to at least set up a README, which includes her vision for the project and her plan for the implementation, design, and goals.

    Best case scenario is that the planning helps her complete the project herself. Worst case scenario, someone else can pick up where she left off and use her considerations for the project.

    I’m thinking of doing that for future projects too