vtnerd: excellent!

<xmr-romine> > <ErCiccione[m]> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it

<xmr-romine> > <ErCiccione[m]> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it

<xmr-romine> You want to go from private gitlab to github ?

<xmr-romine> > <ErCiccione[m]> sgp_: would be cool to host the website on the Monero Ecosystem if you are up for it

<xmr-romine> You want to go from private gitlab to github ?

xmr-romine: the Monero Ecosystem project is and has always been on GitHub: github.com/monero-ecosystem

<xmr-romine> <ErCiccione[m]> Indeed. I read you wrong. Apologies.

Lovely - twitter.com/kmlefranc/status/1221869659139366912?s=19

Remember there's a community meeting in a about 3 hours

Not sure if I can make the community meeting, added my thoughts here: repo.getmonero.org/monero-project/c…posals/merge_requests/115#note_8788

16:06 <sgp_> Remember there's a community meeting in a about 3 hours <-- I think you are off by 1 hour

When is it? 52 minutes?

Or an hour 52

lol.

MOTD: Community meeting this Saturday at 17 UTC.

it's 17:09 UTC.

Oh

Well

Happy community meeting!

9am is a little early, 10 or 11 would be nicer

Should be in 50 minutes. I might be a bit late today

<3

We can push 52m? Or two hours if people were going off of sgp

18utc or 19utc guys?

o darn I was thinking in 50 mins

Speak now or forever hold your peace

sorry, I dropped the ball

Boooo

19 utc it is

Wait isn't it in 50 minutes?

*18 utc

Almutasim may not be able to join if it's later

ErCiccione[m]: I did the same thing

He's traveling but is able to make the first half

OK, I will return at 19

last week messed me up, with events at 16:30 utc and 19 utc

*18 utc

lol.

sorry everyone, meeting in 50 minutes

<3

19 utc.

It's 19.

goddammit needmonero90.

Y topic say 18 utc

cuz it's 18 utc.

I guess i have my calendar set to utc+1. Stupid timezones

it's currently 17:12 utc right?

positive.

so meeting in 50 mins at 18 utc

Oh

Ok

hahahaha

Nods

Timezones are lame

Isn't there some bot that provides useful info? Can it also be used for UTC time?

dam time zones coordinating for Monero's failure!

!time

.time

& there lol

^

.top

<intj440> reddit posts had meeting @ 17:00 reddit.com/r/Monero/comments/ewir53…rkgroup_meeting_1_february_1700_utc

Lol

intj440 I messed up so it's actually at 18 utc now, sorry

<intj440> ok no worries

By the power of decentralization

.time

niiiiice

yes very, very nice

China has one timezone

y not Monero

i read this a while ago. was quite interesting perspective

a calendar would fix this wouldnt it? nobody would need to mentally do time again.

well i guess one person would.

kinghat: we tried that and it wasn't implemented in a good enough way. We will need to retry at some point

But the biggest issue is getting people to subscribe to the calendar notifications

biggest issue seems getting the time correct

in this case at least 3 people were off lol. that's not usua

*usual

so having some notification to say "meeting in 2 hours" or whatever could help

at 15 utc I even posted a reminder in here saying the meeting was in 3 hours haha

sure but calendars can notify you wherever on all your devices. even those not on IRC. which you understand.

yeah, I mean calendar notifications

id say just tossing it on a cloud calendar until there is a self hosted one would be fine.

even if its someones personal one

sgp_ used to do a cloud calendar

we did that for a bit and people complained, but I definitely should do that again

if it's ical (or whatever the standard is) you can import it to other applications and get updates

but then someone needs to keep it updated

Would be nice if GitHub/GitLab had this functionality

I can make a google account for @monerocommunity.org so it no longer comes up as ehrenhofer.org

actually, @communityworkgroup.org

Are there 3rd party solutions that will do ical endpoints?

Then you don't need any kind of googly account

google does, it's great

you can export to pretty much anything

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.

just something that will offer ical

Sure, but the "you" needs to be willing/able to do this

and take care of one-off meetings

and cancel things last-minut

or do time changes

Would be great to have a solution that could delegate workgroups' events to them, but still present a single ical

i mean coming in all the rooms and pasting the notifications takes just as long when its all set up.

let me work on setting this up now actually

ya that last part would be neato

dont know if that exists but it probably does.

looks like gitlab themselves use google calendar: about.gitlab.com/handbook/tools-and-tips/#google-calendar

Meeting at 18? Oof.

Please no google :(

let's stay privacy focused.

Can someone try this link? calendar.google.com/calendar?cid=aX…AZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ

ErCiccione[m]: if you want to host it, be my guest :)

wants me to sign in lol

nioc: ok, let me try something else

Monero Community Workgroup Calendar

sgp_: i can see it but im logged in

can see it in private mode as well

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"

github issues are used

Our fealty lies with Microsoft, then?

i understand it's the easier option. I just find weird to use an anti-privacy platform to advocate a privacy focused technologies

And not Google?

well, we are trying to move away from both no? Are we discussing to which privacy-nightmare company we would better sell ourselves ? :P

If that's the choice, Microsoft is marginally better than Google

Marginally

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

its easier and its now. as compared to the months it will most likely take to get something self hosted.

How about smoke signals? Those are decentralized

anyway, it's meeting time (sorry about the delay!)

fwiw we've already waited months :/

0. Introduction

We would like to welcome everyone to this Monero Community Workgroup Meeting!

Link to agenda on GitHub: monero-project/meta #435

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.

1. Greetings

hello

Hi

Hi

welcome everyone

sorry again for the delay

next meeting at normal time (1 hour before this)

2. Community highlights

It's 18:00 on a Saturday, the regular crowd shuffles in

See Monero weekly highlights at revuo-monero.com

Does anyone have community (non-workgroup) updates to share?

I'll take that as a no

I gave a podcast in Spanish youtube.com/watch?v=zZaf5ps7Lzs&feature=youtu.be

oh sweet, nice ArticMine!

good stuff

Awesome.

you should be on rottensox and anhdres's podcast

3. CCS updates

Funding required:

3 months part time work on Getmonero.org ccs.getmonero.org/proposals/ErCiccione-website-jan-march.html (150.26 / 174 XMR)

v1docq47: video creation / translations into russian (february - july 2020) (6.04 / 100 XMR) ccs.getmonero.org/proposals/%20v1do…o-russian-(february-july-2020).html

Ideas (to be discussed):

Locha Mesh, private transactions and sync over a resilient long-range radio mesh network repo.getmonero.org/monero-project/ccs-proposals/merge_requests/115

lots of comments on this one over the weeks

this specific proposal seems to have general support from binaryfate, selsta, and xmrhaelan

among a few others

and as far as I can tell, ErCiccione[m] and rehrar have outstanding concerns

not really from my side

they plan for recurring funding which I’m against

Myself as well (concerns) but I have not vocalized them in the thread.

My concerns are mostly satisfied at this point.

selsta: against recurring, but you would be ok with this one? I'm trying to understand your viewpoint

I would be comfortable seeing this as a trial period. And if we like them and they like us, integrate them into our project.

rehrar: noted, thanks

needmonero90 and ErCiccione[m], can we please hear your concerns

Integrating them is a bad idea IMO.

The project can be interesting, but gives me the feeling that it need way more than 3 months before we see some concrete development

They are not a Monero project and wouldn’t be here without funding

^

We also have to ask ourselves how many people are actually going to utilize the integration

^

indeed, it's a niche solution to be honest

19:09 <sgp_> 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.

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.

but presumably donors would know that? should that be clearer?

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

Where is the limit? Someone creating an operating system that at one point will run Monero, would that be something for the CCS?

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

I am also a bit worried it might exhaust donors

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

We've already had periods were projects took quite some time to get funded

dEBRUYNE: this is my biggest concern.

We have some big ones coming up too. suraeNoether needs to put his in.

dEBRUYNE: That's a very legit concern. I know the pain of seeing your proposal not funded for months

(it's still not fully funded)

Also, let's be real, funding three conferences a year, plus several quarterlies is, I think, the limit of the system.

Along with a smattering of small one-offs.

Without a pamp at least

^ very valid

Even then we risk over extending for a future bear tho

For this reason alone, I vote no.

A future bear is likely to be weaker than this one

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

I get that this is a nonessential need

In contentious cases like this we leave to Luigi.

I am very much on the fence on this.

I'll be giving a full report to him on our talks here and on the gitlab

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"

Can do.

any other discussions that are new info or new arguments before we wrap up this topic?

None here

ok, thanks for your patience as this one took a bit of time to discuss over the past several weeks

A Monero-centric Merchant Marketplace repo.getmonero.org/monero-project/ccs-proposals/merge_requests/117

Is endogenic around?

any comments on this one? up for a week now

I think endogenic might have a similar project, would be curious to know if he's seen that

item number 7; seems fairly similar to what rbrunner had in mind. koe weighs in on this there.

Wait wrong person

Wasn't endo, lemme contact them

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

Part Time Research Atoc (pending update) repo.getmonero.org/monero-project/ccs-proposals/merge_requests/120

this one is stalled, no discussion needed

xiphon part-time coding repo.getmonero.org/monero-project/ccs-proposals/merge_requests/122

does anyone oppose this one? contributor with a track record looking to increase their involvement 50%

I believe that atoc is presently interested in the XMR-BTC swap proposal from h4sh3d

sarang: I think we can discuss that one when it's updated so we have more to discuss

for the record: who supports xiphon's proposal?

I do

you all are quiet today! many of you commented on gitlab expressing support

19:23 <sgp_> does anyone oppose this one? contributor with a track record looking to increase their involvement 50% <-- AFAIK his previous CCS was already 20h/week

unless I misremember

this one is 30 hrs

20 -> 30

ah

:)

didn’t see that :P

Developer proposals from existing contributors are a safe bet in my books. So yes

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%

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

Contributors*

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

coordinators?

Yeah, like the mrl

They act as human buffers

mrl is contributing tho

For the people who contribute their time and effort for free

we have never done that?

unless I’m missing some discussion

I'm speaking about our funding of the researchers, when other people like isthmus don't get CCSed

Basically, the researchers have an availability expectation

He hasn't asked. :P

needmonero90: are you suggesting a form of leadership role (likely in addition to contributions)?

Exactly

I've been referring to them as coordinators

sounds unnecessary for the GUI

Them = that role

ah, got it

And coordinators are really the place where funding makes sense

I think in this case the gui workgroup hasn't really formed this way, but maybe they will in the future

I mean, they kinda have in practice

I'm on the fence about funding regular contributors with no availability/coordination expectation

I disagree with that.

I think that's a strong stance

I disagree too

and that's not how the ccs work right now fwiw

needmonero90: I wouldn't say mooo has an availability/coordination expectation.

but I acknowledge the benefit of prioritizing leadership roles

He does sometimes, but not all the time. He just codes for the most part.

I've been trying to figure out an internally consistent structure for the CCS in my own head

I realize it's not how it works atm

ah ok :)

I say yay on xiphon.

needmonero90: I think it's an interesting check, but as you acknowledged, there will need to be exceptions as we figure this out :)

We don’t need paid GUI contributors that have expected availability.

We need contributors that code :)

One that doesn't open itself up to random people putting pressure on getting their proposal merged so they get a seal of approval

I think we're done on xiphon discussion

and the CCS stuff

We need contributors that code -> we need contributors.

we got through a lot this week, good job everyone

4. Workgroup report

We need contributors -> We need

We.

lol

not we, just I need

I need money

a. Daemon/CLI workgroup

vtnerd made a PR for the last major hurdle for dandelion++ support! ++

90

I saw that.

That's kind of super exciting.

better network privacy even without tor/i2p

cool stuff

Exciting enough to do a point release with it?

Once merged, I mean.

rehrar: will probably take time to merge, so who knows! :)

that's the biggest thing I saw but I'm sure there was more I missed

There are network benefits even without full adoption, FWIW

At least a day, for sure.

sarang, can MRL look over the implementation and give their thoughts?

yeah, partial is hugely beneficial here

though we should expect large adoption at the next hardfork

I added it to the top of my list as soon as I saw it late yesterday

we definitely need to write a blog post after the PR is merged

b. Localization workgroup

I expect it will be discussed at the next MRL meeting

ErCiccione[m]: absolutely

marketing 101

ErCiccione: you're up now :)

This is actually kinda huge.

cool

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)

hi

and the strings for the GUI got updated

so if you speak another language, get in there and translate all the things

translate.getmonero.org

getmonono.org

there should be about 40 new strings

Sneaky Computer Bucks

and ike 30 removed, but i'm going by memory, could totally be the other way round

that's basically it. Waiting for a PR to be merged in the core repo, so translators can work on the CLI as well

Is CLI currently untranslated?

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

Oh I understand

this is the PR: monero-project/monero #6312

there is also a brief summary of the work of the translators that is being committed

Spanish is only 9% done? Rottensox slackin

so basically after that is merged the new strings will be picked up and people can start to translate the CLI again

that's the normal workflow

needmonero90: sorry... translation isn't my expertise. actually, i have no specialization.

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

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

so how does D++ work with Tor or I2P?

kinghat: let's table that question for now

anything else ErCiccione?

nope

I have two related things I'll mention here

Mastering Monero was translated to Chinese: zh.masteringmonero.com

It was also translated to Russian and needs reviewers: monerobook/monerobook #81

the second one was part of the CCS request that is outstanding

that's actually super cool. Great job to all involved

c. GUI workgroup

Binaries for the point release are still not out yet. github.com/monero-project/monero-gui/releases/tag/v0.15.0.3

no idea what the status is there honestly

Did you ping the telegram channel on the review sgp?

but I haven't been paying close attention

I can drop the link there if you haven't

needmonero90: not yet but I need to

oh, please do :)

d. Outreach workgroup

thunderosa: please give your update

Sure, so I have Almutasim's update first that I'll copy and paste

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:

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)

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.

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.

And advice was given on other ways of individual contribution, such as through mining, running a Monero node, and donating.

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

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.

damn.

they told me before there would be a wall of text, and I recommended getting it all out quickly :)

Well,..so the real wall is coming

and I'm sorry,..but it's a big update.

pastebin?

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.

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,

Spoke, as FOSS and some modernizing and organizing was needed.

sarang: to some extent it's good to have it actually in the logs rather than an external site that will go away

holy cats!

sorry about that

Anyway, there's alot going on,...TLDR: We're serverless and going to finally finish the Community Calendar on it

ay

haha just as I made a temporary solution

(sorry, misclicked)

Well, I have been very late in delivering it, and for that I'm sorry.

But this is the right way to build it.

the non-google calendar is very welcome :P

yeah, we can take Google in if we want,..but I'd really rather avoid using G at all for our projects.

like Google Calendar API in

as a source

no please don't. My point is to not use google

Yeah, I'd like to start with just humans and see how good we can make that before automating too much.

the outreach post on RPC-Pay was awesome 🙏

^ agree. Would be cool to make a user guide for getmonero out of it

Thank you, Alumtasim did a really amazing job making that happen and leading our workgroup into some new ideas through it.

thanks for the update thunderosa

I echo statements that rpc-pay was great

nice, simple name too

any other outreach comments?

put the new cal link in the topic?

Nope that's the load. We'll be posting updates mid next week.

great, thanks for the updates here

skipping hardware since msvb seems away, can come back if needed

f. Konferenco workgroup

Expect an announcement this Monday. But as a sneak peek, the Konferenco is June 13-14 in Berlin.

but yeah, be ready Monday

g. Monero Research Lab

sarang

Hi

Plenty of topics under discussion recently

One of note is CLSAG

We'd planned for an earlier audit, but got great review comments from a conference submission

If there is still good support for deployment, I recommend an audit still

However, I also recommend not having someone directly involved with the work coordinate the audit

to mitigate conflicts of interest

sgp_ suggested an audit workgroup

General thoughts on this initial idea?

I've reached out to a few names to judge interest

but the intent is to use the workgroup to help coordinate the clsag audits

maybe I can answer questions about that after sarang, continue

The timing of the audit depends on (a) security model updates to the preprint; (b) availability of reviewers; (c) timeline of selection/fundraising

Is conflict of interest a realistic threat? Can you explain?

I think it's always a good idea to keep in mind

selsta: there are also a few related goals, like drafting writeups of the results, etc

I think it sets a good standard of impartiality going forward

I agree

As a reminder, the benefits of CLSAG are ~25% reduction in typical tx size, and ~15-20% verification savings

The only quote we received last time for a math+code audit was about 15000 USD

this was from Teserakt

via OSTIF?

Anyway, that's the big research item of timely community interest that I wished to share

ArticMine: yes

thanks sarang

may I jump in?

That's another conflict of interest, since I've participated in an OSTIF advisory committee :)

it was a busy MRL week, so follow their github if interested: github.com/monero-project/research-lab/issues

UkoeHB_: sure briefly :)

Yes, many issues that we'd been looking at (and new ones) are now listed there as issues

Here is the current roadmap containing others’ ideas and my ideas, most of which need more discussion so please feel free to leave thoughts pdf-archive.com/2020/02/01/moneroro…oe020120/moneroroadmapkoe020120.pdf

OpenBazaar integration was investigated by rbrunner in 2019 but met some technological roadblocks. I have been engineering solutions to those problems, which should hopefully be fleshed out over the next weeks. The solutions would be beneficial to any Monero based marketplace that wants to operate with minimal trust requirements.

^ koe's personal roadmap

Sarang has helped me design a monero-style coinjoin protocol, named TxTangle, which is mostly done.

yes

(don't view it as endorsement by anyone else)

nice

This may be a bit off-topic for this group, but at some point it should be decided when the next network upgrade should occur, given CLSAG and other changes of possible interest

CLSAG is a consensus change

D++ is not

but simultaneous release would help adoption

sarang: good point, we will need to talk about that later though

Yeah, I know it's running late :/

thanks UkoeHB_

ErCiccione: would you like to give a website update?

yes

go ahead

i guess we are running late so i'll be superquick

3 things:

1. Logs of meetings are not being submitted on getmonero. We miss quite a lot of logs of meeting happened in the last months. If somebody want to help submitting some, that would be very appreciated

2. We really really need people to review pull request on monero-site. Some of my PR are still waiting for a review after more than one month. Some of them are also trivial

^ please take a look and review if you can

3. Two of these PR need to be merged asap because without them i cannot put getmonero on weblate. The PR are:

That's it. Please review stuff or the development of the website will be slowed down

thank you

5. Open ideas time

Just one thing: xenugrande recommended “doing some sort of one day rally as part of the festivities for the yearly Monero anniversary. I received enthusiasm for it to possibly act as a fundraiser for the Monero research team, as well as doing some sort of "black friday" type of event where we would reach out directly to merchants/vendors to coordinate deals for people using Monero.”

Last year we did the online event. We still need to plan that event, so we can make that a community meeting topic or a separate meeting.

vcool UkoeHB_!

Monero's anniversary falls on a Saturday this year, so it's easy to plan

Look for a Moneroversary issue in the next week on the meta repo to collect ideas

Any final essential thoughts?

6. Confirm next meeting date/time

The next community meeting will be in 2 weeks on 15 February at 17:00 UTC.

The next Coffee Chat is next week on 8 February at 17:00 UTC.

New calendar(mahy now be very temporary haha) (please configure reminders if they don’t copy over!): calendar.google.com/calendar/embed?…oaogsuk%40group.calendar.google.com

7. Conclusion

That’s all! Thanks for attending this Monero Community meeting, and we hope to see you on r/MoneroCommunity and #monero-community. Take care, and know that change starts with YOU.

thanks sgp_

ErCiccione[m]: I've got most of them in my logs from irccloud

If you want to sort through this channel, I can provide them.

sgp_: Russian community has been informed, we have some people who will take a look.

They made fun of my Google translate use :(

poor needmonero90.

Cool, but they will probably need a bit of tweaking to be markdown-compatible. Elooruobuob_ had a script for that iirc, but i haven't seen them around for quite some time

wait it's el00ruobuob_

needmonero90: could you send me the irccloud logs of this meeting? I'll see how much work that needs first, but i already have an headache if i think of manually converting all the past meetings logs :P

ErCiccione[m]: gist.github.com/selsta/1082f90ae3fc7ce3af414e93ba37287a

but it still needs some manual editing afterwards

Interesting... I always use the four-spaces indent trick for GitHub markdown

and thereby avoid any manual editing :)

selsta: thanks!

sarang: yeah, but it also has to deal with jekyll's markdown. I will see

markdown is non-fungible, eh?

=p

Seems like every implementation is a little different, just enough to be irritating

yeah. Somebody decided to standardize markdown creating an universal implementation... and that's how you get just another implementation

there was a funny comic stripe about it

zing

That's it! You are quick :P

When are we going to do the next upgrade (aka, HF)? I don't think anything was planned after the last discussion (6 or 9 months had forks). If we are going to save ~25% of space for each transaction, better do it earlier than later

we cannot have that space back

I am waiting to hear back from suraeNoether for some preprint changes he wished to make (and approval on my earlier overhaul)

and then the audit process, should the workgroup choose to do it

I believe there's dev work ongoing to enforce full block reward

yeah, but the question still remains. Maybe we can postpone the discussion for when everything will be ready, but it's not clear to me what the core team decided about the timing

If CLSAG is a must-have, perhaps they wish to wait

Thanks needmonero90