"[XMR] Monero - The Future: Fungible, Wild, Free || Mandatory: v0.9.1"
Fixed?
"[XMR] Monero - We Have Ponies and Moos || ZOMG Mandatory ZOMG: v0.9.1"
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 692. (Read 4671660 times)
January 25, 2016, 02:39:33 AM
Fixed?
"[XMR] Monero - We Have Ponies and Moos || ZOMG Mandatory ZOMG: v0.9.1"
January 24, 2016, 09:18:58 PM
binaryFate, simple and neat. I have learned to always give great weight to what you say whether they are small things or of great importance.
smooth, good points. How best to do this?
iCEBREAKER, yes cryptocurrency is redundant. After reading many posts on bct it seems that people don't really know what fungibility is so I don't know if it is a key selling point. After all btc is fungable
so therefore I guess all cryptocurrencies are. Please take the emoticon as irony, sarcasm or whatever emotion I was trying for
I just felt it was important to get every on board properly. Taking into account those that do not spend enough time to know all that is going on and those that are relatively new.
Then there are the slow ones. This post took me over 1/2 an hour.
Thank you for your consideration, The Drooling Masses™
smooth, good points. How best to do this?
iCEBREAKER, yes cryptocurrency is redundant. After reading many posts on bct it seems that people don't really know what fungibility is so I don't know if it is a key selling point. After all btc is fungable
so therefore I guess all cryptocurrencies are. Please take the emoticon as irony, sarcasm or whatever emotion I was trying for I just felt it was important to get every on board properly. Taking into account those that do not spend enough time to know all that is going on and those that are relatively new.
Then there are the slow ones. This post took me over 1/2 an hour.
Thank you for your consideration, The Drooling Masses™
I vote for Hueristic's enigmatic submission.
"[XMR] Monero - The Future, Fungible || Mandatory: v0.9.1"
People don't know what 'fungible' means because it has several (overlapping/conflicting/contextual/technical/economic/casual/controversial/radial) definitions.
That intriguing vagueness is a good thing.
People don't know exactly why being 'fungible' is so important , but they know it's from the future and they want it!
January 24, 2016, 08:35:10 PM
binaryFate, simple and neat. I have learned to always give great weight to what you say whether they are small things or of great importance.
smooth, good points. How best to do this?
iCEBREAKER, yes cryptocurrency is redundant. After reading many posts on bct it seems that people don't really know what fungibility is so I don't know if it is a key selling point. After all btc is fungable so therefore I guess all cryptocurrencies are. Please take the emoticon as irony, sarcasm or whatever emotion I was trying for
I just felt it was important to get every on board properly. Taking into account those that do not spend enough time to know all that is going on and those that are relatively new.
Then there are the slow ones. This post took me over 1/2 an hour.
Thank you for your consideration, The Drooling Masses™
smooth, good points. How best to do this?
iCEBREAKER, yes cryptocurrency is redundant. After reading many posts on bct it seems that people don't really know what fungibility is so I don't know if it is a key selling point. After all btc is fungable
so therefore I guess all cryptocurrencies are. Please take the emoticon as irony, sarcasm or whatever emotion I was trying for I just felt it was important to get every on board properly. Taking into account those that do not spend enough time to know all that is going on and those that are relatively new.
Then there are the slow ones. This post took me over 1/2 an hour.
Thank you for your consideration, The Drooling Masses™
January 24, 2016, 08:13:41 PM
"[XMR] Monero - The Future: Fungible, Wild, Free || Mandatory: v0.9.1"
Fixed?
January 24, 2016, 08:04:41 PM
"[XMR] Monero - The Future, Fungible || Mandatory: v0.9.1"
January 24, 2016, 07:50:52 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
"[XMR] Monero - Secure, private, untraceable, fungible. || Latest: v0.9.1"
By context we know it's a cryptocurrency, and (100%) fungibility is a key selling point.
January 24, 2016, 07:32:06 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The the slogan out for now (or if not now, maybe a month from now). Put it back after the fork.
Also, I like presenting it as "mandatory by [date]" which not like "ZOMG WE'RE ALL GONNA DIE" and more of an advance notice, especially since the voting stuff isn't fully implemented (in the future the wallet/node should provide a notice automatically).
January 24, 2016, 07:25:20 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
"[XMR] Monero - A secure, private, untraceable cryptocurrency || Latest: v0.9.1"
January 24, 2016, 07:15:58 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
If you can delete, the original title has about three dozen dispensable characters. The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
January 24, 2016, 07:14:34 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
"[XMR] Monero - A secure, private, untraceable currency || Version 0.9.1"
mebbe
January 24, 2016, 07:11:35 PM
A small complication with updating the OP, input requested.
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
The max length of the title is 80 chars. Currently we are at 60 chars with "[XMR] Monero - A secure, private, untraceable cryptocurrency". Adding " || Latest Version: " already adds 20 chars.
Suggestions?
updated by fluffypony
January 24, 2016, 06:47:42 PM
...- Bonus question: Sorry I forgot, why again was I2P once preffered over TOR to be integrated/used with Monero?
Maybe someone can remind me or point to a link, where I can read it up myself.
Maybe someone can remind me or point to a link, where I can read it up myself.
Probably because Tor is widely accepted as being cracked by TPTB. But something is better than nothing so go for it in the mean time.
I believe there is no reason not to have the mandatory notice on the bct announce page OP.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
It's not a mandatory update from 0.9, but it is a mandatory update from 0.8.x. A fresh sync with 0.9 works just fine, a lot of 0.9 nodes aren't on the bad fork any longer (longest chain rule), and the 1 or 2 nodes that still seem to (bizarrely) be stuck will figure out they need to update.
Re: the thread title, with the mandatory hard fork policy every update is mandatory. We can put the latest version in the title, but I'm not sure it's necessary to use the word mandatory - thoughts?
I completely agree with Nioc.
January 24, 2016, 05:51:48 PM
I believe there is no reason not to have the mandatory notice on the bct announce page OP.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
It's not a mandatory update from 0.9, but it is a mandatory update from 0.8.x. A fresh sync with 0.9 works just fine, a lot of 0.9 nodes aren't on the bad fork any longer (longest chain rule), and the 1 or 2 nodes that still seem to (bizarrely) be stuck will figure out they need to update.
Re: the thread title, with the mandatory hard fork policy every update is mandatory. We can put the latest version in the title, but I'm not sure it's necessary to use the word mandatory - thoughts?
On reddit the thread titled "MANDATORY UPGRADE for everyone that is running v0.9.0 - Hydrogen Helix" is stickied so I assumed something like that should be noted here.
As far as going forward, I assume our constant hardfork policy is unique and I think each time a new hardfork comes out that the proper action required should be communicated as hopefully we will have new users each hardfork.
Thank you for everything fluffypony
BTW I didn't win the lottery today but I collected enough cans and bottles for the next drawing
I added the mandatory part to the thread because on the day itself it was kind of necessary for everyone to upgrade. After that, fluffypony stickied the thread and I can't change the topic title.
More info about the hard fork schedule: https://forum.getmonero.org/4/academic-and-technical/303/a-formal-approach-towards-better-hard-fork-management
I agree with smooth here btw.
January 24, 2016, 05:21:25 PM
I believe there is no reason not to have the mandatory notice on the bct announce page OP.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
It's not a mandatory update from 0.9, but it is a mandatory update from 0.8.x. A fresh sync with 0.9 works just fine, a lot of 0.9 nodes aren't on the bad fork any longer (longest chain rule), and the 1 or 2 nodes that still seem to (bizarrely) be stuck will figure out they need to update.
Re: the thread title, with the mandatory hard fork policy every update is mandatory. We can put the latest version in the title, but I'm not sure it's necessary to use the word mandatory - thoughts?
On reddit the thread titled "MANDATORY UPGRADE for everyone that is running v0.9.0 - Hydrogen Helix" is stickied so I assumed something like that should be noted here.
As far as going forward, I assume our constant hardfork policy is unique and I think each time a new hardfork comes out that the proper action required should be communicated as hopefully we will have new users each hardfork.
Thank you for everything fluffypony
BTW I didn't win the lottery today but I collected enough cans and bottles for the next drawing
January 24, 2016, 04:20:49 PM
I believe there is no reason not to have the mandatory notice on the bct announce page OP.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
It's not a mandatory update from 0.9, but it is a mandatory update from 0.8.x. A fresh sync with 0.9 works just fine, a lot of 0.9 nodes aren't on the bad fork any longer (longest chain rule), and the 1 or 2 nodes that still seem to (bizarrely) be stuck will figure out they need to update.
Re: the thread title, with the mandatory hard fork policy every update is mandatory. We can put the latest version in the title, but I'm not sure it's necessary to use the word mandatory - thoughts?
The policy is valid but this being the first one I would say the point should be emphasized a bit. The older version is going to stop working in two months, after being current for well over a 1 year. We should make clear that the time to upgrade is now.
January 24, 2016, 04:02:56 PM
Want to finally try this coin. What wallet is better?
One that you keep safe. If you're ok running a full node, the standard command line wallet is certainly a good pick.Is there any good web wallets like blockchain's for bitcoin?
-> MyMonero <-These are the ones available:
https://getmonero.org/getting-started/choose
January 24, 2016, 08:51:52 AM
Want to finally try this coin. What wallet is better?
One that you keep safe. If you're ok running a full node, the standard command line wallet is certainly a good pick.Is there any good web wallets like blockchain's for bitcoin?
-> MyMonero <- 
January 24, 2016, 08:47:58 AM
Want to finally try this coin. What wallet is better? Is there any good web wallets like blockchain's for bitcoin?
January 24, 2016, 07:59:27 AM
I believe there is no reason not to have the mandatory notice on the bct announce page OP.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
Those type of notices used to be in the title of the thread.
I understand it says "We are moving away from Bitcointalk" in the OP but still this is critical info. This type of info used to be in the title of this thread.
It's not a mandatory update from 0.9, but it is a mandatory update from 0.8.x. A fresh sync with 0.9 works just fine, a lot of 0.9 nodes aren't on the bad fork any longer (longest chain rule), and the 1 or 2 nodes that still seem to (bizarrely) be stuck will figure out they need to update.
Re: the thread title, with the mandatory hard fork policy every update is mandatory. We can put the latest version in the title, but I'm not sure it's necessary to use the word mandatory - thoughts?
January 24, 2016, 07:57:38 AM
Reading the quote "While Monero isn't made to integrate with Tor, it can be used wrapped with torsocks, if you add --p2p-bind-ip 127.0.0.1 to the bitmonerod command line." in README.md at the repo, leads me to the following questions:
- Whats the status of this TOR-support via wrapper? Is this option: fully functioning and secure to use for people with basic TOR & crypto knowledge. Or this more like an draft/proof of concept/not supported dirty hack?
- Are more Monero I2P-nodes needed?
- Are more Monero TOR-nodes needed?
- In which clearnet geographical region are new nodes needed? Any suggestions?
(Without needs test, I randomly did setup 4 nodes in Asia yesterday: Hong Kong, Kuala Lumpur, Singapore and Kota Kinabalu[MY].)
So next time, I get pocket money from my grandmother and I decide to buy more nodes, I would deploy them, where they are needed. :-)
- Bonus question: Sorry I forgot, why again was I2P once preffered over TOR to be integrated/used with Monero?
Maybe someone can remind me or point to a link, where I can read it up myself.
- Whats the status of this TOR-support via wrapper? Is this option: fully functioning and secure to use for people with basic TOR & crypto knowledge. Or this more like an draft/proof of concept/not supported dirty hack?
- Are more Monero I2P-nodes needed?
- Are more Monero TOR-nodes needed?
- In which clearnet geographical region are new nodes needed? Any suggestions?
(Without needs test, I randomly did setup 4 nodes in Asia yesterday: Hong Kong, Kuala Lumpur, Singapore and Kota Kinabalu[MY].)
So next time, I get pocket money from my grandmother and I decide to buy more nodes, I would deploy them, where they are needed. :-)
- Bonus question: Sorry I forgot, why again was I2P once preffered over TOR to be integrated/used with Monero?
Maybe someone can remind me or point to a link, where I can read it up myself.
Smooth already answered your first questions.
Anyway, you can see the geographical distribution of Monero nodes here -> https://monerohash.com/#network
Regarding bonus question: I would suggest to listen to the podcast -> http://podbay.fm/show/1032156854/e/1451151298?autostart=1
They discuss it in there.
Jump to: