status-im/slack-archive
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
master
slack-archive/091-extended-e2e-test.html
T

217 lines
47 KiB
HTML
Raw Permalink Blame History

<html><body><style>
* {
font-family:sans-serif;
}
body {
text-align:center;
padding:1em;
}
.messages {
width:100%;
max-width:700px;
text-align:left;
display:inline-block;
}
.messages img {
background-color:rgb(248,244,240);
width:36px;
height:36px;
border-radius:0.2em;
display:inline-block;
vertical-align:top;
margin-right:0.65em;
}
.messages .time {
display:inline-block;
color:rgb(200,200,200);
margin-left:0.5em;
}
.messages .username {
display:inline-block;
font-weight:600;
line-height:1;
}
.messages .message {
display:inline-block;
vertical-align:top;
line-height:1;
width:calc(100% - 3em);
}
.messages .message .msg {
line-height:1.5;
}
</style><div class="messages"><div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-28 14:55</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-28 14:55</div><div class="msg">@igor680 set the channel purpose: <a href="https://github.com/status-im/ideas/91">https://github.com/status-im/ideas/91</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-28 14:56</div><div class="msg">@igor680 set the channel topic: <a href="https://github.com/status-im/ideas/91">https://github.com/status-im/ideas/91</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-28 14:56</div><div class="msg">@igor680 set the channel topic: <a href="https://github.com/status-im/ideas/issues/91">https://github.com/status-im/ideas/issues/91</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-28 14:56</div><div class="msg">@igor680 set the channel purpose: <a href="https://github.com/status-im/ideas/issues/91">https://github.com/status-im/ideas/issues/91</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 07:36</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 07:38</div><div class="msg">Hey @igor680 who is part of this swarm? Can you add contributors to the idea? When are you kicking this off?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 07:39</div><div class="msg">I see that @adan is working on something that sounds similar. Is it the same idea?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:39</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 07:43</div><div class="msg">The reason I?m asking is that I?m connecting swarms to OKR?s. Take a look at this doc <a href="https://docs.google.com/spreadsheets/d/1BhWKyjkpxhavkqtk9VYB3EHNDIzQtUlkwlg7_lQNAws/edit#gid=0">https://docs.google.com/spreadsheets/d/1BhWKyjkpxhavkqtk9VYB3EHNDIzQtUlkwlg7_lQNAws/edit#gid=0</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:53</div><div class="msg">@chad yep, this swarm is about the send/delivery ratio KR. So it goes together with #99-confidence
It still is a bit drafty. So far it's @andreap and me who started. I hope to launch it properly post-Easter holidays.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:54</div><div class="msg">Hi, I am wondering is it possible to create a bot which will send any amount of messages to a public key?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:55</div><div class="msg">would be great to implement the bot on go side in order not to use UI (will be used for network/ui performance tests) in order to check the behavior of the app with ~10k messages in a chat</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:56</div><div class="msg">So far I made one that sends messages to a public chat.
Here, I wanted to use Clojure (but not UI) for these tests, not to re-implement the message protocol we have on top on Whisper.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:56</div><div class="msg">Clojure with no UI sounds awesome</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-03-29 07:56</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:57</div><div class="msg">Yeah, @roman made a small PoC, so we hope to continue from there.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:57</div><div class="msg">I see this as a job in Jenkins which can be built with 2 params: public key and number of messages</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:58</div><div class="msg">there are a few scenarios and a few parameters, I tried to write them in the idea itself</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:58</div><div class="msg">(including network quality and topology)</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-03-29 07:58</div><div class="msg">As a clojure dev, we would like everything to be dockerized, so we can easily run the e2e tests on our machines</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:58</div><div class="msg">Let me know if any assistance from my side is required in order to get this done, maybe one of yours scenarios can be extended in order to make the bot</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:59</div><div class="msg">for testteam purposes such tool is must need</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:59</div><div class="msg">maybe we can have a sync-up on Tuesday for that? @adan it would be great if you can join?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 07:59</div><div class="msg">send me an invite please</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 07:59</div><div class="msg">will do</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 08:35</div><div class="msg">@levgeniia created this issue today too. Great to get her involved. I assume it makes sense for @adan and @levgeniia to join this swarm too?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-03-29 08:35</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 08:38</div><div class="msg">So, let?s make a sync-up on Tuesday to gather everyone?s opinions and requirements about that. I'll be glad to tweak the idea so it fits more usecases.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 08:39</div><div class="msg">Then if we all be on the same page, we can kick it off :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 08:39</div><div class="msg">Sounds awesome! I think what this swarm is doing is so important!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-29 08:40</div><div class="msg">I have one ask: Make the reliability number super visible. Eg post it to core everyday automatically (with +/- change from last period)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 08:46</div><div class="msg">Good idea!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 08:47</div><div class="msg">we are going to add reliability number visibility to <a href="https://github.com/status-im/status-react/issues/3723">https://github.com/status-im/status-react/issues/3723</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 08:58</div><div class="msg">yeah, so it is very similar to what is described in the idea.
@levgeniia @adan can you take a look at <a href="https://github.com/status-im/ideas/issues/91">https://github.com/status-im/ideas/issues/91</a> and give your feedback? :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-03-29 08:59</div><div class="msg">I think that #91 is the idea which we discussed in BKK, right?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 09:02</div><div class="msg">hmm, I wasn't in BKK, so? maybe? :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 09:09</div><div class="msg">sent an invitation, ping me if the time doesn?t suit you</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-03-29 09:32</div><div class="msg">sorry, it's conflicting with dogfooding session which I?m leading in Tuesday</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 09:34</div><div class="msg">what time works better for you then?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-03-29 09:36</div><div class="msg">starting from 11.30 CET</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-29 09:38</div><div class="msg">updated</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-03-29 09:39</div><div class="msg">thank you!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 08:07</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 08:16</div><div class="msg">I think send/delivered ratio is a crucial metric for Send/delivered ratio &gt;99% KR. We should have stats from production (users that enabled sharing data) as well as from testnet. I was thinking of having it in Grafana together with historical data.
@igor680 is it possible to track it on the go level? Maybe we could at least track number of messages that were send and just compare it with delivered messages?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 08:21</div><div class="msg">please invite me as well. I'd love to contribute to to the bots (test data generation) as well as e2e tests themselves.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 08:26</div><div class="msg">Yeah, that was the idea</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 08:28</div><div class="msg">great! can we track if a particular message that was send was delivered? Or we will need to track just general number of messages that were sent/delivered?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 09:15</div><div class="msg">if we have a common DB we can send random values as a message content and track them, for instance</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 09:30</div><div class="msg">yeah, and maybe we could visualise (have a simple dashboard with other metrics like avg. time it takes to deliver a message) in Grafana. @adamb I heard you are already using Grafana. What do you think about our idea? Is Grafana a good place to visualize it? What data source we could use to store the data?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 09:33</div><div class="msg">Since all our tests will run in the same Docker compose, we can use any container with relational DB there and after that post data to something else.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 09:34</div><div class="msg">Hm, I was thinking about tracking this data in general. Also for real users using the app in production. Of course when they will allow for it (by sharing usage data).</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 09:40</div><div class="msg">For the real users it would be very tricky w/o read receipts.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 09:48</div><div class="msg">so we won't know if a message was delivered?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 09:54</div><div class="msg">Maybe we as a company can get some stats from a mail server. But we as users - maybe not. But @roman and #99-confidence should know the answers</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 09:59</div><div class="msg">what if we could just increment number of delivered messages if a message is received in the app?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-03-30 10:08</div><div class="msg">That would only work if both the sender and the receiver allow us to collect the data.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 10:16</div><div class="msg">yeah, and I think it could work. We would have real time production monitoring. @chad do you think we could track number of messages that were send and delivered as a part of sharing usage data? Do you have any idea how many (%) users will allow to collect the data in general?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-26/320279260448_ec6cae0dd4f9145858b4_72.jpg" /><div class="message"><div class="username">chad</div><div class="time">2018-03-30 10:18</div><div class="msg">Yes absolutely. We currently track who taps ?send?, but don't yet track other messaging states. I know that the iOS system data opt-in rate is around 35%. Hopefully ours will be higher.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-03-30 11:56</div><div class="msg">35% is not bad. Having send/delivered ratio for so many users will give us great insight about message reliability</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-02 16:18</div><div class="msg">Hey guys, the PoC for message reliability automated solution is done.
You can see the results here <a href="https://jenkins.status.im/job/end-to-end-tests/job/status-app-message-reliability/23/artifact/test/appium/tests/chart.png">https://jenkins.status.im/job/end-to-end-tests/job/status-app-message-reliability/23/artifact/test/appium/tests/chart.png</a>
The graph shows number of messages received by each user and time for a message to be received.
As you can see time to receive messages growth with increasing amount of messages.
I assume that the time will grow even more with increasing amount of messages.
We can't test this assumption now because of a session time restriction from SauceLabs (max 3 hours) but we are going to solve it soon.
Please add your thoughts :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 08:05</div><div class="msg">Looks great!
What was the environment?
Was it just 2 mobile clients talking through our production mailservers?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 08:23</div><div class="msg">Nice @levgeniia!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-03 08:24</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-19/289021559940_764a5c704a5a99098d7a_72.jpg" /><div class="message"><div class="username">oskarth</div><div class="time">2018-04-03 09:08</div><div class="msg">@oskarth has renamed the channel from "91-extended-e2e-tests" to "091-extended-e2e-test"</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 12:26</div><div class="msg"><!here> there is the meeting minutes of the call. feel free to tweak if I forgot anything.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 12:30</div><div class="msg">@adan this is the bots repo: <a href="https://github.com/mandrigin/status-go-bots">https://github.com/mandrigin/status-go-bots</a>. It has a Dockerfile already.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 12:31</div><div class="msg">that is basically how I call it
`docker run -d --restart unless-stopped -e "STATUS_BOT_PASSWORD=&lt;password&gt;" status-bots:whisper-v6 pinger --channel=humans-need-not-apply --nickname="whisperv6 experimental bot"`</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 12:34</div><div class="msg">and kudos to @andreap for <a href="https://github.com/status-im/status-react/pull/3750">https://github.com/status-im/status-react/pull/3750</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-03 13:28</div><div class="msg">I?m going to start today with PoC of tests for public chat with bot, @igor680 could you please send me a password for it?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 13:35</div><div class="msg">Ah, you can pick any password. It will either create an account or sign in with that. </div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-03 13:57</div><div class="msg">thanks!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 14:37</div><div class="msg">I was able to run it. `make` then:
```
docker run -d --restart unless-stopped -e "STATUS_BOT_PASSWORD=abc123456" status-bots:latest pinger --channel=humans-need-not-apply-lukasz --nickname="bot"
```
I see in the logs that the bot is receiving envelopes and tries to send some. But, I don't see the its messages in the channel. @igor680 any idea?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 14:41</div><div class="msg">what network are you looking at? the bot sends stuff only to our current Ropsten network.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 14:53</div><div class="msg">I?m on Ropsten. Does my command look ok?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 14:55</div><div class="msg">I can receive messages from ?humans-need-not-apply? (your bot) but not mine.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 15:13</div><div class="msg">ah, probably you need to use whisperv6 branch</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 15:13</div><div class="msg">I don't remember if I merged it into master</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 15:23</div><div class="msg">updated the MVP description: <a href="https://github.com/status-im/ideas/issues/91">https://github.com/status-im/ideas/issues/91</a></div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 15:28</div><div class="msg">@lukasz949 did it help?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:08</div><div class="msg">@igor680 nope:
```
2018/04/03 16:06:40 -&gt; SENT: {"jsonrpc":"2.0","id":0,"result":true}
DEBUG[04-03|16:06:49] Can't resolve node id=e006f0b2dc98e757 err="discovery is disabled"
```
I?m not sure if ?Can?t resolve node? is an issue here?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:11</div><div class="msg">did you push the branch?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 16:12</div><div class="msg">hmm, good point. try `igorm/whisper-v6` branch now</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:19</div><div class="msg">yes, now it works!</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 16:19</div><div class="msg">great! I'll need to merge it to master then</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:19</div><div class="msg">sweet :slightly_smiling_face: I?m going to use it in battery tests today</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:24</div><div class="msg">interesting, I?m sending a new message every 5s and app receives ~6 messages at once. Maybe it's because the network usage at this moment.
Also, looking at the timestamp in the messages, the ordering is wrong.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:24</div><div class="msg">we can learn a lot from such load tests</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 16:24</div><div class="msg">yeah, network is weird sometimes</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 16:25</div><div class="msg">merged `igorm/whisper-v6` to `master`</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-03 16:26</div><div class="msg">I?m wondering if the ordering issue I just mentioned is something we are aware of?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-03 16:34</div><div class="msg">no idea :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-04-04 13:22</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-04-07 18:35</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-09 14:20</div><div class="msg">hey, I?m not able to receive messages from the bot now, it this due to the new protocol?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-09 14:23</div><div class="msg">yep</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-09 14:23</div><div class="msg">I hope @adria will make a new bot that works with the new protocol.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-09 14:24</div><div class="msg">@levgeniia does the new protocol support public chats?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-09 14:25</div><div class="msg">yes</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-09 14:25</div><div class="msg">great :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-09 14:28</div><div class="msg">so for now tests implementation is blocked by the bot absence on the one hand and by SauceLabs session duration limit on the other hand</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-10 15:04</div><div class="msg">is this swarm still active? ( I just noticed that the issue has been closed on github). Just saying this as I am quite close to get a command line working that sends messages to a specific public key</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-10 15:05</div><div class="msg">(1 to 1 chat)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-10 15:09</div><div class="msg">yep, it is still in drafts but it will start soon :slightly_smiling_face:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-10 15:11</div><div class="msg">cool, thanks! maybe you know, do we have a document on what the command line parameters should be?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-10 15:18</div><div class="msg">nope, it would be nice if you add them</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-10 15:21</div><div class="msg">ok, I'll ask around to gather some requirements</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-11 08:08</div><div class="msg"><!here> I would like to formalize what we need from the command line tool, could you please comment on what you need and a brief explanation of why you need it please, I will collate it and add it to a doc.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-11 08:10</div><div class="msg">1. Prerequisites for a chat (creating an account/logging in, preserving this information somewhere).
2. 1o1 chats, public groups and private group chats, to be able to read/write messages there (that sounds like a web API to me)</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-16/316437191861_849cef1f2e8411a22126_72.png" /><div class="message"><div class="username">lukasz949</div><div class="time">2018-04-11 08:12</div><div class="msg">@andreap I put test team requirements here: <a href="https://github.com/status-im/ideas/issues/131#issuecomment-378895534">https://github.com/status-im/ideas/issues/131#issuecomment-378895534</a></div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-11 08:13</div><div class="msg">thanks, I missed that @lukasz949</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-11 08:38</div><div class="msg">Also, there seems to be a bit of a duplication of effort, we are both developing a clojure and a go command line, is there any consesus on which one we should be focusing on?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-11 08:42</div><div class="msg">I think Clojure is important for this Swarm in particular. We want to be as close to the real client as possible.
Go SDK won't provide that much authenticity.
So in the bright future? I see us having a Clojure bot that shares most of the code with Status itself.</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-11 08:42</div><div class="msg">@adria wdyt? and what are your plans for Go SDK?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-04-11 08:50</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-04-11 08:55</div><div class="msg">Go SDK is not a CLI tool, should be the library you can build a CLI on top of it.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-11 08:57</div><div class="msg">ok, so let's keep the command line as a clojure effort, as sdk seems to be an independent effort which provides value on its own, thanks @adria</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-04-11 08:57</div><div class="msg">i agree there is an overlap in the sense we could interact with messaging system thorugh 2 different libraries go and react</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-22/302460725283_f9781c5a7fcc3cf62af9_72.jpg" /><div class="message"><div class="username">adria</div><div class="time">2018-04-11 08:58</div><div class="msg">:thumbsup:</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-11 08:58</div><div class="msg">:+1:</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-06/310412231971_aab33885aa55d16e4740_72.jpg" /><div class="message"><div class="username">arnetheduck.slack</div><div class="time">2018-04-11 09:21</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-03-08/150717543185_46c3b78ed6fd88d4b338_72.jpg" /><div class="message"><div class="username">anna</div><div class="time">2018-04-11 09:22</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-12-29/291837550193_7c75b6459537f373c8e1_72.jpg" /><div class="message"><div class="username">igor680</div><div class="time">2018-04-13 08:59</div><div class="msg">@levgeniia so I guess now when the pinger is implemented, the stress test implementation is (partially) unblocked?</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-01-12/298981446807_2ce374952c07670e437e_72.jpg" /><div class="message"><div class="username">levgeniia</div><div class="time">2018-04-13 09:03</div><div class="msg">yes, sure, I?m going to continue soon</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-16 12:50</div><div class="msg">I have implemented support for group/public/1to1 chats on the clojure cli, it's still a bit rough but you get the idea <a href="https://github.com/status-im/status-react/tree/tests/use-cli-in-tests">https://github.com/status-im/status-react/tree/tests/use-cli-in-tests</a> . It will probably be packaged as a docker-image as it needs to include status-go as well</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-04-16 12:58</div><div class="msg">Hi all. I had a conversation with @igor680 on Friday, because this swarm seems to overlap with what I've been trying to start for a long time, so here some more food for thoughts from me.
There is a possibility in geth to create custom in-memory p2p networks. Basically you can programmatically start Node1, Node2... Node N, connect them in a way you wish, and run any service on top of these p2p network, for example Whisper.
I do harness this for p2p whisper simulator and I'm able to easily create custom networks with ~800 nodes and custom topologies, start Whisper nodes on each of them and start simulation. This is insanely fast (starting network and nodes takes around 1.5 sec on my macbook) and opens a huge space for analysis of how network behaves, how messages are delivered etc.
However, this simulator can also run nodes not as a geth's in-memory service, but also as a local executable and as a docker container. I haven't explored these options yet, but it's implemented and should work. So we potentially can run the whole status-go/status-react stack within this simulation, not only whisper service.
I'm using this simulations for work on 3D visualization of whisper, but I think this swarm can benefit from this solution as well. Let me know if you interested, I think I can hack the proof-of-concept code for simulation with docker in a couple of days so we can try and evaluate if this can be used for the swarm needs.</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-16 13:02</div><div class="msg">It feels like this could be useful, at least for when we want network connections to be reliable, I will probably ask more about at some point when you have time</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/3fbb10b8c7115b8c44459363fb6476cf.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F66f9%2Fimg%2Favatars%2Fava_0007-72.png" /><div class="message"><div class="username">divan</div><div class="time">2018-04-16 13:05</div><div class="msg">Sure. Yeah, I think it's possible to implement slow/laggy network as well (they use in-mem net.Conn object so it can be extended to simulate shitty network connection).</div></div></div><br/>
<div><img src="https://secure.gravatar.com/avatar/4f643ff2e520e1b103a3c81fe6d4267c.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2F3654%2Fimg%2Favatars%2Fava_0023-72.png" /><div class="message"><div class="username">andreap</div><div class="time">2018-04-16 13:05</div><div class="msg">cool, it would be handy to have something like that</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2018-02-23/319521513136_d6db8eeb85a03cb7d705_72.png" /><div class="message"><div class="username">andreaf</div><div class="time">2018-04-17 01:13</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-08-23/230590927909_ddd8ad9c4f223a701b35_72.jpg" /><div class="message"><div class="username">adan</div><div class="time">2018-04-25 07:54</div><div class="msg">has joined #091-extended-e2e-test</div></div></div><br/>
<div><img src="https://avatars.slack-edge.com/2017-10-04/251566892466_e37667e6064fe542e7d7_72.jpg" /><div class="message"><div class="username">naghdy</div><div class="time">2018-10-05 05:50</div><div class="msg">@naghdy archived the channel</div></div></div><br/>
</div></body></html>
Reference in New Issue View Git Blame Copy Permalink