-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathlatest.rss
659 lines (652 loc) · 48.5 KB
/
latest.rss
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:discourse="http://www.discourse.org/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>MESG Community - Latest topics</title>
<link>https://forum.mesg.com/latest</link>
<description>Latest topics</description>
<lastBuildDate>Mon, 10 Aug 2020 11:57:08 +0000</lastBuildDate>
<atom:link href="https://forum.mesg.com/latest.rss" rel="self" type="application/rss+xml" />
<item>
<title>Build Easier, Ship Faster: Why We Launched Liteflow</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><a href="https://liteflow.com/?utm_source=mesg_blog&utm_medium=blog_post&utm_campaign=why_liteflow">Liteflow</a> is a new open platform for application processing that helps developer-entrepreneurs launch projects easily and quickly. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/what-is-liteflow/">https://blog.mesg.com/what-is-liteflow/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/763">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/763</link>
<pubDate>Mon, 10 Aug 2020 11:57:08 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-763</guid>
<source url="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/763.rss">Build Easier, Ship Faster: Why We Launched Liteflow</source>
</item>
<item>
<title>Community Update: April & May 2020</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered
straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-april-may-2020/">https://blog.mesg.com/community-update-april-may-2020/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-april-may-2020/757">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-april-may-2020/757</link>
<pubDate>Wed, 03 Jun 2020 09:36:44 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-757</guid>
<source url="https://forum.mesg.com/t/community-update-april-may-2020/757.rss">Community Update: April & May 2020</source>
</item>
<item>
<title>Migrate your application to Liteflow</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>With the launch of <a href="https://blog.mesg.com/why-did-we-build-liteflow/">Liteflow</a>, the current ecosystem of MESG has changed, and your application is slightly different, but that’s for the best.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/migrate-your-application-to-liteflow/">https://blog.mesg.com/migrate-your-application-to-liteflow/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/migrate-your-application-to-liteflow/738">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/migrate-your-application-to-liteflow/738</link>
<pubDate>Fri, 08 May 2020 03:30:52 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-738</guid>
<source url="https://forum.mesg.com/t/migrate-your-application-to-liteflow/738.rss">Migrate your application to Liteflow</source>
</item>
<item>
<title>A new era for the MESG Token</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>With the <a href="https://blog.mesg.com/why-did-we-build-liteflow/">launch of Liteflow</a>, it was time to rethink all of the products of MESG, token included. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/a-new-era-for-the-mesg-token/">https://blog.mesg.com/a-new-era-for-the-mesg-token/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/a-new-era-for-the-mesg-token/732">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/a-new-era-for-the-mesg-token/732</link>
<pubDate>Fri, 01 May 2020 06:05:22 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-732</guid>
<source url="https://forum.mesg.com/t/a-new-era-for-the-mesg-token/732.rss">A new era for the MESG Token</source>
</item>
<item>
<title>A new era for the MESG Token</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>With the <a href="https://blog.mesg.com/why-did-we-build-liteflow/">launch of Liteflow</a>, it was time to rethink all of the products of MESG, token included. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/5a16b201-101e-456b-b2bc-1e7c30a71023/">https://blog.mesg.com/p/5a16b201-101e-456b-b2bc-1e7c30a71023/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/a-new-era-for-the-mesg-token/731">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/a-new-era-for-the-mesg-token/731</link>
<pubDate>Fri, 01 May 2020 05:59:17 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-731</guid>
<source url="https://forum.mesg.com/t/a-new-era-for-the-mesg-token/731.rss">A new era for the MESG Token</source>
</item>
<item>
<title>Build Easier, Ship Faster: Why We Launched Liteflow</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><a href="https://liteflow.com/?utm_source=mesg_blog&utm_medium=blog_post&utm_campaign=why_liteflow">Liteflow</a> is a new open platform for application processing that helps developer-entrepreneurs launch projects easily and quickly. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/why-did-we-build-liteflow/">https://blog.mesg.com/why-did-we-build-liteflow/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/728">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/728</link>
<pubDate>Wed, 29 Apr 2020 19:52:56 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-728</guid>
<source url="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/728.rss">Build Easier, Ship Faster: Why We Launched Liteflow</source>
</item>
<item>
<title>Build Easier, Ship Faster: Why We Launched Liteflow</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><a href="https://liteflow.com/?utm_source=mesg_blog&utm_medium=blog_post&utm_campaign=why_liteflow">Liteflow</a> is a new open platform for application processing that helps developer-entrepreneurs launch projects easily and quickly. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/1c487811-6528-4fd3-bd0a-9d80300e91c9/">https://blog.mesg.com/p/1c487811-6528-4fd3-bd0a-9d80300e91c9/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/727">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/727</link>
<pubDate>Wed, 29 Apr 2020 19:32:45 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-727</guid>
<source url="https://forum.mesg.com/t/build-easier-ship-faster-why-we-launched-liteflow/727.rss">Build Easier, Ship Faster: Why We Launched Liteflow</source>
</item>
<item>
<title>gRPC issues when creating a service</title>
<dc:creator><![CDATA[fragment]]></dc:creator>
<category>Hackathon</category>
<description><![CDATA[
<p><code>npm link</code> does not work</p>
<p>Error:</p>
<pre><code>`Error: The gRPC binary module was not installed. This may be fixed by running "npm rebuild"
</code></pre>
<p>Original error: Cannot find module ‘/usr/lib/node_modules/<span class="mention">@mesg</span>/cli/node_modules/grpc/src/node/extension_binary/node-v64-linux-x64-glibc/grpc_node.node’<br>
at Object. (/usr/lib/node_modules/<span class="mention">@mesg</span>/cli/node_modules/grpc/src/grpc_extension.js:43:17)<br>
at Object. (/usr/lib/node_modules/<span class="mention">@mesg</span>/cli/node_modules/grpc/src/client_interceptors.js:144:12)<br>
`</p>
<p><small>3 posts - 2 participants</small></p>
<p><a href="https://forum.mesg.com/t/grpc-issues-when-creating-a-service/723">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/grpc-issues-when-creating-a-service/723</link>
<pubDate>Sun, 26 Apr 2020 23:24:01 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-723</guid>
<source url="https://forum.mesg.com/t/grpc-issues-when-creating-a-service/723.rss">gRPC issues when creating a service</source>
</item>
<item>
<title>Migrate your application to Liteflow</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>With the launch of Liteflow[<a href="https://docs.google.com/document/d/1wrYhWFQ18qvmD3fMmucan0bg4l8HlCkoIuTcWw0_H1A/edit">https://docs.google.com/document/d/1wrYhWFQ18qvmD3fMmucan0bg4l8HlCkoIuTcWw0_H1A/edit</a>], the current ecosystem of MESG has changed, and your application is slightly different, but that’s for the best.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/5524418a-ced9-4361-9a86-0cc5b0b4308e/">https://blog.mesg.com/p/5524418a-ced9-4361-9a86-0cc5b0b4308e/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/migrate-your-application-to-liteflow/721">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/migrate-your-application-to-liteflow/721</link>
<pubDate>Fri, 24 Apr 2020 05:29:41 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-721</guid>
<source url="https://forum.mesg.com/t/migrate-your-application-to-liteflow/721.rss">Migrate your application to Liteflow</source>
</item>
<item>
<title>A Refreshing Development Experience Awaits...</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><em>Application development is slow, it’s inefficient, there’s high overhead, customization & maintenance are a mess, it’s hard to scale, tough to secure, a challenge to avoid vendor lock-in, and you’re dependent on the success of the platforms you build upon.</em></p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/a-refreshing-development-experience-awaits/">https://blog.mesg.com/a-refreshing-development-experience-awaits/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/a-refreshing-development-experience-awaits/719">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/a-refreshing-development-experience-awaits/719</link>
<pubDate>Thu, 23 Apr 2020 20:22:28 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-719</guid>
<source url="https://forum.mesg.com/t/a-refreshing-development-experience-awaits/719.rss">A Refreshing Development Experience Awaits...</source>
</item>
<item>
<title>A refreshing take on development awaits...</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><strong>That’s all about to change...</strong></p>
<p><strong>And that's only the beginning.</strong></p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/f09b1218-e5b6-4d30-bfaa-1c1ea435d430/">https://blog.mesg.com/p/f09b1218-e5b6-4d30-bfaa-1c1ea435d430/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/a-refreshing-take-on-development-awaits/718">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/a-refreshing-take-on-development-awaits/718</link>
<pubDate>Thu, 23 Apr 2020 19:59:25 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-718</guid>
<source url="https://forum.mesg.com/t/a-refreshing-take-on-development-awaits/718.rss">A refreshing take on development awaits...</source>
</item>
<item>
<title>MESG Community Update - March '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered
straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-march-2020/">https://blog.mesg.com/community-update-march-2020/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/mesg-community-update-march-20/699">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/mesg-community-update-march-20/699</link>
<pubDate>Sat, 04 Apr 2020 18:47:40 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-699</guid>
<source url="https://forum.mesg.com/t/mesg-community-update-march-20/699.rss">MESG Community Update - March '20</source>
</item>
<item>
<title>Aragon DAO to MESG Integration: Milestone 2</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><em>This article is a continuation of MESG's ongoing integration with Aragon, connecting DAOs to to web services. See our previous report on <a href="https://blog.mesg.com/aragon-dao-integration/">Milestone 1</a>. </em></p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/aragon-dao-integration-milestone-2/">https://blog.mesg.com/aragon-dao-integration-milestone-2/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/678">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/678</link>
<pubDate>Fri, 06 Mar 2020 09:57:39 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-678</guid>
<source url="https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/678.rss">Aragon DAO to MESG Integration: Milestone 2</source>
</item>
<item>
<title>Aragon DAO to MESG Integration: Milestone 2</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>The second milestone of our Aragon / MESG integration has been reached! We’ve built an Aragon application for connecting to webhooks. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/f296bff4-df21-4abc-a3e3-4998bd8a3901/">https://blog.mesg.com/p/f296bff4-df21-4abc-a3e3-4998bd8a3901/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/676">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/676</link>
<pubDate>Thu, 05 Mar 2020 10:58:27 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-676</guid>
<source url="https://forum.mesg.com/t/aragon-dao-to-mesg-integration-milestone-2/676.rss">Aragon DAO to MESG Integration: Milestone 2</source>
</item>
<item>
<title>Community Update: Late Feb '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered
straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-late-february-20/">https://blog.mesg.com/community-update-late-february-20/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-late-feb-20/672">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-late-feb-20/672</link>
<pubDate>Mon, 02 Mar 2020 11:39:47 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-672</guid>
<source url="https://forum.mesg.com/t/community-update-late-feb-20/672.rss">Community Update: Late Feb '20</source>
</item>
<item>
<title>MESG Ecosystem Online Hackathon - Win up to $9k</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>We’re extremely excited to announce the MESG Ecosystem Hackathon, the second online hackathon by the MESG Foundation.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/announcing-the-mesg-ecosystem-online-hackathon/">https://blog.mesg.com/announcing-the-mesg-ecosystem-online-hackathon/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/mesg-ecosystem-online-hackathon-win-up-to-9k/670">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/mesg-ecosystem-online-hackathon-win-up-to-9k/670</link>
<pubDate>Sun, 01 Mar 2020 13:01:09 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-670</guid>
<source url="https://forum.mesg.com/t/mesg-ecosystem-online-hackathon-win-up-to-9k/670.rss">MESG Ecosystem Online Hackathon - Win up to $9k</source>
</item>
<item>
<title>MESG Economy</title>
<dc:creator><![CDATA[Nicolas]]></dc:creator>
<category>Development</category>
<description><![CDATA[
<p>Hey guys, I want to create a unique topic that group everything anyone (developers and users) need to know about the token economy within the network.</p>
<p>This is also the place for anyone to ask questions and give feedback so we can improve the explanations.</p>
<p>First, read Anthony’s article that explains the overview of the economy:<br>
<aside class="onebox whitelistedgeneric">
<header class="source">
<img src="https://forum.mesg.com/uploads/default/original/1X/092bad48c2cf6eea80b04d60235188fb8d9c5af1.png" class="site-icon" width="" height="">
<a href="https://blog.mesg.com/token-utility-in-the-mesg-economy/" target="_blank" title="03:32AM - 19 February 2020">MESG – 19 Feb 20</a>
</header>
<article class="onebox-body">
<img src="https://forum.mesg.com/uploads/default/original/1X/f441ecbae6471eb65a08e8ce08a707468f8081bc.jpeg" class="thumbnail" width="" height="">
<h3><a href="https://blog.mesg.com/token-utility-in-the-mesg-economy/" target="_blank">Token Utility in the MESG Economy</a></h3>
<p>Explore the utility of the MESG Token, how it is used in the builders' open economy, and what it can mean for you.</p>
</article>
<div class="onebox-metadata">
</div>
<div style="clear: both"></div>
</aside>
</p>
<h2>Glossary</h2>
<p>I will start by explaining the different pieces that are needed to make the system works.</p>
<h3>Node</h3>
<p>A node is a computer that is running a specific software and that connects to other nodes running the same software to create a network.</p>
<h3>Transaction</h3>
<p>In a blockchain, transactions are created by users or software to ask the network to perform actions. Actions can be to transfer some token, to publish a service or to ask the network to execute an execution. A transaction requires to be cryptographically signed by a wallet that already has tokens to pay for gas fees (do not confuse transactions’ gas fees and execution’s fees). A transaction is considered as valid ONLY when it has been included in a valid block.</p>
<h3>Block</h3>
<p>A block is a list of transactions that have been validated by the creator(s) of the block.<br>
In <a href="https://en.wikipedia.org/wiki/Proof_of_stake">POS</a> blockchains, blocks are created by a group of block producers. A block producer is a node that MUST verify every new transaction, agree with other block producers on which transactions will be part of the new block, and finally signed cryptographically the block. Then the block (containing the transactions) is sent to every node of the network so they can apply locally the actions contained in each transaction. That’s how each node of the network synchronizes with the rest of the network.<br>
The network’s node will only accept block produced by block producers they already know. So the reliability and the stability of block producers are super important.</p>
<h3>Execution</h3>
<p>Executions are the centerpiece of the project. They are what “connect” the users, services, runners and bring the value to the project.<br>
Executions are composed of 3 resources.</p>
<h4>Execution’s request</h4>
<p>An execution’s request is a transaction from a user that requests a specific runner to execute a specific service’s task with specific inputs, alongside a fee to pay the runner and the service developer.<br>
Users can select manually the runner that will execute the execution or let the engine auto-select based on the runners’ stake and how much fee the runner wants and the user is willing to pay.</p>
<h4>Execution’s result</h4>
<p>Once the specified runner executes the execution, it submits the execution’s result by creating a new transaction containing the result and the hash of the execution’s request and submit it to the network.<br>
The block producers can only check that the result respects the structure of data defined by the service. That’s why we need a third step to verify the execution’s result.</p>
<h4>Execution’s verification</h4>
<p>Once the execution’s result is submitted and integrated into a block, the real execution’s verification step can occur.<br>
A group of runners that also run the same service is selected to verify if the result is valid.</p>
<p>The verification process depends on the type of service and in some case is not possible.</p>
<ul>
<li>In the case of a deterministic task, like a mathematical problem, they do this by either re-executing the same execution and checking the result is the same</li>
<li>In the case of an action against a public database, like a blockchain or twitter, they can check that the action happened</li>
<li>In the case of an action to a private service or an API that cannot be verified, then the verification step is not happening and we refer to the task as <strong>trusted</strong> as users will have to trust the runner to do the work correctly.</li>
</ul>
<p><strong>A question to discuss:</strong> what name do you think is the best: validation/validator or verification/verifier? I like verification/verifier because it separates it from other existing validation (transaction validation, block validation, etc…) and also it seems to be less strong than validation and makes the user more aware of the importance of this step.</p>
<h3>Service</h3>
<p>A service is a software that communicates with the Engine to emit events when needed and to execute tasks when the network needs to.<br>
The events and tasks of the service are defined in the service’s definition.<br>
A service is published to the network by a developer by creating a bundle of the software and its definition. When the service is published, anyone can download it and run it on its node as a runner.<br>
A service cannot be deleted from the network.</p>
<h3>Runner</h3>
<p>A runner is a node that downloads a service, runs it locally and registers itself to the network as a runner of this service. Runners will have to provide token as a stake when registering to prove their good willing and be slashed in case of malicious behavior.<br>
The runner will process executions the network is asking it to do and get paid for it.<br>
A runner can unregister itself from the network and get back the remaining of its stake.<br>
A single node can have many runners at the same time. The only issue by running too many services at the same time is computation resources. If the node is overloaded, it will not be able to keep synchronizing the network and runs the services in good condition, so it will be slashed.</p>
<h3>Process</h3>
<p>A process is an application that defines which tasks to execute when a specific event occurs on behalf of a user. Processes are run by emitters across the network. Each process has a token balance that is used to pay to create executions. Users need to make sure their processes have enough balance if they want them to run correctly.</p>
<h3>Emitter</h3>
<p>Emitters are responsible for creating executions by following the rules from processes.<br>
To reduce the charge of the network, each emitter is only running against its node’s runners. It means that runners of a specific service will also be an emitter of the same service. That’s why we group emitters inside runners.<br>
Emitters pay the transaction’s fee (not the full execution fees) to create the execution request on behalf of the process and get reimbursed plus an incentive.</p>
<hr>
<p>I’m stopping here for today but I will continue with a very detailed explanation of the execution lifecycle.</p>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/mesg-economy/664">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/mesg-economy/664</link>
<pubDate>Sun, 23 Feb 2020 10:17:57 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-664</guid>
<source url="https://forum.mesg.com/t/mesg-economy/664.rss">MESG Economy</source>
</item>
<item>
<title>Token Utility in the MESG Economy</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><em>This article describes the utility of the MESG Token and what it means for you.</em></p>
<p>The MESG Token is the fuel for the MESG Network, and its primary use is to create executions. MESG is a blockchain of executions and any node on the network can process executions and get rewarded for their work. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/token-utility-in-the-mesg-economy/">https://blog.mesg.com/token-utility-in-the-mesg-economy/</a></small>
<p><small>3 posts - 2 participants</small></p>
<p><a href="https://forum.mesg.com/t/token-utility-in-the-mesg-economy/661">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/token-utility-in-the-mesg-economy/661</link>
<pubDate>Wed, 19 Feb 2020 03:55:31 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-661</guid>
<source url="https://forum.mesg.com/t/token-utility-in-the-mesg-economy/661.rss">Token Utility in the MESG Economy</source>
</item>
<item>
<title>MESG Product Update - February '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>The new testnet was published on January 15th, 2020. It uses four validators spread around the world.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/mesg-product-update-february-20/">https://blog.mesg.com/mesg-product-update-february-20/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/mesg-product-update-february-20/658">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/mesg-product-update-february-20/658</link>
<pubDate>Tue, 18 Feb 2020 05:34:10 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-658</guid>
<source url="https://forum.mesg.com/t/mesg-product-update-february-20/658.rss">MESG Product Update - February '20</source>
</item>
<item>
<title>CTA card download</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/02b53d8b-a0bf-4569-bf63-b097ad311ead/">https://blog.mesg.com/p/02b53d8b-a0bf-4569-bf63-b097ad311ead/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/cta-card-download/655">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/cta-card-download/655</link>
<pubDate>Sun, 16 Feb 2020 07:48:27 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-655</guid>
<source url="https://forum.mesg.com/t/cta-card-download/655.rss">CTA card download</source>
</item>
<item>
<title>MESG Product Update - February '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>We’ve been quite busy over the past few months shipping the testnet and updating to ATD v2. Additionally, we received an Aragon Nest grant and shipped our first milestone for the integration.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/bcba904a-a055-4e91-919d-3687c706ba5c/">https://blog.mesg.com/p/bcba904a-a055-4e91-919d-3687c706ba5c/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/mesg-product-update-february-20/653">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/mesg-product-update-february-20/653</link>
<pubDate>Fri, 14 Feb 2020 11:43:11 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-653</guid>
<source url="https://forum.mesg.com/t/mesg-product-update-february-20/653.rss">MESG Product Update - February '20</source>
</item>
<item>
<title>ATD Report: February 2020</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p><em>The table below shows the number of MESG Tokens to be released in March per day per wallet.</em></p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/atd-report-february-2020/">https://blog.mesg.com/atd-report-february-2020/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/atd-report-february-2020/652">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/atd-report-february-2020/652</link>
<pubDate>Fri, 14 Feb 2020 11:06:05 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-652</guid>
<source url="https://forum.mesg.com/t/atd-report-february-2020/652.rss">ATD Report: February 2020</source>
</item>
<item>
<title>ATD Report: February 2020</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>The MESG Foundation’s commitment to transparency continues this month with the release of February 2020’s ATD and Financial Report. This report outlines the daily rates for March 2020, along with a financial report as a means of justification.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/0afed732-80b8-4b2a-aeef-3a84335a5e65/">https://blog.mesg.com/p/0afed732-80b8-4b2a-aeef-3a84335a5e65/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/atd-report-february-2020/651">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/atd-report-february-2020/651</link>
<pubDate>Fri, 14 Feb 2020 10:39:39 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-651</guid>
<source url="https://forum.mesg.com/t/atd-report-february-2020/651.rss">ATD Report: February 2020</source>
</item>
<item>
<title>Community Update - Early February '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-early-february-20/">https://blog.mesg.com/community-update-early-february-20/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-early-february-20/650">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-early-february-20/650</link>
<pubDate>Fri, 14 Feb 2020 08:20:44 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-650</guid>
<source url="https://forum.mesg.com/t/community-update-early-february-20/650.rss">Community Update - Early February '20</source>
</item>
<item>
<title>Community Update - Early February '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p class="subscribe-overlay-description">Stay up to date! Get all the latest & greatest posts delivered straight to your inbox</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/a88c241f-1c75-4d67-a61e-10b8ff80f688/">https://blog.mesg.com/p/a88c241f-1c75-4d67-a61e-10b8ff80f688/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-early-february-20/649">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-early-february-20/649</link>
<pubDate>Fri, 14 Feb 2020 07:29:20 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-649</guid>
<source url="https://forum.mesg.com/t/community-update-early-february-20/649.rss">Community Update - Early February '20</source>
</item>
<item>
<title>Why the MESG Token</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>The goal of this article is to describe the utility of the MESG and what it means for you if you already have some now. </p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/p/de879b35-0da6-4f31-bd23-9bdc6c95c88c/">https://blog.mesg.com/p/de879b35-0da6-4f31-bd23-9bdc6c95c88c/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/why-the-mesg-token/647">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/why-the-mesg-token/647</link>
<pubDate>Thu, 13 Feb 2020 05:05:03 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-647</guid>
<source url="https://forum.mesg.com/t/why-the-mesg-token/647.rss">Why the MESG Token</source>
</item>
<item>
<title>Aragon DAO / MESG Integration: Milestone 1</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>We've just reached the first milestone of the <a href="https://github.com/aragon/nest/issues/190">MESG integration with Aragon DAOs</a>, while also starting the first iteration of our <a href="http://explorer.testnet.mesg.com/">testnet</a> running on Tendermint.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/aragon-dao-integration/">https://blog.mesg.com/aragon-dao-integration/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/aragon-dao-mesg-integration-milestone-1/639">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/aragon-dao-mesg-integration-milestone-1/639</link>
<pubDate>Tue, 04 Feb 2020 07:24:04 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-639</guid>
<source url="https://forum.mesg.com/t/aragon-dao-mesg-integration-milestone-1/639.rss">Aragon DAO / MESG Integration: Milestone 1</source>
</item>
<item>
<title>Community Update - Late Jan '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>To stay up to date on MESG’s latest developments, join our<a href="https://forum.mesg.com/?source=post_page---------------------------"> Forum</a> or chat with us on<a href="http://discord.mesg.com/"> Discord</a>. Advanced users, head to<a href="https://github.com/mesg-foundation/engine/pulse?source=post_page---------------------------"> Github</a>. Plus, if you have suggestions or improvements, feel free to make a<a href="https://github.com/mesg-foundation/engine?source=post_page---------------------------"> pull request</a>. MESG is open source and community-driven.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-late-jan-20/">https://blog.mesg.com/community-update-late-jan-20/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-late-jan-20/636">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-late-jan-20/636</link>
<pubDate>Fri, 31 Jan 2020 11:00:06 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-636</guid>
<source url="https://forum.mesg.com/t/community-update-late-jan-20/636.rss">Community Update - Late Jan '20</source>
</item>
<item>
<title>ATD Report: January 2020</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>The end of January marks the beginning of the implementation of the ATD V2 system, <a href="https://blog.mesg.com/atd-version-2/">as announced last month</a>.</p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/atd-report-january-2020/">https://blog.mesg.com/atd-report-january-2020/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/atd-report-january-2020/630">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/atd-report-january-2020/630</link>
<pubDate>Fri, 24 Jan 2020 10:04:50 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-630</guid>
<source url="https://forum.mesg.com/t/atd-report-january-2020/630.rss">ATD Report: January 2020</source>
</item>
<item>
<title>Community Update- Early Jan '20</title>
<dc:creator><![CDATA[Anthony]]></dc:creator>
<category>Blog discussions</category>
<description><![CDATA[
<p>Happy New Year! We're starting off 2020 with a new Testnet and processes that enable on-demand payments, notifications, analytics and more. Plus, we're hard at work on a new growth-hacking strategy, expanding functionalities of highly-active projects through a simple web interface. <strong>Here's what we've been up to lately:</strong></p>
<hr>
<small>This is a companion discussion topic for the original entry at <a href="https://blog.mesg.com/community-update-early-january-20/">https://blog.mesg.com/community-update-early-january-20/</a></small>
<p><small>1 post - 1 participant</small></p>
<p><a href="https://forum.mesg.com/t/community-update-early-jan-20/622">Read full topic</a></p>
]]></description>
<link>https://forum.mesg.com/t/community-update-early-jan-20/622</link>
<pubDate>Thu, 16 Jan 2020 03:44:54 +0000</pubDate>
<discourse:topicPinned>No</discourse:topicPinned>
<discourse:topicClosed>No</discourse:topicClosed>
<discourse:topicArchived>No</discourse:topicArchived>
<guid isPermaLink="false">forum.mesg.com-topic-622</guid>
<source url="https://forum.mesg.com/t/community-update-early-jan-20/622.rss">Community Update- Early Jan '20</source>
</item>
</channel>
</rss>