Undistributed NuShares

[GLock]

Thanks for your feedback. I will try to send another message even though I tried that already few weeks ago.

[RobertLloyd]

Glock
I was approved for purchase in September and had an message from Jordan asking me several questions. I replied late Sept, and resent in early October, but have yet to hear

[mhps]

Be sure to date your message in the text. It seems that my Bitmessage changes dates of sent messages according to when the receiving end receives / opens / replies it. It also tries to re-send old message again possiblly because the receiving party has deleted it after replying. It would really confuse the receiver, and hence cause you trouble, if he receive the same message again after having replied it.

[GLock]

@RobertLloyd I can see that I am not the only one in the same situation, thank you for the info.

@mhps thank you for the advice

[kac]

Do you know if it’s possible to export reception ACK from BitMessage and how to use it as a “prove of sent”?
I don’t even know if I’m “approved” for purchase, if no - I’d be glad to know that. ACK of request received 18 Oct.
Cheers

[Hyena]

I also contacted you with BM a month ago and I got an initial reply that asked me to send a new message to another BM address. I did that but haven’t got any reply. I guess my message was lost then? I am still interested in buying a lot of nushares. I guess I must send a new bitmessage?

[Hyena]

Everyone will receive the price as it was at the time of their initial request.

thank god that

[lg15x]

Peercoin and Nubits community is the best I’ve ever seen.

[Hyena]

May I ask what version of BM JL is using? My friend used 0.4.2 far too long and at some point he didn’t receive any messages from me and I didn’t receive messages from him. Then he upgraded his BitMessage to 0.4.4 and everything started to work again. I sent a message to the address I received as an answer to the nushares buying request yesterday and it still shows “Message sent. Waiting for ACK.”

[kschneezy]

Some of the brightest minds in the world are working with Peercoin and Nubits

[miner]

Exactly. Impressive job and I can see the dev team growing. I noticed new ids in the peerunity dev team when the 0.1.2 released.

[kschneezy]

I am just hopeful I can participate, still waiting on my NuShares…

Not to say I can not contribute without them, but there is no financial incentive to do so. I do wish to help the Nu economy grow for ideological reasons as I believe that it can bring about benevolent change.

[desrever]

My friend used 0.4.2 far too long and at some point he didn’t receive any messages from me and I didn’t receive messages from him. Then he upgraded his BitMessage to 0.4.4 and everything started to work again.

This happened to me too! Glad to see I am not alone! Writing a post right away!

[Cybnate]

It is a lot better than on 0.4.2, but I still have issues with acknowledgements by the network after I’ve sent a message. Haven’t figured out why that happens sometimes even with the same people. It is hard to test as you don’t know how other people behave (e.g. go off-line, restart client, use ToR etc.). Hope next version improves this aspect.

[cryptog]

@Cybnate “not acknowledged” means the sendee has not opened the msg yet —> at least this is my interpretation .

[masterOfDisaster]

You can only for sure say that the acknowledgement has not been received by the sender; it’s possible that the recipient has received the message, sent an ack, but this was somehow lost (would it be resent? is the receipt of an ack confirmed in bitmessage?). Or the recipient didn’t send an ack because of a malfunction of the application, etc…
There are a lot of possibilities what can go wrong when trying to establish a reliable communication.

[Cybnate]

I have examples where the recipient did receive the message, but I have never received the ack. It makes it hard as you are forced to resend messages to ensure they have received it. Looking at the BM forum, the devs are still active, so I still hope that this will be fixed rather sooner than later.

[mhps]

I have some old message in my sent box that has been answered months ago. Now the client starts to do work to send them again every time I turn on the client. I don’t want to remove these message and the client doesn’t allow to archive old sent messages. I don’t want the old message to get resend again. So basically I have stopped turning on my BM client

[cryptog]

@Cybnate i am having the same experience here. i sent a msg to JL recently with no acknowledgement yet though all my msgs were acknowledged almost immediately so far. i tried sending a msg to a friend for testing purposes. same thing. no ack but he confirmed he did get it. weird.

[cryptog]

@JordanLee Hi Jordan. I sent you a message on 08DEC14 (to you and your representative ?). Since it was not acknowledged, I decided to resend it to you today (12DEC14) just in case.
Sorry if you got it twice.
Looking forward to your reply.