Trouble with private replies

[mix irving]

I had some trouble passing a valid invite key to the reply method in scuttle-dark-crystal

Traced it back to getInvite which was being a total jerk. I don't know why but it's not decrypting messages.
I've made it so that getInvite if given an invite just calls back with it.

This means upstream that reply can take an invite message and not die. This is for sure a workaround which is upsetting.

Changes :

• be0a261
• https://github.com/blockades/patchbay-dark-crystal/pull/8/files#diff-3c5dc10568d100893cb9fae3629e6d7bR57

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mix irving]

@christianbundy this stalebot is annoying here.

I just about re-wrote this issue. It's not resolved, it still needs resolving. It may be stale but I don't want it closed. Can you set it to mark them with a stale label instead?

[Christian Bundy]

Sorry about that. I just added the label "pinned" so it should be exempt from stale[bot] (I think if we label it "stale" it will get closed in 7 days). I'm still waiting, but soon we should be able to just assign ourselves to an issue to prevent it from becoming stale or getting closed.

[mix irving]

I don't want to assign myself?! I think pinned would be sufficient. It means that it's been seen and triaged into "quite important"

…

On Tue, 4 Dec 2018 at 05:37, Christian Bundy ***@***.***> wrote: Sorry about that. I just added the label "pinned" so it should be exempt from stale[bot] (I think if we label it "stale" it will get closed in 7 days). I'm still waiting <probot/stale#172>, but soon we should be able to just assign ourselves to an issue to prevent it from becoming stale or getting closed. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACitnmpZkOPJoP9Y_CZVazl-lc_t2re4ks5u1VMxgaJpZM4V1bXb> .

[mix irving]

You know what would be better than this? I beautiful issue tracking and weaving system for scuttlebutt. It drives me crazy that github has all this captured value in conversation

…

On Fri, 7 Dec 2018 at 16:50, mix irving ***@***.***> wrote: I don't want to assign myself?! I think pinned would be sufficient. It means that it's been seen and triaged into "quite important" On Tue, 4 Dec 2018 at 05:37, Christian Bundy ***@***.***> wrote: > Sorry about that. I just added the label "pinned" so it should be exempt > from stale[bot] (I think if we label it "stale" it will get closed in 7 > days). I'm still waiting <probot/stale#172>, but > soon we should be able to just assign ourselves to an issue to prevent it > from becoming stale or getting closed. > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub > <#7 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ACitnmpZkOPJoP9Y_CZVazl-lc_t2re4ks5u1VMxgaJpZM4V1bXb> > . >