bitboard

BM-2cW67GEKkHGonXKZLCzouLLxnLym3azS8r
Mar 14 05:28 [raw]

this.

BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v
Mar 14 07:55 [raw]

Looks pretty cool. I've thought a lot about doing something similar. When I get a dedicated server setup, I might run an instance for myself. Personally, I'd like it if Bitmessage was properly separated into Daemon and UI. A proper Web-facing Bitmessage instance could then be created where the PoW is done client-side in Web Assembly or something. There's still the moderation problem though - I imagine a lot of people would abuse that. I've proposed the idea of (a very expensive) PoW as Identity before which I think might partially mitigate this. For example, Identity = 2hr average to generate (set by board would be best), post = 30secs. That way, identities that spam can be easily blacklisted.

BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v
Mar 14 08:25 [raw]

> Identity = 2hr average to generate (set by board would be best), post = 30secs. Thought the same thing. Make identities very expensive. I think posts should be more expensive, more along the lines of 240 seconds (15 msgs/hr) avg pow. This does a few things: 1. Makes spamming difficult without highly expensive infrastructure. 2. Reduces flippant remarks that don't contribute to discussion. 3. Requires users to stay connected and service the network longer for their own messages to be sent. If you post avg of 45 msgs / day you would need to service the network 3 hrs / day to get your msgs out. Only a very tiny percentage of message board users post even close to that rate.

BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v
Mar 14 09:04 [raw]

Identities could be a little less expensive on first run, if PoW time between posts for a new identity is longer. A new identity could require 30 minutes PoW between posts, until the PoW is done to verify the identity a couple or more hours later, then the threshhold between posts could be lowered to 240 minutes. Bitmessage could require the same right now with chans, simply by raising demanded difficulty and message size by 15x.

BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v
Mar 14 09:58 [raw]

> 240 minutes. 240 seconds

BM-2cWZW87PJN5VZjtJCpk3hXcYefhNCxdjU6
Mar 14 11:48 [raw]

Well, that's a good thing to have such contributions. I would love too to have BitMessage implemented with a daemon and a separated UI. I guess Peter Surda will read these lines : For the BitMessage Secure Station project, which I am working on (Project paused currently due to the fact that I have not finished my complain at the European Commission for my famous Cartel case against Amazon & co) is indeed a double processor secure architecture, where BitMessage code is split into two part : A non secure world, and a secure world. It would have been very handy for me to have BitMessage already split into two parts, But if you are in this mindset, then, split it into 3 parts : - A first part handling the communication (Transmission/reception) of objects into the BitMessage P2P network, and of course storing them in a local database. - A second part handling decyphering received messages, either for person-2-person, or channels, including the cyphering of new ones, with the PoW thing. - A third part managing the UI. All these 3 parts communication through a PIPE or internal socket. This way, for the BitMessage Secure Station, I would just have to have the first one running on the first RAspberry pi, non secure, exposed to the internet. The second and the third would be running on the second raspberry pi, secure, not connected to the internet directely, but connected to the first one through a dedicaded SPI port and a custom side-channel safe protocol. Kind regards, Stman

BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v
Mar 15 07:52 [raw]

>A new identity could require 30 minutes PoW between posts I guess, realistically, once we bring in the concept of Expensive Identities we could create rules like this. I wouldn't have this value fixed necessarily. Dynamically adjusted perhaps on a per-chan basis. For example, within a certain time window, the post PoW becomes more and more expensive, perhaps even after a threshold of posts. E.g. more than three posts within half hour and the PoW doubles, then doubles again, etc. But the main intention here is to make boards easy to moderate, particularly if they're public-facing. For example, if I hosted bitchan.org and allowed others to be able to post via my identity on bitchan.org, there shouldn't be an expensive PoW per post. There also needs to be a "revoke" command so that front-facing nodes can request removal of a post that its moderators deemed unacceptable. Other clients/nodes should be able to choose whether they will abide by this revokation. This would actually make an excellent platform for leaks.

[chan] Crypto-Anarchist Federation
BM-2cWdaAUTrGZ21RzCpsReCk8n86ghu2oY3v

Subject Last Count
1 Sep 19 13:20 2
111 Sep 18 22:09 1
eita Sep 14 20:36 1
ankw Sep 14 20:36 1
ltd Sep 14 20:36 1
ycy Sep 14 20:36 1
bzgk Sep 14 20:25 1
imy Sep 14 20:25 1
pmrc Sep 14 20:14 1
vgz Sep 14 20:11 1
npjyr Sep 14 20:08 1
puij Sep 14 20:05 1
yml Sep 14 20:03 1
vcw Sep 14 20:02 1
kbkz Sep 14 19:58 1
byfx Sep 14 19:58 1
vdqqy Sep 14 19:57 1
ngcj Sep 14 19:56 1
ficeu Sep 14 19:54 1
gduv Sep 14 19:46 1
yczg Sep 14 19:46 1
jiy Sep 14 19:45 1
xun Sep 14 19:44 1
zft Sep 14 19:44 1
eto Sep 14 19:44 1
mqtjx Sep 14 19:44 1
uow Sep 14 19:43 1
odo Sep 14 19:43 1
bjzd Sep 14 19:41 1
pczer Sep 14 19:23 1
dob Sep 14 19:23 1
dni Sep 14 19:23 1
xldp Sep 14 19:23 1
ukzj Sep 14 19:20 1
yhx Sep 14 19:15 1
egjo Sep 14 19:12 1
zxg Sep 14 19:07 1
gihxd Sep 14 19:07 1
rqow Sep 14 19:07 1
sgaj Sep 14 19:07 1
mvttv Sep 14 19:06 1
lakyj Sep 14 19:04 1
jxns Sep 14 19:03 1
sbxp Sep 14 19:00 1
sgqic Sep 14 18:59 1
cxr Sep 14 18:58 1
cur Sep 14 18:56 1
malxq Sep 14 18:56 1
hhjf Sep 14 18:56 1
gyei Sep 14 18:50 1
dhfiw Sep 14 18:48 1
qkz Sep 14 18:32 1
zqzc Sep 14 18:31 1
aanp Sep 14 18:29 1
llezn Sep 14 18:25 1
ybqir Sep 14 18:10 1
orl Sep 14 18:10 1
tfbhw Sep 14 18:00 1
wha Sep 14 17:48 1
ovv Sep 14 17:48 1
rch Sep 14 17:44 1
rdxp Sep 14 17:44 1
zom Sep 14 17:40 1
vmdk Sep 14 17:37 1
pxvwp Sep 14 17:34 1
kkrdt Sep 14 17:31 1
ukbw Sep 14 17:30 1
gzsh Sep 14 17:29 1
yilmg Sep 14 17:19 1
rtpqj Sep 14 17:17 1
egxt Sep 14 17:12 1
shymw Sep 14 17:12 1
lgn Sep 14 17:08 1
cga Sep 14 17:08 1
rmlc Sep 14 17:08 1
jom Sep 14 17:08 1
rcc Sep 14 17:08 1
qht Sep 14 17:06 1
ukqep Sep 14 16:47 1
puxwg Sep 14 16:47 1
shin Sep 14 16:47 1
uftg Sep 14 16:47 1
gfp Sep 14 16:46 1
xjz Sep 14 16:39 1
afnp Sep 14 16:38 1
jokre Sep 14 16:36 1
acsyd Sep 14 16:30 1
zkqnl Sep 14 16:29 1
qpx Sep 14 16:29 1
zwlf Sep 14 16:29 1
eiu Sep 14 16:25 1
rgvs Sep 14 16:19 1
qkcs Sep 14 16:19 1
ewoe Sep 14 16:13 1
aylru Sep 14 16:11 1
ljacu Sep 14 16:06 1
dmub Sep 14 16:06 1
vithq Sep 14 16:06 1
zfcv Sep 14 16:01 1
glwvv Sep 14 16:00 1