GitHub - poetaster/keypeer.org: This is the repository of the keypeer project website. now contains the sources for the website. Anyone who has some time to elaborate on the skeletal ideas contained here, take a look at about.md ā¦ thanks in advance!
Iām offering this too: internships at our research lab that are related to privacy and security. Feel free to mail me or DM me on the forum. You can have a look at my profile on the university website, for some context. Iād be especially delighted to have someone work on (privacy-related components of) Whisperfish, but anything privacy-related on SailfishOS is a welcome proposal, and we can think together of something.
I think it would make a good project, but it should also fit the research lab, which it would not by a lot in my case 
Iām thinking mostly in Whisperfish context here, but for instance using Tor with context aware sockets for sealed sending would make a great topic, although thatās probably also a masterās thesis.
Iāve stopped using whisperfish. Itās not usable. Sorry to be blunt. As for tor, itās a false sense of security. Given the concentration of nodes here abouts (germany), I consider it to be a fish bowel. Every tor user I accomodate (ie. increase the timeouts on web services because of the lag on the tor network), INCREASES the likelyhood that they generate traffic that makes my hidden service less hidden. Itās not even funny how cat and mouse it is.
I understand. Thereās a reason I still label this as beta. It is not usable if youāre not willing to put time into reporting and debugging some issues. Given the technical debt that we are working through (and catching up on), the complexity of Signal itself (which we are catching up on), and the fact that we have to build our own ecosystem of support libraries (unlike Telegram with TDlib), this is probably one of the more complex applications that are being written for SailfishOS. Weāre closing in on 0.6.0, and I would urge you to take a look again when we reach that point.
I agree on most of what you say here. However, there are very specific use cases where a Tor-style access to a network is useful, and the sealed sender socket is very probably one of them. These are one-shot, anonymous, unidentified sockets that are accessed per-recipient. Mapping those sockets on single-use Tor circuits should quite effectively help to totally hide your endpoint from Signal.
At least, in theory. Part of such an endeavour would be the evaluation in practice, which is something we can actually try out, thanks to Whisperfish.
1 Like
I may do so to help with the engineering. But, since itās in rust, which I abhor, I canāt really help that much. I follow the announcements, but since I bailed, most people have just stopped talking to me, which is quite ok
I gather this is research. In any case, hiding from signal, since they have your phone number (and they still have mine!) is a bit, well, you tell me? Sounds like it serves no purpose for the Signal case? But I can imagine a use case.
In any case, Iām grateful for any academic feedback, on keypeer.org, too Although itās still so rough that itās probably not worth the time.
The purpose is to unlink sender from receiver, also at IP-level. Phone numbers is another topic, and there too I imagine thesis topics and internships
If you ever feel like itās less rough, this looks like something I would love to play with. Feel free to DM me, even without internship intentions 
Iāll polish it up and let you know when itās āup to snuffā, so to speak Thanks!
1 Like
To balance the feedback: I am quite happy with Whisperfish and always looking forward for its improvements. It is usable - at least by a light user
PS: and back to the original topic - EU development grants. Have to give constructive feedback regarding keypeer.org .
3 Likes
Just to bump this because there isnāt much time left for the next application round, Iāve cleaned up the structure of the site some and would ask people to comment on Introduction ( keypeer.org/introduction.md at main Ā· poetaster/keypeer.org Ā· GitHub ) Currently there is a bunch of discussion going on in tickets, but that could be moved to the discussions in the repo. Thanks!
The āweāre finalizing thisā draft of the application to NLnet is currently at: keypeer.org/nl.md at main Ā· poetaster/keypeer.org Ā· GitHub if anyone has time / means to comment. Weāre applying at: NLnet; Apply for a grant under the NGI Zero Entrust Theme call. @hildon I know itās not your interest area, per se, but feedback would be welcome!
1 Like
Hello @poetaster and all members of this project. This looks really fantastic from my point of view. Iāve proposed a PR correcting some typos and asking some questions.
If Iāve time before this evening, Iāll try to read the call also to re-read the proposal with it in mind.
1 Like
So far itās been @rinigus, the Sailmates and myself working on the proposal.But Iāll be very happy to add you!
Well thanks, but youāve done guys, all the job. Iāve simply re-read and corrected some typos. But I wish the best for the initiative !
Reminding me to fix typos albeit humiliating is important Thanks!
Well, later on, I read in the call that Ā« our reviewers donāt care about spelling errors Ā» after all ; D
1 Like
And just to add more stress to my post-employment life (!) https://prototypefund.de/ is opening up the next round for grant proposals next week. Thatās restricted to people living in Germany, I believe.
2 Likes
Apologies, I did not have time to comment a lot on this. I am switching jobs and interviewing takes a lot of time, plus travel. Nonetheless, I skimmed through your proposal and it looked very cool. I hope you get funded! Keep us posted.
No worries! Good luck with the job switch! Iām also unemployed at the moment and trying to use the time constructively!
Since another round of NLnet grant was opened (NGI0), i think it would be nice to gather here some ideas that can be funded. Next deadline is August 1st. In addition, I stumped upon a video where NLnet themself want to support Sailfish (36C3 - NGI Zero: A treasure trove of IT innovation - Invidious - 58:50).
At the Sailmates association we started collecting ideas that could be funded: Issues - boards - Codeberg.org but would be great if others here have additional ideas.
Since one can apply for multiple grants at the same time (NLnet; Frequently Asked (and/or Anticipated) Questions) there is no need to focus only on one topic.
To make it easier for applying (the Sailmates association being able to apply if you donāt wish to do so as an individual) I recommend answering the following questions, just like those bug reports to Jolla:
- project name
- description of the whole project and expected outcomes
- how would the grant budget be used ? (max budget 50kā¬)
- comparison with historical similar efforts
- technical challenges one might face
- ecosystem of the project (how to engage with relevant actors and promote outcomes)
I found an example of an application getting to the second round: #4 - NLNet - December 1st 2022 application (UI/UX) - sustainability - Codeberg.org that we could inspire ourselfs from.
BTW, maybe @hildon can change the title and remove the ādeadlines soonā since itās a cycle and if projects are not funded this time they might get it next time.
3 Likes
Apologies, but I couldnāt figure out how to edit the title. Is this still possible for an old thread?