https://gittr.space/npub1n2ph08n4pqz4d3jk6n2p35p2f4ldhc5g5tu7dhftfpueajf4rpxqfjhzmc/gittr?file=docs here's with the blossom addition
Discussion
nostr:nprofile1qqsf4qmhne6ssp2kcetdf4qc6q4y6lkmu2y2970xm545s7v7ey63snqpz9mhxue69uhkymmnw3ezuumgdacz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqsuamnwvaz7tmwdaejumr0dshs7tcy97 are you worried that supporting so may ways of doing the same thing, adds unnecessary complexity, makes it harder to understand and harder to implement?
Not anylonger but it was certainly a fight. Made a PR on the optional changes back to gitnostr and a repo on snippets with which stuff got better to handle. And serious doku, not the unuseful kind but actually helpful 🐈⬛
If everyone contributes back and new ones still know where to start we' re good 🤗
I'm a bit confused. Are you are saying the extra complexity of having lots of different ways of doing the same thing is OK? And that you made a PR to a project that has only 1 commit posted 2 years ago.
Yes, thats what i am saying. Its about discoverability for me.
See nothing wrong in PRing changes so its up to date. Lost and left repos are a problem when ppl want to contribute.
The result is very reliable & fast so i dont really get the problem here neither with complexity and sharing snippets on that nor PRing progress. Ive contributed to much older code than 2 years before..
Id like to know what's too complex in this. You can just fork it and build upon or just face the complexity.