Thank you for putting all this together!

Potential conflict of interest: I help with [email protected]

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 plan on experimenting with the suggestions posted here. That way I can narrow down where the problem is

The live website works on desktop and mobile. The offline folder works well on desktop, but it has issues on mobile, such as the search bar not working

That would work

I’ll check it out

Thank you, I’ll try those

This looks good, thank you!

I think it’s about IO interrupts?

https://www.geeksforgeeks.org/interrupts-in-8086-microprocessor/

deleted by creator

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

I might be able to set something up with the InstanceAssistant browser extension. It would be nice to have it in the main UI, but this could help temporarily.

I’ll send a PM :)

This is amazing, thank you for reaching out to the dev!

This was on the list of ideas for InstanceAssistant, but I didn’t know where to start. It is great news that it was added to the original extension.

That t-shirt would be cool, but don’t have time to properly test our extension before then

I’m looking forward to December when I’ll have time to work on it. I’ll try to attend some office hours, I didn’t know that was an option

I think the issue here is

they don’t show up under “posts” on your own profile

It makes sense to hide read posts on the main feed, but not when you’re looking at a particular user?

Yep I think the defederation point is the big one which causes the idea to break down. I’ll edit the post to better reflect my thoughts now

That’s a problem everywhere, but I’ve found that people are a lot better on here about downvotes?

On Reddit I’d see comments and questions with no replies and only downvotes. Here you’re a lot more likely to see responses

Thank you!

Hope it helps :)

Look, honestly: if you want Facebook ot Twitter, go back to them.

This post was to talk about the merits/drawbacks of a potential change, and the constructive comments on the post have been helpful for that. Some of the other ‘solutions’ that have been posted here feel even more antithetical to the idea of decentralization (ex. redirecting upvotes, having communities follow other communities) so I was looking for a compromise that would address some of the annoyances without making the site another centralized platform. The intent was to allow users to choose how they want to link cross posts together, rather than having the community (or an app/frontend) make the decision for them. We’ve also been seeing users naturally gravitate to a few instances/communities, so I was looking for ways to redirect some of that traffic back to lesser known spaces.

Regardless, I appreciate the comment. Reading the perspectives on this post helped me see how locking the post completely would cause more issues and annoyances than it would help with. A simple “we are discussing X over on this post, feel free to join” seems like the better compromise.

that’s fair :)

Everyone who’s subscribed to the same communities will see all of each others’ comments.

This still relies on everyone using the same app/front-end.

I guess I’m thinking about how it would be helpful in more general cases. If someone has an issue with a FOSS app, and they ask about it in two small communities, it would be much better to have the troubleshooting discussion in one place rather than have both communities missing part of the context.

Ultimately in your example, the user can still make both posts, this doesn’t change that. It just directs the comments to one post’s comment section rather than having it spread out.

Still it’s good to think about cases where OP tries to abuse the system. Would a good middle ground just be the first implementation then? For OP to link to the post that they want to be the main discussion thread, but people are free to ignore that if they want.

I agree, instance assistant (our extension actually!) handles this, but it would be much better to have it exist natively.

this proposal would give more controls to the bigger communities

what are the concerns that come to mind?

I’d rather just have different communities

All the individual communities would continue to exist as they do right now. When it makes sense for a post to have a deeper discussion, users can lock and redirect accordingly