Full time nodes

[chan] bitmessage
Aug 2 13:06

How many people are running nodes 24/7 ? Is there a way to tell the uptime of other nodes?

[chan] bitmessage
Aug 2 13:58

BM is decentralized and distributed. Uptime does not matter. Try this service: https://uptimerobot.com/

[chan] bitmessage
Aug 2 14:03

I can't keep mine up 24/7 as it eventually fills all RAM overnight and crashes

[chan] bitmessage
Aug 5 11:02

Version 0.6 treats memory way better.

[chan] bitmessage
Aug 5 11:04

I run one node. Uualy i need to restart it like every 14-20days I'm not sure with v0.6 cause it looks like treating memory way better.

BM-NBKKF1io494ddT3GxwzEebZVEJJ5ULQe
Aug 5 12:19

I had been running a 24/7 hidden service node before the asyncore mods. Asyncore caused some problems but I was able to resolve those recently. It was just a borked keys.dat file. BTW I ran onionscan on my .onion address and found some security holes. I advise using onionscan for hidden services just to be sure.

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Aug 5 12:36

Let me know what problems you're having (or had), I want to fix all the critical issues before 0.6.3. Regarding the onion addresses, I tested it previously on my ubuntu systems and only the port listed in the tor config was reachable. So just make sure you only list the PyBitmessage port and you should be fine. But making an extra check with onionscan can't hurt. Peter Surda Bitmessage core developer

[chan] bitmessage
Aug 5 13:47

I was running an apache web server on the same address just for lulz which I know is a security problem. I had mod_status enabled (apparently by default) which is really bad. I turned that off. I think there's a problem in the wiki about running as a hidden service: https://bitmessage.org/wiki/FAQ#How_do_I_setup_Bitmessage_as_a_hidden_service_on_Tor In the cell for "Incoming connections only through Tor"/"Outgoing connections over Tor" I believe sockslisten should be true, not false as stated in the wiki. I tried it both ways but could only connect outgoing with sockslisten = true. Anyway it's set to true now and everything is working as expected. All incoming connections are through my .onion address, all outgoing connections are via Tor.

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Aug 5 13:50

Thanks for the report, I opened a ticket and will review it. Peter Surda Bitmessage core developer

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
Is anyone even online at this moment? Aug 20 08:43 4
All green peers 127.0.0.1? Aug 19 09:07 5
Chips without backdoors Aug 18 19:10 4
New warnings in log Aug 17 21:00 20
Yellow peers and green peers Aug 16 20:59 4
cannot import name bmpow Aug 15 12:36 2
Brute forcing BM addr's Aug 15 07:58 2
Bitmessage crashes when posting Aug 14 05:51 10
plz assist. are you a netcat or SSH tunnel guru? Aug 14 05:01 4
shorter bitmessage addresses Aug 14 04:56 14
Why Python? Aug 13 10:45 16
Nerd Bully Aug 13 05:17 1
Bitmessage not connecting Aug 12 04:16 64
Feature idea Aug 10 03:30 10
Local nodes won't connect properly Aug 9 15:51 28
I do any thing in iran for BTC Aug 7 15:36 3
Bitmessage feature request Aug 7 12:50 4
query about short addresses Aug 7 06:54 4
Curious Aug 5 22:39 8
Full time nodes Aug 5 13:50 9
changes to the dodobit server Aug 5 11:05 2
Received Date Aug 5 06:04 13
apinotifypath Aug 4 06:04 9
BM <-> TOR Aug 3 13:19 12
BM Bandwidth Aug 2 14:11 11
When I try to register BM, collided with your key Aug 2 13:51 12
Received Date Aug 1 21:34 4
Bitmessage reminds me of ... Aug 1 14:36 3
I need help Aug 1 13:08 3
Response from Bitmessage Dodo Server Aug 1 02:25 1
Streams and bloom filter Jul 31 21:25 3
Questions about bitmessage streams Jul 31 21:25 1
TTL question Jul 31 08:03 3
API JSON index error Jul 31 07:22 3
API question Jul 30 11:22 7
MiNode Jul 30 07:19 3
Yes it's obvious my BM private keys have been stolen.... Jul 29 19:50 2
Keys.dat options Jul 29 04:56 3
Bitmessage and I2P no longer working Jul 28 22:39 10
Connect Bitmessage only to .onion nodes Jul 27 13:22 3
peers Jul 26 11:36 4
© 2013-2016 The Bitmessage Developers Jul 26 07:12 6
0.6.3 Jul 24 20:52 3
Bug with chan creation Jul 24 10:15 8