Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1306. (Read 4671575 times)

It's free choice but practicality will win once again. people just don't care about esperanto or correct grammar that much and monero will be 'moneros' in plural for most people cause they simply don't care or don't know about the correct esperanto grammar, even though monero is an esperanto word meaning 'coin'.

I believe moneroj or moneros could be used equally. Technically moneroj is the correct plural because monero is an esperanto word. Many people also attach "s" to things they consider plural, like car(s). So it could potentially go both ways.

in brazilian portuguese it would be 'monerinhos'

the plural 'moneros' is perhaps better suited for mass appeal in the real world.. rather than 'moneroy'.. cryptocurrencies are already hard enough to understand for most people so it's better to keep it simple. the natural plural would be moneros for most people, without a doubt, naturally.
actually also spend some time checking up on esperanto, interesting stuff.

Original post is here

Monero Monday Missives

October 27th, 2014

Hello, and welcome to our sixteenth Monero Monday Missive!

Major Updates

1. We have made major strides in the initial database implementation (you'll recall from our last Missive that our first implementation will use LMDB), and it is very nearly ready for broader testing. Specifically: the new blockchain is working for most things, but there are bugs with certain aspects of block verification that need to be fixed before it can be more widely tested. If you are particularly intrepid you can already grab it here: https://github.com/tewinget/bitmonero/tree/blockchain and compile it, and thus assist in identifying areas where it breaks down, although such reports are probably best submitted as github issues to tewinget's repository to reduce duplication. Once these and any other major issues have been weeded out the next steps would involve a bit of refactoring, fix cross-platform nigglies, and open it up for general testing.

2. The testing of per-kb fees on testnet, too, has gone exceedingly well. We will be adding the functionality to simplewallet (previously it required manual creation) and hope to deploy that for general testing within the next week.

3. Kitware staff, Ben Boeckel in particular, have spent a lot of time completely reworking our CMake build system and bringing it up to best practices. The fruits of those efforts can be seen on the Pull Request currently undergoing testing: https://github.com/monero-project/bitmonero/pull/180 (feel free to checkout this PR if you'd like to test). Now that the build system is starting to come together in its final form, we are hoping to use it to tag and release 0.8.8.5 during the course of next week.

4. In order to more efficiently deal with changes in the on-disk wallet format we are moving away from the old serialised+encrypted .keys format, and have a new format which is effectively encrypted JSON. This change allows us to note the wordlist language in the wallet format (so that the "seed" command can reflect that choice) and allows for cross-platform compatibility of the .keys file, which we are sure is excellent news for anyone that moves wallets between operating systems and architectures. You can test this in PR 179.

5. There have been a constant string of improvements and changes to the forum software to make it more usable and useful. In particular, new comments in a thread are highlighted within that thread. Additionally, unread threads (or threads with new unread comments) are highlighted by having a green dot next to them. Both of these apply to logged in users only. If you haven't visited the forum, you are encouraged to do so: https://forum.monero.cc

Dev Diary

Core: LMDB implementation is rough but nearly working (details above). Worth testing cross-platform, least of all from a build perspective.

Core: since we have already had to perform the rather annoyingly complex task of offloading MoneroPulse checkpoint checks to a separate thread (so as not to tie anything up during checks) we have begun extending this to other parts of the core that could potentially be or currently are pain points. This does not include the flat-file blockchain saving, as that is going to be deprecated with the move to LMDB, so pools will just need to hang on and deal with that nuisance for a little bit longer.

Build: CMake is looking a lot cleaner and easier to grok. It also fixes cross-compile (see: http://www.cmake.org/Wiki/CMake_Cross_Compiling) which means that binaries for all our major supported platforms can be built on a single system.

Account: multilang wordlists are now inherent to the wallet/account, so that RPC and CLI calls that retrieve the mnemonic do so in the correct format. This has, in turn, necessitated moving away from the horrible serialised data format for account data. Since epee's JSON library is beyond redemption, we have opted to use RapidJSON instead (which is headers-only and thus straight in the source tree).

Until next week!

PS. this Missive has the very great honour of being the first one to be finalised and very nearly posted from the air

- updated by fluffypony

I am surprised the blockchain is already 2.1 GB 

Not, it's roy.
"As written" means nothing and is ethnocentric. How do you pronounce the Slovene first name Jana? As written? Well, for Slovene, "as written" is "yana", whilst for English natives, "as written" is "jana". Who is right? The Slovenes, since this is a Slovene first name.

Same here. Moneroj is Esperanto, so the Esperanto pronunciation applies, not the English ones.

And it is "moneroy" (source).

actually, I just looked it up.
The diminutive of "monero" is "monereto"  
And the plural is, off course, moneretoj  

moneritos makes me hungry too. I think of doritos  LOL

I think the issue is that the network hashrate is calculated from the diff, which is I think is based on blocks in the last 24 hours, I believe it's just (diff/(60*1024^2)), while I think the pools calculate their hashrate based on average diff of blocks in the last 10 or 30 minutes, so they are basing the two numbers on a different starting point. With that being said, it does seem strange how it always seems like the sum of the pools is greater than the reported network hashrate, but maybe that just has to do with the fact that I usually check it in the morning time of the USA.

If you look at the pie chart here: http://minexmr.com/pools.html
It says the network rate is 18.6 Mh/s while the sum of the known pools hashrate is 22 Mh/s, and that's not including solo miners as well as private/unknown pools

In any event, if you want to support the network, you probably shouldn't mine at moneropool.com, I think this much is obvious...

Moneritos makes me hungry. Sounds like biscuits to me 
It is perfect for a millionth of a monero, thanks to the crypto kingdom game for expanding this term.

I'm with you papa_lazzarou  
I think an English speaker would pronounce it -mo-ne-ro-ge- if matching the Portuguese pronunciation of Moneroj.

For some reason, I just like Moneritos so much better (as a general term, not as the plural of Monero).
I suppose it's just personal sentiment.

Found this - https://www.facebook.com/NumlEsperantoClub/posts/393130217458349

Well, in Portugal (or euro portuguese) we pronounce euros as euroj so its all the same to us.

This is not true on my system. I just launched the daemon and synced up and it's using less than 4.5 GB. Total RAM 32 GB; Win 8.1.

It's read as written, Moneroj. I don't know where you get that rosh or roy. It's ROJ.

Just for posterity:

On Monday I bought my first item with XMR, a guitar theory course at  http://www.guitartheoryrevolution.info for 35 XMR.

The transaction went well and the material is great so if anyone is interested in this kind of stuff support the guy

Ok, you are right  :p
No, it's indeed "Mo Ne Roy" (NOT MoanRoy)

It's an Esperanto word.