May 13 17:45 [raw]
Hi. Anything new coming up in the new version? something that hasnt been on bitmessage before..
May 13 21:18 [raw]
May 14 04:50 [raw]
https://github.com/Bitmessage/PyBitmessage/pulls is the place to look. Click the "xxx Closed" and "xxx Open" links to see what has changed recently and what changes are coming up next. TL;DR it seems that the last couple of months have been focused mainly on bug fixes, code quality and testing, which is normal in the wake of the eval bug. However, there are some interesting proposals in the pipeline, including some extensions of the existing API, which should help the ecosystem grow horizontally as well as vertically. Personally I am most excited about the progress in code quality. Don't care that much about "new" features; if the foundation is solid, new features can be built on top of it. And the foundation is indeed getting stronger, so the future is looking good. So yeah, "probably nothing" too visible, but still a few things to look forward to.
May 14 07:48 [raw]
Yes, that's true, priority focus on code quality and bugs. In the background a lot of work has been done on the development infrastructure. There are also some collaboration being discussed, and business strategies being evaluated, but I can't publicly disclose anything, except one thing. There is a good chance there will be a professional security audit of the project. As you can see I now do only very little development (except from merging PRs) and shifted into management and infrastructure (as I can't trust anyone with infrastructure at the moment). Peter Surda Bitmessage core developer
May 14 07:50 [raw]
I have heard of audit etc.. But what is audit actuially? is it some kind of review of the Bitmessage to let users know if its good,if its better than other chats etc?
May 14 07:59 [raw]
Well, the audit is primarily internal. It would be pretty comprehensive from what I understand, from policies, procedures, design to code. It's not really an end-user point of view. Peter Surda Bitmessage core developer
May 14 08:33 [raw]
Maybe it's just me, but that sounds slightly ominous :) Stay safe out there, Peter. We've had enough of the Worf effect in this sector to know how the monster works. (the Worf effect for the uninitiated: http://tvtropes.org/pmwiki/pmwiki.php/Main/TheWorfEffect )
May 14 10:26 [raw]
> There is a good chance there will be a professional security audit of the project. noyce, maytee.
[chan] Good Jokes
May 14 10:42 [raw]
Worf Effect: A Klingon is an interstellar dingleberry; an extraterrestrial bodagget.
May 14 11:03 [raw]
Not sure why ominous. I need to know what I/we are doing wrong. And since I'll probably be paying for a significant proportion of it, not sure why I need to "stay safe". That's what it's for, to find out what is safe. I used to work in companies before where we recruited another company to audit the procedures and documentation (e.g. PCI-DSS), I don't see anything unusual about it. This one will probably be more thorough, which is good. We (me and the developers I hired) are increasingly using DevOps for the process, I read studies which indicated that this is better for security as well. Ideally I'd like to have the whole release process automated, with binaries being available after each commit (or at least daily) and releases being triggered only by creating a new release on github, without manual intervention (it will check that the tag is GPG signed, which I do anyway). The build environment is already isolated from development environment, I have to stick a smart card into my workstation/laptop to be able to login to it at all, and I'll receive a notification on my phone upon any login. Peter Surda Bitmessage core developer
May 14 11:29 [raw]
Never mind, it's probably just me. Since you didn't disclose much of your plans yet, I made some automatic (and probably incorrect) assumptions. You mentioned a monetization strategy, which usually means registering with the political authorities of your land, which means you'll be facing the monster head-on, and we know how this ends. That's the ominous component. *Slightly* ominous. :) Again, probably never mind. No concerns whatsoever with your technical setup, you seem perfectly competent at what you're doing. More please.
May 14 12:00 [raw]
Well as for monetisation I don't plan doing anything strange, there probably will be some sort of extra service that you can pay for, just like mailchuck accounts are available for payment. I did get some inputs and have a couple of ideas on my own. There still needs to be some analysis not only from the business side but also legal, regulatory and technical perspectives. But given that there are so many directions available I'm sure something will work out. Peter Surda Bitmessage core developer
May 14 12:19 [raw]
All, in case you missed the announcement, have a look here: https://twitter.com/seecurity/status/995906576170053633 Until further announcements, it's safest to turn off any automatic PGP processing on your systems.
May 14 12:42 [raw]
Keep in mind though: in order to make a plausible claim of peaceful civil disobedience, you absolutely need to disconnect the monetary/material component first. Breaking laws for profit is usually a slam dunk case for any "public prosecutor". See https://motherboard.vice.com/en_us/article/4xknyq/dutch-cops-bust-another-pgp-blackberry-company-for-alleged-money-laundering and other similar cases in recent history. It's a bit of a minefield to navigate.
May 14 13:09 [raw]
So someone is steering Peter into a trap?
May 14 23:26 [raw]
If I had money to burn I would do something similar--set up a few servers and offer free services people need and make it so secure that I couldn't even hack myself ;)
May 15 04:50 [raw]
> automated https://nixos.org/hydra/ hydra got u covered fam
May 15 15:52 [raw]
>audit >infrastructure >business >legal Good way to kill a project.
May 15 16:05 [raw]
Bitmessage is the newest victim of "Project Orchestra": http://www.draketo.de/english/freenet/de-orchestrating-phk
May 15 17:14 [raw]
That's the point.
May 16 06:47 [raw]
I don't give a fuck about disruption, I have my own vision and I'll see it through. Trolls can fuck off. Peter Surda Bitmessage core developer
May 16 06:56 [raw]
Wow... I'm just gonna say it. https://www.youtube.com/watch?v=_uMEE7eaaUA
May 16 11:22 [raw]
Hello, Peter! From your kind words I can see you joined Crypto-Anarchist community. When do you plan to perform first anal rapes on government agents? Best wishes, Your Fan P.S. Jokes aside, your project really starts to derail. Exfiltration of your infrastructure was not a cyber-attack, it was PSYOP-attack to influence your decisions. With deep regret I see this attack succeeded. Now we have two "Crypto-Anarchists" and no chance for secure communication. RIP Bitmessage.
May 16 19:08 [raw]
My Little Pony 💜 Care Bears 💜 Strawberry Shortcake & Friends 💜 Smurfs 💜 Remember happy tales. Worry not about the guy under the bridge.
May 16 19:33 [raw]
Shut yer fuckin' pie hole.
May 17 00:26 [raw]
Dear Fan, We have changed our strategy. We are no longer anally raping feds. We've decided to shift gears and implement a policy of making sweet love to our fans. Feds have been in short supply lately so I'm glad you've stepped up to the task and volunteered. Seter Purda Bitmessage Kore Duhvelopr
May 17 07:37 [raw]
Nobody cares what you think. Just deactivate your account. No one likes your posts, and you’re a waste of everyone’s time.
May 17 08:03 [raw]
what's the purpose of this blather? could you at least troll Peter on his private address so we don't have to read your FUD about bitmessage being derailed? None of us believes you any more than he would.
May 17 08:03 [raw]
Of course you only care what you think. The "Dear Fan" response is appropriate reply to a "psyops paranoia" troll. We all know that troll needs lovin'.
May 17 12:08 [raw]
Don't touch him, he's funny.
May 17 18:41 [raw]
May 21 02:17 [raw]
|minimum difficulty for chans||May 25 07:39||7|
|YOU WANNA HIRE A LEGIT HACKER?????||May 25 07:08||2|
|BM-2cWkFSxB4cyeNVr99tgJdkMA2nfivbXLiH||May 25 07:07||2|
|ein kleines pyBM Nebenproblem in KDE LiquidShell||May 24 18:14||1|
|PyBitmessage 0.6.3.2 blacklist whitelist||May 24 06:29||6|
|Test DML||May 24 02:18||1|
|Now, following my own advice, adding channel bitmessage and general to the blacklist||May 23 15:50||9|
|hyperboria node [fc5b:acf7:9762:439c:394d:02bb:d603:05de]:8444||May 23 01:34||3|
|Feature request: delete all messages from user||May 22 10:46||2|
|(no subject)||May 22 06:46||7|
|Github Wiki complaint||May 21 08:49||12|
|EFAIL?!||May 21 08:25||26|
|ERROR - Error Processing||May 21 08:25||3|
|Curious||May 21 02:17||32|
|Is bitmessage within whonix bad?||May 20 21:24||14|
|Duplicate messages||May 20 21:08||1|
|Download of Windows binary from Bitmessage.org||May 20 07:25||3|
|How to create a "send only" bitmessage address||May 20 04:35||1|
|/join #bitmessage on eris.us.ircnet.net :6667||May 19 21:46||3|
|hey - why not make pyBM as shitty as "Signal-App" by Marlinspike ?||May 19 20:30||7|
|use Claws mail-App with pyBM and python||May 19 20:28||5|
|A question||May 18 23:24||2|
|A Few Bitmessage Internals for New Users||May 18 23:08||5|
|May 18 17:33||1|
|Ideas for countering trolls and spam||May 18 12:54||98|
|DARKNET DIRECTORY ASSISTANCE||May 18 02:25||1|
|Broadcast messages||May 17 23:24||24|
|2018 : Der junge Karl Marx -- youtube.com/watch?v=AbM76KUm4IM -- 2 hours "Le Jeune Karl Marx"||May 17 20:24||1|
|Signal-App is complete shit||May 17 20:24||13|
|May 17 19:49||2|
|OTR interception||May 17 18:00||3|
|auto renew one's canary using broadcast or [chan] ?||May 17 10:51||1|
|latest in the spy world||May 16 14:14||3|
|Curious -- GUIfied pyBM-CLI||May 16 13:47||1|
|efail vulns||May 16 13:21||1|
|how does the namecoin feature work?||May 16 07:24||3|
|Email campaign to promote Bitmessage?||May 15 18:09||1|
|NSA doesn't joke, folks||May 14 23:26||2|
|Beaker||May 14 19:27||1|
|Bitmessage Bug - Re: Now, following my own advice, adding channel bitmessage and general to the blacklist||May 14 16:21||3|
|Ideas for countering trolls and spam - technology.||May 14 16:21||9|
|BITMESSAGE||May 14 14:58||2|
|BM in firejail||May 14 14:24||1|
|Team Revenge||May 14 09:54||1|
|What are these messages?||May 13 07:57||8|
|Bitmessage Bug?||May 10 19:59||1|
|TOR -> VPN -> TOR||May 10 14:57||2|
|Bitmessage on Raspi||May 10 09:32||2|
|Bloom Filter for Routing||May 10 09:04||1|
|Alternative treatment of Bitmessage addresses for use as public channels||May 9 16:12||4|
|deterministic passphrases||May 8 16:54||21|
|nothing wrong with suicide these days||May 8 10:30||2|
|What's Peter Todd's public key?||May 8 10:27||7|
|BMinstallMenu - easy download + run Bitmessage from py source in one single menu||May 8 08:46||1|
|BMinstallMenu - easy download + run Bitmessage from py source in one single menu||May 7 18:38||2|
|Why there are so many alternative Bitmessage implementations?||May 7 18:31||14|
|modding pyBM||May 7 18:17||4|
|bm hidden service settings||May 7 10:48||1|
|bitmessage feature proposal||May 7 10:38||1|
|This shit world||May 7 07:22||2|
|Outgoing connections||May 7 04:53||2|
|"time to live" ?||May 7 03:27||2|
|OTR on Bitmessage||May 7 02:06||31|
|Newbies! READ ME! (Bitmessage Primer)||May 7 00:43||1|
|For Bitmessage Devs - GUI Interface Design||May 6 23:18||1|
|O M E G A||May 6 19:14||14|
|Bitmessage being sandbagged?||May 6 05:55||3|
|Is Peter Surda around? Why stop signing technical messages?||May 5 22:40||3|
|How to decrypt past objects?||May 5 08:18||14|
|PyBM Error - no sufficient space in / partition but /home have lot's of free space||May 4 13:42||3|
|Anybody seen this error before?||May 4 12:58||4|
|<h1>HTML tags are enabled in subject tooltips</h1>||May 3 22:17||3|
|is that right?||May 3 07:33||6|
|RE: pyinstaller binaries do not run||May 2 07:37||1|
|RE: hidden chan?||May 1 06:05||1|
|hidden chan?||Apr 30 16:15||2|
|bitmessage takes long to connect and finds only few peers||Apr 29 10:54||2|
|pyinstaller binaries do not run||Apr 29 09:43||3|
|ready-made Linux distro with BM included via TOR : "Merlot"||Apr 29 09:27||1|