what if the note just shows:
💬 3
and maybe like zaps you need to expand to load this in sometimes
what if the note just shows:
💬 3
and maybe like zaps you need to expand to load this in sometimes
Added to Damus github https://github.com/damus-io/damus/issues/744
not sure we need to document ideas proposed by jb over there. Not so sure he uses git issues at all. We eventually want to get off GitHub. I find seeking a contributing dev who previously pr’d the relevant part of the client and offering considerate suggestions to them directly, maybe even attempt to pr yourself or at least reference the part of the code for them, on nostr works best.
Will has only so much capacity, and has to choose what he works on, and by consequence what he does not work on.
For the things he chooses not to work on, there is a team of great devs that can pick up well documented tickets that are known by Will, and not necessarily known by all devs in full.
Where I know a dev has a particular interest in a topic I will directly tag them, so they consider a ticket.
Yes, agree getting off corporate github is the way. This is a different question than documenting issues with that tool that Will and devteam all use today.
just sharing my experience creating issues on GitHub compared to just interacting here. I'll submit pr’s if they are simple enough for my skill level, but communicating here has been more productive for issues for me. 💁♀️
Some of us are not anointed with the skills of devs (me) 😅. I appreciate you and others who can PR the technical work.
I agree with you that I’ve found tagging here helps with bringing up an issue to a dev’s attention. Combined with documenting elsewhere (currently github) in detail works best for me.
Let me know if you have a particular area of interest and I can tag you here if there’s related issues I know of 🙏
I’m not really a dev either. A plain English project I worked on recently was rewriting the getting started section of git. It’s not perfect, would love you input on this or expand it.
easier to view the changes rendered on my fork than the raw markup in the pr https://github.com/olheadinternet/damus
My bad, That link goes to the master, have to change the branch to readme_2_22_23
A few comments:
1. Change “by hard pressing a note”
To “by tapping on three dots in top right of the note”
Long tap is deprecated in favor of ellipsis menu (three dots in top right of note)
2. Above also reflects on long pressing in Share (Quote) Note
3. Add description of long tapping zap capability
4. Add example wallets that support NIP-57: e.g. wallet of satoshi + hyperlink https://www.walletofsatoshi.com/