02:24:34 vtnerd: excellent! 06:18:20

> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it 06:19:02

> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it 06:19:03

You want to go from private gitlab to github ? 06:19:17

> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it 06:19:23

You want to go from private gitlab to github ? 10:19:59 xmr-romine: the Monero Ecosystem project is and has always been on GitHub: https://github.com/monero-ecosystem 10:56:14

Indeed. I read you wrong. Apologies. 13:58:21 Lovely - https://twitter.com/kmlefranc/status/1221869659139366912?s=19 13:58:21 [ bruise almighty on Twitter: "I had to get a background check for my job, and it turns out the report is a 300+ page pdf of every single tweet I’ve ever liked with the work “fuck” in it. Enjoy your d ] - twitter.com 15:06:50 Remember there's a community meeting in a about 3 hours 16:34:31 Not sure if I can make the community meeting, added my thoughts here: https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/115#note_8788 17:01:57 * rottensox whistles 17:03:03 16:06 Remember there's a community meeting in a about 3 hours <-- I think you are off by 1 hour 17:08:52 When is it? 52 minutes? 17:08:57 Or an hour 52 17:09:01 lol. 17:09:15 MOTD: Community meeting this Saturday at 17 UTC. 17:09:24 it's 17:09 UTC. 17:09:29 Oh 17:09:33 Well 17:09:37 Happy community meeting! 17:09:47 9am is a little early, 10 or 11 would be nicer 17:09:56 Should be in 50 minutes. I might be a bit late today 17:10:03 <3 17:10:09 We can push 52m? Or two hours if people were going off of sgp 17:10:11 https://www.timeanddate.com/worldclock/timezone/utc 17:10:32 18utc or 19utc guys? 17:10:37 o darn I was thinking in 50 mins 17:10:38 Speak now or forever hold your peace 17:10:42 sorry, I dropped the ball 17:10:46 Boooo 17:10:53 19 utc it is 17:10:57 Wait isn't it in 50 minutes? 17:10:57 *18 utc 17:10:58 Almutasim may not be able to join if it's later 17:11:01 * needmonero90 shames Justin for good measure 17:11:17 ErCiccione[m]: I did the same thing 17:11:18 He's traveling but is able to make the first half 17:11:29 OK, I will return at 19 17:11:33 last week messed me up, with events at 16:30 utc and 19 utc 17:11:35 *18 utc 17:11:37 lol. 17:11:48 sorry everyone, meeting in 50 minutes 17:11:55 <3 17:12:01 19 utc. 17:12:04 It's 19. 17:12:07 goddammit needmonero90. 17:12:25 Y topic say 18 utc 17:12:35 cuz it's 18 utc. 17:12:36 I guess i have my calendar set to utc+1. Stupid timezones 17:12:43 it's currently 17:12 utc right? 17:12:47 positive. 17:12:54 so meeting in 50 mins at 18 utc 17:12:55 Oh 17:12:57 Ok 17:12:59 hahahaha 17:13:03 * needmonero90 node in confusion 17:13:05 Nods 17:13:16 Timezones are lame 17:13:20 Isn't there some bot that provides useful info? Can it also be used for UTC time? 17:13:26 dam time zones coordinating for Monero's failure! 17:13:50 !time 17:13:54 .time 17:13:54 2020-02-01 - 17:13:54 17:14:02 & there lol 17:14:04 ^ 17:14:05 .top 17:14:05 Total market cap $264B | 1. BTC $171B | 2. ETH $20B | 3. XRP $10B | 4. BCH $7.0B | 5. BSV $5.1B | 6. USDT $4.6B | 7. LTC $4.5B | 8. EOS $4.0B | 9. BNB $2.8B | 10. ADA $1.4B | 11. ETC $1.3B | 12. XMR $1.3B | 13. TRX $1.2B | 14. XLM $1.2B | 15. XTZ $1.2B | 16. DASH $1.1B | 17. LINK $983.8M | 18. LEO $864.5M | 19. ATOM $828.0M | 20. MIOTA $824.9M 17:14:07 reddit posts had meeting @ 17:00 https://www.reddit.com/r/Monero/comments/ewir53/community_workgroup_meeting_1_february_1700_utc/ 17:14:07 Lol 17:14:09 [REDDIT] Community Workgroup Meeting: 1 February 17:00 UTC (https://github.com/monero-project/meta/issues/435) to r/Monero | 6 points (88.0%) | 0 comments | Posted by SamsungGalaxyPlayer | Created at 2020-01-31 - 04:23:21 17:14:22 intj440 I messed up so it's actually at 18 utc now, sorry 17:14:47 ok no worries 17:14:56 By the power of decentralization 17:15:37 .time 17:15:37 2020-02-01 - 17:15:37 17:15:41 niiiiice 17:15:52 * sarang learned a new thing today 17:15:54 yes very, very nice 17:21:05 China has one timezone 17:21:10 y not Monero 17:33:00 i read this a while ago. was quite interesting perspective 17:33:10 https://www.wired.co.uk/article/universal-time-zones 17:33:11 a calendar would fix this wouldnt it? nobody would need to mentally do time again. 17:33:16 well i guess one person would. 17:35:31 kinghat: we tried that and it wasn't implemented in a good enough way. We will need to retry at some point 17:35:47 But the biggest issue is getting people to subscribe to the calendar notifications 17:36:25 biggest issue seems getting the time correct 17:37:05 in this case at least 3 people were off lol. that's not usua 17:37:08 *usual 17:37:25 so having some notification to say "meeting in 2 hours" or whatever could help 17:38:00 at 15 utc I even posted a reminder in here saying the meeting was in 3 hours haha 17:38:23 sure but calendars can notify you wherever on all your devices. even those not on IRC. which you understand. 17:38:35 yeah, I mean calendar notifications 17:38:54 id say just tossing it on a cloud calendar until there is a self hosted one would be fine. 17:39:16 even if its someones personal one 17:39:26 sgp_ used to do a cloud calendar 17:39:27 we did that for a bit and people complained, but I definitely should do that again 17:39:58 if it's ical (or whatever the standard is) you can import it to other applications and get updates 17:40:36 but then someone needs to keep it updated 17:40:58 Would be nice if GitHub/GitLab had this functionality 17:41:01 I can make a google account for @monerocommunity.org so it no longer comes up as ehrenhofer.org 17:41:23 actually, @communityworkgroup.org 17:41:40 Are there 3rd party solutions that will do ical endpoints? 17:41:49 Then you don't need any kind of googly account 17:41:51 google does, it's great 17:42:01 you can export to pretty much anything 17:42:01 i mean you can plaster out a year or more of dates in like one click. then alter them monthly or whatever if the times change. everyones calendars should update accordingly. 17:42:03 just something that will offer ical 17:42:18 Sure, but the "you" needs to be willing/able to do this 17:42:31 and take care of one-off meetings 17:42:42 and cancel things last-minut 17:42:45 or do time changes 17:43:12 Would be great to have a solution that could delegate workgroups' events to them, but still present a single ical 17:43:21 i mean coming in all the rooms and pasting the notifications takes just as long when its all set up. 17:43:42 let me work on setting this up now actually 17:43:43 ya that last part would be neato 17:44:14 dont know if that exists but it probably does. 17:46:52 looks like gitlab themselves use google calendar: https://about.gitlab.com/handbook/tools-and-tips/#google-calendar 17:48:21 Meeting at 18? Oof. 17:50:18 Please no google :( 17:50:31 let's stay privacy focused. 17:52:34 Can someone try this link? https://calendar.google.com/calendar?cid=aXRtYXJhdWJrZm9lNGFxMm9xdW9hb2dzdWtAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ 17:52:49 ErCiccione[m]: if you want to host it, be my guest :) 17:54:35 wants me to sign in lol 17:54:45 nioc: ok, let me try something else 17:55:12 https://calendar.google.com/calendar/embed?src=itmaraubkfoe4aq2oquoaogsuk%40group.calendar.google.com 17:55:54 Monero Community Workgroup Calendar 17:56:24 sgp_: i can see it but im logged in 17:56:41 can see it in private mode as well 17:56:53 * needmonero90 saunters in 17:57:18 sgp_: no need to self host it if that's what you meant. I just think that would be very weird to advocate for privacy and then say to the community: "do you want to follow when the meeting of the community workggroup are going to happen? you can do that, but not without giving your info to google" 17:57:59 github issues are used 17:58:16 Our fealty lies with Microsoft, then? 17:58:18 i understand it's the easier option. I just find weird to use an anti-privacy platform to advocate a privacy focused technologies 17:58:20 And not Google? 17:58:54 well, we are trying to move away from both no? Are we discussing to which privacy-nightmare company we would better sell ourselves ? :P 17:59:16 If that's the choice, Microsoft is marginally better than Google 17:59:18 Marginally 17:59:24 ideally we would use something else, but I'm using this for now since it's better than nothing. I'll still announce the workgroup meetings the typical ways 17:59:36 its easier and its now. as compared to the months it will most likely take to get something self hosted. 17:59:40 How about smoke signals? Those are decentralized 17:59:47 anyway, it's meeting time (sorry about the delay!) 17:59:56 fwiw we've already waited months :/ 18:00:01 0. Introduction 18:00:05 We would like to welcome everyone to this Monero Community Workgroup Meeting! 18:00:09 Link to agenda on GitHub: https://github.com/monero-project/meta/issues/435 18:00:13 Monero Community meetings are a discussion place for anything going on in the Monero Community, including other Monero workgroups. We use meetings to encourage the community to share ideas and provide support. 18:00:18 1. Greetings 18:00:48 hello 18:01:04 * needmonero90 waves 18:01:18 Hi 18:01:36 Hi 18:02:39 welcome everyone 18:02:43 sorry again for the delay 18:02:52 next meeting at normal time (1 hour before this) 18:02:57 2. Community highlights 18:02:59 It's 18:00 on a Saturday, the regular crowd shuffles in 18:03:01 See Monero weekly highlights at https://revuo-monero.com 18:03:05 Does anyone have community (non-workgroup) updates to share? 18:04:24 I'll take that as a no 18:04:25 I gave a podcast in Spanish https://www.youtube.com/watch?v=zZaf5ps7Lzs&feature=youtu.be 18:04:25 [ Monero Swaps para anonimizar Bitcoin con ArticMine - L47 - YouTube ] - www.youtube.com 18:04:35 oh sweet, nice ArticMine! 18:04:52 good stuff 18:05:10 Awesome. 18:05:10 you should be on rottensox and anhdres's podcast 18:05:30 3. CCS updates 18:05:34 Funding required: 18:05:39 3 months part time work on Getmonero.org https://ccs.getmonero.org/proposals/ErCiccione-website-jan-march.html (150.26 / 174 XMR) 18:05:43 v1docq47: video creation / translations into russian (february - july 2020) (6.04 / 100 XMR) https://ccs.getmonero.org/proposals/%20v1docq47-video-creation-translations-into-russian-(february-july-2020).html 18:05:50 Ideas (to be discussed): 18:05:54 Locha Mesh, private transactions and sync over a resilient long-range radio mesh network https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/115 18:06:04 lots of comments on this one over the weeks 18:07:33 this specific proposal seems to have general support from binaryfate, selsta, and xmrhaelan 18:07:41 among a few others 18:07:58 and as far as I can tell, ErCiccione[m] and rehrar have outstanding concerns 18:08:11 not really from my side 18:08:24 https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/115#note_8788 18:08:29 they plan for recurring funding which I’m against 18:08:31 Myself as well (concerns) but I have not vocalized them in the thread. 18:08:46 My concerns are mostly satisfied at this point. 18:09:07 selsta: against recurring, but you would be ok with this one? I'm trying to understand your viewpoint 18:09:11 I would be comfortable seeing this as a trial period. And if we like them and they like us, integrate them into our project. 18:09:15 rehrar: noted, thanks 18:09:39 needmonero90 and ErCiccione[m], can we please hear your concerns 18:09:45 Integrating them is a bad idea IMO. 18:10:01 The project can be interesting, but gives me the feeling that it need way more than 3 months before we see some concrete development 18:10:03 They are not a Monero project and wouldn’t be here without funding 18:10:18 ^ 18:10:28 We also have to ask ourselves how many people are actually going to utilize the integration 18:10:34 ^ 18:10:43 indeed, it's a niche solution to be honest 18:10:48 19:09 selsta: against recurring, but you would be ok with this one? I'm trying to understand your viewpoint <-- In general I’m against it as it is not related to Monero but I would be ok with one time funding. 18:10:48 selsta, perhaps. I'm not for them being integrated necessarily. I'm against them getting money unless they are one of us, was my point. 18:11:03 but presumably donors would know that? should that be clearer? 18:12:00 my concerns with it being niche are related to the donors knowing that, not necessarily a hold on moving the CCS if that makes sense 18:12:09 Where is the limit? Someone creating an operating system that at one point will run Monero, would that be something for the CCS? 18:12:43 I think i'm leaning more to selsta's point of view. A continuous funding of a project without clear benefits doesn;t sound like a good idea, especially since we will see the real benefits in a very long time, not at the end of the 3 months 18:12:51 I am also a bit worried it might exhaust donors 18:12:58 selsta: I don't want to get too into the weeds, but there is an associated marketing opportunity and clear prioritization for a tool built for Monero I suppose. These would need to be addressed case-by-case 18:13:00 We've already had periods were projects took quite some time to get funded 18:13:05 dEBRUYNE: this is my biggest concern. 18:13:20 We have some big ones coming up too. suraeNoether needs to put his in. 18:13:34 dEBRUYNE: That's a very legit concern. I know the pain of seeing your proposal not funded for months 18:13:50 (it's still not fully funded) 18:13:57 Also, let's be real, funding three conferences a year, plus several quarterlies is, I think, the limit of the system. 18:14:26 Along with a smattering of small one-offs. 18:14:36 Without a pamp at least 18:15:08 ^ very valid 18:15:08 Even then we risk over extending for a future bear tho 18:15:31 For this reason alone, I vote no. 18:16:17 A future bear is likely to be weaker than this one 18:16:28 as a CCS moderator, it's hard for me to weigh the concern about burdening donors in a way that's fair. it's entirely subjective in terms of what to move 18:16:55 I get that this is a nonessential need 18:17:15 In contentious cases like this we leave to Luigi. 18:17:21 I am very much on the fence on this. 18:17:46 I'll be giving a full report to him on our talks here and on the gitlab 18:17:53 rehrar: can you tell luigi I lean yes move with donor disclaimers (they know it's a fun, ambitious, "extra" project), and that you "vote no" 18:18:05 Can do. 18:18:25 any other discussions that are new info or new arguments before we wrap up this topic? 18:19:11 None here 18:19:18 ok, thanks for your patience as this one took a bit of time to discuss over the past several weeks 18:19:26 A Monero-centric Merchant Marketplace https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/117 18:20:07 Is endogenic around? 18:20:09 any comments on this one? up for a week now 18:20:37 I think endogenic might have a similar project, would be curious to know if he's seen that 18:21:16 https://www.pdf-archive.com/2020/01/29/moneroroadmapkoe012920/moneroroadmapkoe012920.pdf 18:21:16 item number 7; seems fairly similar to what rbrunner had in mind. koe weighs in on this there. 18:21:45 Wait wrong person 18:22:00 Wasn't endo, lemme contact them 18:22:30 doesn't seem like there's much discussion here yet, so we should review on gitlab and encourage them to do another round of reddit to increase exposure to the idea 18:22:52 Part Time Research Atoc (pending update) https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/120 18:23:01 this one is stalled, no discussion needed 18:23:10 xiphon part-time coding https://repo.getmonero.org/monero-project/ccs-proposals/merge_requests/122 18:23:27 does anyone oppose this one? contributor with a track record looking to increase their involvement 50% 18:23:38 I believe that atoc is presently interested in the XMR-BTC swap proposal from h4sh3d 18:24:18 sarang: I think we can discuss that one when it's updated so we have more to discuss 18:24:28 for the record: who supports xiphon's proposal? 18:24:57 I do 18:25:09 you all are quiet today! many of you commented on gitlab expressing support 18:25:15 19:23 does anyone oppose this one? contributor with a track record looking to increase their involvement 50% <-- AFAIK his previous CCS was already 20h/week 18:25:20 unless I misremember 18:25:32 this one is 30 hrs 18:25:43 20 -> 30 18:25:51 ah 18:25:54 :) 18:25:58 didn’t see that :P 18:26:05 Developer proposals from existing contributors are a safe bet in my books. So yes 18:26:19 I personally looked to make sure that there are plenty of plans to-do to fill the time, and it seems to be the case 100% 18:26:24 Xiphon does valuable work, though I'm also curious how far we can stretch donated time. In the past I've tried to come to grips with the difference between people who are coordinators (availability expectations) and regular controvutors 18:26:29 Contributors* 18:27:02 Right now I'm in favor of the proposal, though it's inconsistent with my previously expressed stance that we should only be paying coordinators 18:27:13 coordinators? 18:27:30 Yeah, like the mrl 18:27:35 They act as human buffers 18:27:48 mrl is contributing tho 18:27:49 For the people who contribute their time and effort for free 18:28:10 we have never done that? 18:28:21 unless I’m missing some discussion 18:28:23 I'm speaking about our funding of the researchers, when other people like isthmus don't get CCSed 18:28:51 Basically, the researchers have an availability expectation 18:28:51 He hasn't asked. :P 18:29:14 needmonero90: are you suggesting a form of leadership role (likely in addition to contributions)? 18:29:21 Exactly 18:29:29 I've been referring to them as coordinators 18:29:29 sounds unnecessary for the GUI 18:29:32 Them = that role 18:29:34 ah, got it 18:29:50 And coordinators are really the place where funding makes sense 18:29:53 I think in this case the gui workgroup hasn't really formed this way, but maybe they will in the future 18:30:10 I mean, they kinda have in practice 18:30:14 I'm on the fence about funding regular contributors with no availability/coordination expectation 18:30:17 I disagree with that. 18:30:30 I think that's a strong stance 18:30:34 I disagree too 18:30:47 and that's not how the ccs work right now fwiw 18:30:50 needmonero90: I wouldn't say mooo has an availability/coordination expectation. 18:30:51 but I acknowledge the benefit of prioritizing leadership roles 18:31:09 He does sometimes, but not all the time. He just codes for the most part. 18:31:18 I've been trying to figure out an internally consistent structure for the CCS in my own head 18:31:24 I realize it's not how it works atm 18:31:37 ah ok :) 18:31:49 I say yay on xiphon. 18:31:53 needmonero90: I think it's an interesting check, but as you acknowledged, there will need to be exceptions as we figure this out :) 18:31:57 We don’t need paid GUI contributors that have expected availability. 18:32:02 We need contributors that code :) 18:32:05 One that doesn't open itself up to random people putting pressure on getting their proposal merged so they get a seal of approval 18:32:11 I think we're done on xiphon discussion 18:32:21 and the CCS stuff 18:32:25 We need contributors that code -> we need contributors. 18:32:32 we got through a lot this week, good job everyone 18:32:38 4. Workgroup report 18:32:41 We need contributors -> We need 18:32:45 We. 18:32:48 lol 18:32:54 not we, just I need 18:32:59 I need money 18:33:03 a. Daemon/CLI workgroup 18:33:12 vtnerd made a PR for the last major hurdle for dandelion++ support! ++ 18:33:13 90 18:33:24 I saw that. 18:33:30 That's kind of super exciting. 18:33:36 better network privacy even without tor/i2p 18:33:40 cool stuff 18:33:49 Exciting enough to do a point release with it? 18:33:56 Once merged, I mean. 18:34:08 rehrar: will probably take time to merge, so who knows! :) 18:34:18 that's the biggest thing I saw but I'm sure there was more I missed 18:34:18 There are network benefits even without full adoption, FWIW 18:34:21 At least a day, for sure. 18:34:45 sarang, can MRL look over the implementation and give their thoughts? 18:34:48 yeah, partial is hugely beneficial here 18:35:05 though we should expect large adoption at the next hardfork 18:35:06 I added it to the top of my list as soon as I saw it late yesterday 18:35:28 we definitely need to write a blog post after the PR is merged 18:35:29 b. Localization workgroup 18:35:30 I expect it will be discussed at the next MRL meeting 18:35:34 ErCiccione[m]: absolutely 18:35:40 marketing 101 18:35:48 ErCiccione: you're up now :) 18:35:51 This is actually kinda huge. 18:36:00 cool 18:36:50 nothing too big. I'm waiting for 2 PR to be merged in the getmonero repo before starting to use weblate for the website (i will speak about it more in the report of the website workgroup) 18:37:03 hi 18:37:07 and the strings for the GUI got updated 18:37:18 so if you speak another language, get in there and translate all the things 18:37:22 translate.getmonero.org 18:37:31 getmonono.org 18:37:34 there should be about 40 new strings 18:37:42 Sneaky Computer Bucks 18:37:51 and ike 30 removed, but i'm going by memory, could totally be the other way round 18:38:28 that's basically it. Waiting for a PR to be merged in the core repo, so translators can work on the CLI as well 18:38:55 Is CLI currently untranslated? 18:39:52 Not sure of what you mean. CLI is translatable on weblate, but not in this very moment, because the PR with the refresh and the translated strings need to be merged first, or there would be conflicts 18:40:13 Oh I understand 18:40:18 this is the PR: https://github.com/monero-project/monero/pull/6312 18:40:39 there is also a brief summary of the work of the translators that is being committed 18:41:33 Spanish is only 9% done? Rottensox slackin 18:41:36 so basically after that is merged the new strings will be picked up and people can start to translate the CLI again 18:41:40 that's the normal workflow 18:42:19 needmonero90: sorry... translation isn't my expertise. actually, i have no specialization. 18:42:30 yeah, cli doesn't see much action, but i'm kinda ok with it, i prefer most of the effort to be on the GUI and if there are energies left, CLI 18:43:37 rottensox: you don't need any specialization. I literally just learned english properly when i started to translate Monero stuff. But that's another story 18:43:55 so how does D++ work with Tor or I2P? 18:44:09 kinghat: let's table that question for now 18:45:05 anything else ErCiccione? 18:45:14 nope 18:45:26 I have two related things I'll mention here 18:45:29 Mastering Monero was translated to Chinese: zh.masteringmonero.com 18:45:34 It was also translated to Russian and needs reviewers: https://github.com/monerobook/monerobook/pull/81 18:45:51 the second one was part of the CCS request that is outstanding 18:45:58 that's actually super cool. Great job to all involved 18:46:08 c. GUI workgroup 18:46:12 Binaries for the point release are still not out yet. https://github.com/monero-project/monero-gui/releases/tag/v0.15.0.3 18:46:23 no idea what the status is there honestly 18:46:30 Did you ping the telegram channel on the review sgp? 18:46:32 but I haven't been paying close attention 18:46:36 I can drop the link there if you haven't 18:46:40 needmonero90: not yet but I need to 18:46:47 oh, please do :) 18:47:07 d. Outreach workgroup 18:47:13 thunderosa: please give your update 18:47:34 Sure, so I have Almutasim's update first that I'll copy and paste 18:47:48 In the second half of last year, Monero Outreach worked on story generation and publishing in several areas. The following were either edited or written by Monero Outreach during this period: 18:47:48 Response to Coinbase. On November 8, 2019, Coinbase blogged an article covering its views on Proof of Work (PoW), and the article made a number of incorrect points and reached an arguably inappropriate conclusion regarding Monero. Monero Outreach's fast-turnaround November 13 response corrected the errors and argued in favor of the ASIC-resistance path taken by Monero’s developers. Corrections included 1) 18:47:48 pointing out the article’s description of Monero’s efforts to prevent the use of ASICs as outdated and 2) countering adverse technical and philosophical arguments made regarding the benefits of ASICs. 18:47:49 Getting Started with Helping Monero. Monero Outreach created a document describing the many ways individuals can engage with the Monero community and support Monero. Resources for learning more about Monero and its technology were presented. The document included advice for software developers, with links to repositories, guides, and research results. It summarize Monero workgroups and social media outlets. 18:47:49 And advice was given on other ways of individual contribution, such as through mining, running a Monero node, and donating. 18:47:50 Monero in China and The West. Monero Outreach worked with Chinese Monero community member FutureFan to publish an article comparing the Monero communities of China and the West. FutureFan had previously worked with Monero Outreach by translating articles into Chinese. This new article talked about the relative sizes of the Monero communities and the difference in interest, with, for example, the West more 18:47:51 interested in philosophy and China more interested in mining. It presended a path forward to improve cooperation between the two communities and increase the use of Monero in China. This article, released just after the new year, was followed up with a Monero Talk interview that will be published as a video soon. 18:47:55 damn. 18:48:17 they told me before there would be a wall of text, and I recommended getting it all out quickly :) 18:48:30 Well,..so the real wall is coming 18:48:40 and I'm sorry,..but it's a big update. 18:48:48 pastebin? 18:49:02 But our main focus this time around was more on how we publish versus what we publish. Over the past year we've realized that much of the traffic we orchestrate for Monero never touches our servers and in fact the only things we actually need www for is SEO and thumbnail scraping for social media. We saw an opportunity to practice what we preach and decentralize our publishing. 18:49:02 With that in mind, we also had a basket of concrete design goals. A big focus was to setup Primo/RPC-Pay/Support Mining in an effort to help subsidize our hard costs. We also thought we were well-suited to be an RPC-Pay guinea pig publisher. It was also important that the Community Calendar and Merchant Directory projects would be furthered. Lastly, we wanted to prepare to release our publishing platform, 18:49:02 Spoke, as FOSS and some modernizing and organizing was needed. 18:49:05 sarang: to some extent it's good to have it actually in the logs rather than an external site that will go away 18:49:14 holy cats! 18:49:17 sorry about that 18:50:04 Anyway, there's alot going on,...TLDR: We're serverless and going to finally finish the Community Calendar on it 18:50:20 ay 18:50:21 haha just as I made a temporary solution 18:50:45 (sorry, misclicked) 18:50:50 Well, I have been very late in delivering it, and for that I'm sorry. 18:50:59 But this is the right way to build it. 18:51:02 the non-google calendar is very welcome :P 18:51:38 yeah, we can take Google in if we want,..but I'd really rather avoid using G at all for our projects. 18:51:51