If anyone knows #Go and is looking for a project to help out with, Go-based #Signal protocol implementation library and a native #SailfishOS Signal client using it are in dire need of love:
Yes, I also prefer truly decentralized protocols, but Signal is where it's at currently with a lot of people, and it's way better than other popular options... So, we need independent clients.
@pettter well they insist that unofficial clients do not use the word "Signal" in the name. Other than that, Whisperfish seems to work fine (modulo bugs and missing functionality) so far.
@strypey yeah, I am more interested in Briar (time to go full p2p decentralized).
I need Signal for work. It took 3 years to move 200+ journalists to Signal, I don't have 3 more years to now move them to Wire, unless Signal really fscks up big time.
@strypey ah no, didn't know about Jami. Thanks! Will check it out.
> that's no reason to encourage people to do unpaid work for them.
Moxie fights the idea of independent clients, so this is far from working *for them*. In fact, it seems to be the opposite.
> Why support Sailfish?
Because it's the only usable mobile OS that is so open and comes with actual support.
> Did you read OP of the first link I posted?
Yes, and I agree with most of it. But I need to communicate with people where my choices are Signal or Viber/Telegram/Whatsapp.
@strypey oh, and I love that this privacytoolsIO thing is hosted on GitHub.
We all make compromises.
For example, subscriptions to ticket trackers could be sold
You wanna open a ticket ?
You need to buy a 10$ annual subscription
Reading and triaging bugs is work and it should be payed
If that makes you outraged you are probably forgetting the "free" is intended as in freedom, not as in beer
I agree that estimates are weak, but I can think of two possibilities that might also work: one is the devs set a price, and the other that the users set a bounty. Each has pluses and minuses. The big plus is "all within the same environment, not a separate site".
Software production is craftsmanship
What's needed to achieve targets is not measurable.
And it's not a given that users know what they want, or that they share the vision with the devs
I wouldn't overcomplicate because then implementation gets more difficult and you run into overlaps with uman issues (differences in vision, motivation)
You risk this thing to fail and you couldn't even point precisely to a reason why
I'd keep it simple
The community needs to produce some more revenue right now without the need to implement new processes whose implementation would eat up the new revenue produced
I'd try to keep this more down to hearth
@AbbieNormal @bhaugen @strypey @rysiek @sullybiker
I think it's already very hard to get people to report bugs, as opposed to just giving up and coming to a conclusion that the piece of software is shit and will never work.
It's even harder to get quality bug reports.
Putting up a paywall in front of that will guarantee that more people will give up before filing a bug report.
But it will also guarantee that the reactions will be of a higher quality
Repeating over and over that the problem of floss is money without acting won't help
Gamifying the software production process is a silly idea
The problem doesn't need more tech
It needs people to step out of their comfort zones
Now that I think of it, it really depends on what kinda project you're developing and your target audience.
A lot of projects would benefit more from making it easy for users to become contributors and help fix the issues they encounter.
But then for a project that targets mostly non-technical people, money probably would be more effective.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!