There's also the fact that, in this special case, there's the testing between-systems that is very time-consuming and requires a deep understanding of the various system parts and the underlying protocol and it's various implementations and use cases.
I seem to be sort of sinking into that Nostr System Tester superrole out of frustration and because I'm used to testing large, complex, modular systems, which is what Nostr is.
I can produce results, but they are for tests nobody ordered because they span the entire network.
It's like I've tested the Internet.
If I test the sensor interactions within a car or the compliance of the software systems for a large logistics chain, then I have a clear customer.
Not just for payment, but also to help define the scope of the test and to accept and review the test result. I never even even know who to address, here, and they act like they're offering me customer support.
Haha, bunch of ungrateful b'stards. They should cherish you!
You are very important to the existence of the protocol.
The problem with not knowing who to turn to is a classic. Every team will first point to the other, because it saves them the trouble. Only when you can prove without a doubt that their system is causing the issue, will they submit and try to do something about it.
An ungrateful role to say the least. And you shouldn't be doing it without some kind of compensation. Either financial or in (high) recognition!
Often, they mute me or tell me "user error". 😂
Yeah, I need to stop doing this and focus more on my own project. I'll just go batty, otherwise. Screaming into the void, all day.
Sad, very sad that you are treated in this way. In stead of cherished and thanked for every issue you raise.
Stupid and short-sighted of them. They will get it back eventually, either by complaints of users or worse, users rejecting their garbage software. Either way will be painful.
You should definitely not use your precious time if they are treating you like that. Move on and spend your time on the tings you like.
I guess it's just me being my nerdy self, churning out a product nobody wants, for weeks, without taking a hint. 😂
Took me a while to get that nobody actually cares if their stuff works well or interoperates. I thought they didn't have the information, but they don't have the motivation.
There is simply no Nostr incentive structure for "Things Working".
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m
Do you know if there is any incentive for hard working people like this girl who sacrifices her time and effort without any financial incentive or recognition?
Software testing is an ungrateful work and there is no focus on quality and interoperability. How can we solve this?
Please read previous posts in this thread for more info and let us know what you think.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Interface testing is very annoying as the documentation is almost always lacking. However once the documents are complete it shouldn't be much too complicated, more like time consuming.
End-to-end testing spanning multiple systems and multiple interfaces is whole other ballgame. It's not just complex, but it's very intensive as you need to know where the issue has arisen. It's a lot of communication and hustle.
System tests and even interface tests can be carried out by developers. It's just that they're not too keen on doing it. And it should never be done by the people that built the damn thing. Out of obvious reasons.
I suspect some developers are even their own PR reviewers. 🙈
Thread collapsed
Thread collapsed
Also, the idea that we can use multiple clients is a good one. Redundancy promotes independence.
Constantly breaking things, and failing so miserably in coordinating on basic functionality, so that users need to toggle between three similar clients, or cling desperately to the worst offender, just to send a note or read threads... That is unacceptable.
Thread collapsed
