Inflood of old messages

[chan] bitmessage
Feb 2 11:02

What's up with the influx of old messages, which are sometimes even a week or more old? Is someone recomputing the PoW for these messages and flooding them out as new ones? It's also interesting that the repeated messages are ALL shitposts.

[chan] bitmessage
Feb 2 11:09

>It's also interesting that the repeated messages are ALL shitposts. You've just answered your own question.

[chan] bitmessage
Feb 2 11:24

Are the trolls now getting so fucking lazy, that they just repost old stuff? Has Bitmessage sunken so low that even the quality of the trolls is now dropping towards zero?

[chan] bitmessage
Feb 6 10:43

When I upgraded bitmessage old messages were re-synced or re-sent. Once all sent messages were recomputed. Three times all objects for the last 28 days were downloaded again.

[chan] bitmessage
Feb 6 11:02

There is a snotgobbler who is doing it on purpose.

[chan] bitmessage
Feb 6 11:33

Is there a way to mitigate this so my peer stops re-downloading and decrypting all objects?

[chan] bitmessage
Feb 6 11:36

I don't think so. Just delete them.

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Feb 6 12:07

> When I upgraded bitmessage old messages were re-synced or re-sent. Can you perhaps describe in a bit more detail which versions you upgraded from/to and how did you do the upgrade? Peter Surda Bitmessage core developer

[chan] bitmessage
Feb 6 12:15

Depends on the level of duplication. You can usually just keep a message and new messages will be compared against it (actually the hash of the signatures are compared rather than the subject/body - there was some person/group sending cryptocurrency exchange rates that complained some of their quotes were considered duplicates)

[chan] bitmessage
Feb 6 13:36

upgraded from 4.4 to current master and dev branch deleted /src and replaced with new /src in both instances had the problems

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Feb 6 13:59

> upgraded from 4.4 to current master and dev branch > > deleted /src and replaced with new /src > > in both instances had the problems It's possible that this happens once. I changed the storage type for certain binary types as they were being stored as text and this created some problems, like dumping/importing the sql data. This could create duplicates. After the "duplicates" are downloaded, all should be fine. I would like to add a data migration to initialisation before 0.6.3, which would avoid duplicates. However this would make the local data backwards incompatible with older versions (if you downgrade, they will refuse to start). But thanks for reporting this, I thought it may happen but haven't actually experienced it. Peter Surda Bitmessage core developer

[chan] bitmessage
Feb 15 02:50

Since upgrading to most recent pull v0.6.3.2, I am still having this problem. Every message in sent messages list now shows "doing work necessary to send message." Perhaps that exploit is still open?

BM-2cUdgkDDAahwPAU6oD2A7DnjqZz3hgY832
Feb 15 08:17

> Since upgrading to most recent pull v0.6.3.2, I am still having this > problem. Every message in sent messages list now shows "doing work > necessary to send message." Perhaps that exploit is still open? That sounds like it's resending messages that haven't been acknowledged. Peter Surda Bitmessage core developer

BM-2cU3ubnYxFdiUNkhqpezH2cVBerh4uMXjQ
Feb 15 08:44

Maybe because sending to someone who is activating dontsendack

[chan] bitmessage
Feb 15 15:28

YOU PEOPLE CAN'T READ.

[chan] bitmessage
Feb 15 15:29

> Maybe because sending to someone who is activating dontsendack Stop trying to mimimize the crappiness of the software, lickspittle. No, EVERY MESSAGE, to all chans, and all private addresses. every every did you read the word EVERY? EVERY MESSAGE GET IT? Stop trying to mimimize the crappiness of the software, lickspittle.

[chan] bitmessage
Feb 15 15:41

Trying to get stuff fixed by cursing at the dev. Pure genius.

[chan] bitmessage
Feb 15 16:03

Stop whining. If you don't like Bitmessage then don't use it.

BM-2cUdgkDDAahwPAU6oD2A7DnjqZz3hgY832
Feb 15 17:59

Please write bit more details, for example what was the previous version you had, what platform do you have, if you're using the portable mode, and so on. Messages to chans don't expect an ack so it's unusual that it's resent. Peter Surda Bitmessage core developer

[chan] bitmessage
Feb 15 18:08

Cursing? There are no cursewords here.

[chan] bitmessage
Feb 18 17:32

Ok I think I found the issue. It looks like a display error, it will erroneously show all messages as being doing PoW instead of the one that actually is. If you switch to another folder and then back, it should be showing all ok. I'll put it on the todo list. Peter Surda Bitmessage core developer

[chan] bitmessage
Feb 18 18:16

Ah, so it's just a glitch, not actually redoing all the messages. Got it.

[chan] bitmessage
Feb 18 19:16

Fixed in 616920e21a74864f7f32cfe4b32b17481bf2a4eb Peter Surda Bitmessage core developer

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
How to start an argument in geekspace Feb 24 23:37 38
Abit 1.0-rc1 Feb 24 18:18 2
http://33xtkivab2nthghe.onion/7uim34gdxs5z6b5l72nbji7ste Feb 24 08:36 1
Bitmessage security suggestion Feb 24 04:01 27
Fixes #1131 -- typo corrected Feb 23 22:19 1
little fish Feb 23 20:07 1
test Feb 23 17:43 3
Fixes #1134 Feb 23 14:42 2
Fixes #1131 Feb 23 11:37 1
Bitmessage feature request for API commands Feb 23 01:19 10
bitmessage launches cmd and then powershell Feb 22 15:53 56
bitmessage tor service Feb 22 13:31 6
I want the FEDS on this chan to know I identified one of their new tactics. Feb 20 12:03 2
Mitigating exploited software with firejail Feb 19 22:42 8
Critical vulnerability in v0.6.2 Feb 19 16:51 50
message database seems to be corrupted after all that upgraes and attacks Feb 19 14:55 7
Since upgrading yesterday to 6.3.2, Bitmessage is not connecting Feb 19 11:12 7
Inflood of old messages Feb 18 19:16 23
It is slow making connection. Feb 18 18:04 1
Globewashing Feb 18 17:44 1
how to make bitmessage secure Feb 18 05:02 1
Are you blacklisted/whitelisted? Feb 18 04:19 2
Are Linux systems vulnerable to recent attack? Feb 18 02:19 12
Are you blacklisted? Feb 18 02:09 1
address on Peter's reddit account Feb 17 23:51 3
Can't add entries to black list using Add Entry button Feb 17 15:20 4
Errors while trying to run 0.6.2 or 0.6.1 Feb 17 15:20 4
Bitmessage project looking for auditors and/or security specialists (reddit crosspost) Feb 17 13:21 6
HIRE A HACKER/CHANGE GRADES Feb 17 08:59 2
Download it. Feb 17 07:59 2
passphrase strength ? Feb 16 20:34 8
$ cd PyBitmessage ; git log | grep Author | sort -u | blacklist Feb 16 15:54 18
diagram Feb 16 01:46 1
Bitmessage components security seclusion example Feb 16 01:24 1
โฉฉ ๐„‰ ใŽฎ ไทฆ ๐Ÿžณ ๐Ÿ† ใ ๏‡บ f ๐™ฒ ๐Ÿ„ฆ โž‡ โจ˜ ใŠณ ๐— โฆฑ ๓ฟฟป ๏ค ๐Ÿ„น ๐Ÿ’ ๎… ไท„ ๎Žพ ๏ผซ ๎ƒ— ๐Ÿ†™ ๏€• ไทค ๐™ ๎Œฅ โ’„ โ‚น ๊ ฒ ๎‘• Feb 16 00:04 1
NOTICE: Address Revocation Feb 15 18:28 12
Cannot connect since yesterday Feb 15 17:59 2
Questions regarding recent bitmessage data exploit Feb 15 03:46 2
Latest commit borked Feb 14 05:26 5
BM-onion Feb 14 05:22 5
That's my new address Feb 14 03:40 1
BM massacre! Feb 13 21:23 2
Namecoin integration Feb 13 20:18 11
Hashwalling Functions for Security Feb 13 17:58 2
Same old problem connecting to network Feb 13 17:12 4
Injection attack mitigation Feb 13 16:52 7
This denial of service shit needs to be patched Feb 13 12:00 7
Test Feb 13 11:37 1
Proving that BM was sent? Feb 13 11:07 10
bitmessage ... Feb 13 08:13 1
Improve icon for chan + messages: important or not Feb 13 05:25 2
pickle puzzle Feb 13 01:03 20
so happy Feb 12 16:32 2
Fwd: Re: Did everyone else's BM starting freezing up Feb 11 03:54 10
hacker service Feb 10 03:48 2
another feature request Feb 10 01:12 1
bitmessage feature request Feb 10 01:10 1
feature request Feb 10 01:04 1
Questions for the Bitmessage Community Feb 9 21:30 7
Did everyone else's BM starting freezing up Feb 9 03:21 4
A light weight version of the denial of service message Feb 8 13:22 3
RE: Hello. Feb 8 11:48 1
WWtest Feb 8 10:44 1
test1 Feb 8 10:37 1
WARNING! denial of service message Feb 8 10:19 3
extended encoding Feb 8 01:24 7
bountyfy -- 7 โ‚ฌ payout Feb 5 20:59 2
clean up pyBM github landing page, please Feb 4 23:00 2
Running BM daemon as a service Feb 4 13:47 6
hidden service - long names Feb 4 12:37 7
RAM consumption - RAM not released Feb 3 21:05 4
Bug? First connection quickly breaks Feb 3 11:41 6
Request: debug.log initialization / termination Feb 2 18:30 2
kqueue poller in asyncore bounty -- no payout Feb 2 14:23 5
Bitmessage bug in Help > About Feb 2 13:59 7
Message size is metadata Feb 2 13:25 6
New warning "sni-qt/5864" WARN Feb 2 12:12 2
ordering Feb 1 10:38 12
RAM consumption Feb 1 10:14 5
discrepancy in transmit/receive byte counts Feb 1 07:53 6
BM CPU time Feb 1 02:39 5
kqueue poller in asyncore bounty Feb 1 00:13 15
new theme for beamstat Jan 31 11:35 2
Support request -- dontconnect in pyBM 062 not being honoured Jan 31 10:16 1
python IDE Jan 31 10:15 2
My BM is connected to one peer twice Jan 30 06:36 7
Support request/Bug report: keys.dat gets corrupted when running out of disk space Jan 29 15:44 2
Feature request/idea/suggestion: user-defined data directory (command-line argument) Jan 29 15:16 2
GUI dontsendack Jan 29 05:15 1
Another message problem Jan 29 03:49 3
Message deletion broken Jan 29 00:28 3
bitmessage on android device Jan 29 00:03 1