This is gentlemen!
Amazing work, the wallet looks fantastic!!
Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 1267. (Read 4671575 times)
November 25, 2014, 07:30:57 AM
November 25, 2014, 07:30:49 AM
November 25, 2014, 07:10:26 AM
Finally something that everyone can use. Its a shame about the view key but that wont matter too much to most people who this wallet will help out.
November 25, 2014, 07:06:43 AM
great something nice and visible thanks to the guys involved.
Globb0
November 25, 2014, 07:00:47 AM
very very nice work 
looks great
looks great
November 25, 2014, 06:35:27 AM
Great news. Thanks for the info and great job fluffypony. Just created an account!
November 25, 2014, 06:25:41 AM
Amazing guys! "My Monero" is awesome news, can't wait to try it out
Cross-posted from the official forum.
Quote
November 24th, 2014
Hello, and welcome to our nineteenth Monero Monday Missive!
Major Updates
1. It is with great pride that we announce the very first Monero hosted account service (a web wallet for Monero, if you will), which we are certain will provide a level of accessibility that was previously unknown with Monero. My Monero is managed by Riccardo "fluffypony" Spagni, although it was created through the efforts and hard work of many people including members of the Monero Core Team, Lucas Jones, Matthew Little, and seed funding provided by Risto Pietila. All of the heavy lifting is done client-side, which means that My Monero can never spend your funds on your behalf or without your authorisation. However, there is a small compromise in that the server knows your view key, which is necessary in order for it to identify transactions belonging to you. Thus there is some reduction in transactional privacy when using My Monero, as if the service is compromised your view key would be revealed. That having been said, stealth addresses would still be in effect even if the server was compromised, and thus transactions can still be said to be unlinkable. If you are truly concerned about absolute transactional privacy, then running your own Monero node will always be the preferred route.
2. Significant progress has been made to fixing the last few Windows build issues. KitWare have worked with us ensuring that our CMake is 100% up to their best practices, and the resulting 2 905 lines of new CMake (!!!) is evidence thereof: https://github.com/monero-project/bitmonero/pull/180/files. Now that we are seeing light at the end of the proverbial tunnel, we expect to tidy this up by the end of the week and can finally tag-and-release Monero 0.8.8.5.
3. We are working hard on solving the blockchain DB bugs as and where they are found. If all goes well we should have enough of the nuances worked out to have it merged into master within the next 4 weeks.
4. We have seen our QA (automated testing) / CI (Continuous Integration) / Gitian build efforts drag their heels extremely slowly over the past few months, mostly due to specialists in those fields originally interested in helping us finally not being able to commit to any significant period of assistance. We are stepping this up a notch with the assistance of a new contributor, Gazby in #monero-dev, who will focus on the devops work.
Dev Diary
Core: msys2 now successfully compiles static releases in PR 180, final testing of new builds will happen this week
Core: expect a mass merge of PRs previously waiting this week. If you have a PR with CMake changes in it expect it to be merged and fixed manually, but moving forward CMake changes will have to comply with the new, cleaner CMake.
Until next week!
updated by davidlatapieHello, and welcome to our nineteenth Monero Monday Missive!
Major Updates
1. It is with great pride that we announce the very first Monero hosted account service (a web wallet for Monero, if you will), which we are certain will provide a level of accessibility that was previously unknown with Monero. My Monero is managed by Riccardo "fluffypony" Spagni, although it was created through the efforts and hard work of many people including members of the Monero Core Team, Lucas Jones, Matthew Little, and seed funding provided by Risto Pietila. All of the heavy lifting is done client-side, which means that My Monero can never spend your funds on your behalf or without your authorisation. However, there is a small compromise in that the server knows your view key, which is necessary in order for it to identify transactions belonging to you. Thus there is some reduction in transactional privacy when using My Monero, as if the service is compromised your view key would be revealed. That having been said, stealth addresses would still be in effect even if the server was compromised, and thus transactions can still be said to be unlinkable. If you are truly concerned about absolute transactional privacy, then running your own Monero node will always be the preferred route.
2. Significant progress has been made to fixing the last few Windows build issues. KitWare have worked with us ensuring that our CMake is 100% up to their best practices, and the resulting 2 905 lines of new CMake (!!!) is evidence thereof: https://github.com/monero-project/bitmonero/pull/180/files. Now that we are seeing light at the end of the proverbial tunnel, we expect to tidy this up by the end of the week and can finally tag-and-release Monero 0.8.8.5.
3. We are working hard on solving the blockchain DB bugs as and where they are found. If all goes well we should have enough of the nuances worked out to have it merged into master within the next 4 weeks.
4. We have seen our QA (automated testing) / CI (Continuous Integration) / Gitian build efforts drag their heels extremely slowly over the past few months, mostly due to specialists in those fields originally interested in helping us finally not being able to commit to any significant period of assistance. We are stepping this up a notch with the assistance of a new contributor, Gazby in #monero-dev, who will focus on the devops work.
Dev Diary
Core: msys2 now successfully compiles static releases in PR 180, final testing of new builds will happen this week
Core: expect a mass merge of PRs previously waiting this week. If you have a PR with CMake changes in it expect it to be merged and fixed manually, but moving forward CMake changes will have to comply with the new, cleaner CMake.
Until next week!
November 25, 2014, 06:18:55 AM
Cross-posted from the official forum.
Quote
November 24th, 2014
Hello, and welcome to our nineteenth Monero Monday Missive!
Major Updates
1. It is with great pride that we announce the very first Monero hosted account service (a web wallet for Monero, if you will), which we are certain will provide a level of accessibility that was previously unknown with Monero. My Monero is managed by Riccardo "fluffypony" Spagni, although it was created through the efforts and hard work of many people including members of the Monero Core Team, Lucas Jones, Matthew Little, and seed funding provided by Risto Pietila. All of the heavy lifting is done client-side, which means that My Monero can never spend your funds on your behalf or without your authorisation. However, there is a small compromise in that the server knows your view key, which is necessary in order for it to identify transactions belonging to you. Thus there is some reduction in transactional privacy when using My Monero, as if the service is compromised your view key would be revealed. That having been said, stealth addresses would still be in effect even if the server was compromised, and thus transactions can still be said to be unlinkable. If you are truly concerned about absolute transactional privacy, then running your own Monero node will always be the preferred route.
2. Significant progress has been made to fixing the last few Windows build issues. KitWare have worked with us ensuring that our CMake is 100% up to their best practices, and the resulting 2 905 lines of new CMake (!!!) is evidence thereof: https://github.com/monero-project/bitmonero/pull/180/files. Now that we are seeing light at the end of the proverbial tunnel, we expect to tidy this up by the end of the week and can finally tag-and-release Monero 0.8.8.5.
3. We are working hard on solving the blockchain DB bugs as and where they are found. If all goes well we should have enough of the nuances worked out to have it merged into master within the next 4 weeks.
4. We have seen our QA (automated testing) / CI (Continuous Integration) / Gitian build efforts drag their heels extremely slowly over the past few months, mostly due to specialists in those fields originally interested in helping us finally not being able to commit to any significant period of assistance. We are stepping this up a notch with the assistance of a new contributor, Gazby in #monero-dev, who will focus on the devops work.
Dev Diary
Core: msys2 now successfully compiles static releases in PR 180, final testing of new builds will happen this week
Core: expect a mass merge of PRs previously waiting this week. If you have a PR with CMake changes in it expect it to be merged and fixed manually, but moving forward CMake changes will have to comply with the new, cleaner CMake.
Until next week!
updated by davidlatapie Hello, and welcome to our nineteenth Monero Monday Missive!
Major Updates
1. It is with great pride that we announce the very first Monero hosted account service (a web wallet for Monero, if you will), which we are certain will provide a level of accessibility that was previously unknown with Monero. My Monero is managed by Riccardo "fluffypony" Spagni, although it was created through the efforts and hard work of many people including members of the Monero Core Team, Lucas Jones, Matthew Little, and seed funding provided by Risto Pietila. All of the heavy lifting is done client-side, which means that My Monero can never spend your funds on your behalf or without your authorisation. However, there is a small compromise in that the server knows your view key, which is necessary in order for it to identify transactions belonging to you. Thus there is some reduction in transactional privacy when using My Monero, as if the service is compromised your view key would be revealed. That having been said, stealth addresses would still be in effect even if the server was compromised, and thus transactions can still be said to be unlinkable. If you are truly concerned about absolute transactional privacy, then running your own Monero node will always be the preferred route.
2. Significant progress has been made to fixing the last few Windows build issues. KitWare have worked with us ensuring that our CMake is 100% up to their best practices, and the resulting 2 905 lines of new CMake (!!!) is evidence thereof: https://github.com/monero-project/bitmonero/pull/180/files. Now that we are seeing light at the end of the proverbial tunnel, we expect to tidy this up by the end of the week and can finally tag-and-release Monero 0.8.8.5.
3. We are working hard on solving the blockchain DB bugs as and where they are found. If all goes well we should have enough of the nuances worked out to have it merged into master within the next 4 weeks.
4. We have seen our QA (automated testing) / CI (Continuous Integration) / Gitian build efforts drag their heels extremely slowly over the past few months, mostly due to specialists in those fields originally interested in helping us finally not being able to commit to any significant period of assistance. We are stepping this up a notch with the assistance of a new contributor, Gazby in #monero-dev, who will focus on the devops work.
Dev Diary
Core: msys2 now successfully compiles static releases in PR 180, final testing of new builds will happen this week
Core: expect a mass merge of PRs previously waiting this week. If you have a PR with CMake changes in it expect it to be merged and fixed manually, but moving forward CMake changes will have to comply with the new, cleaner CMake.
Until next week!
November 25, 2014, 06:14:18 AM
Dev not online for long time.?where xmr will go?
What??? We are online all the time
November 25, 2014, 04:22:33 AM
I'm hoping that's the dumbest thing I read today, but I doubt it.
I like this. :-) I loled. 
November 25, 2014, 04:06:35 AM
Dev not online for long time.?where xmr will go?
Sadly to abyss I guess, as annon hype is over, all coins including DRK and XMR will die, but they will die slow.I'm hoping that's the dumbest thing I read today, but I doubt it.
November 25, 2014, 04:02:43 AM
Dev not online for long time.?where xmr will go?
What??? We are online all the time
November 25, 2014, 03:56:35 AM
Dev not online for long time.?where xmr will go?
Sadly to abyss I guess, as annon hype is over, all coins including DRK and XMR will die, but they will die slow. November 25, 2014, 03:42:37 AM
Dev not online for long time.?where xmr will go?
November 25, 2014, 03:34:48 AM
Britain colonised the world! if you want a worldwide understanding it seems like a good start.
Of course you could stick with the world of America if you prefer. "baseball world series" ahem
Of course you could stick with the world of America if you prefer. "baseball world series" ahem
That doesn't answer the question challenge I presented, but thank you for chiming in.
November 25, 2014, 01:59:04 AM
Thats not a real reason to not use British English, of course most denominations are USD/BTC with the USD being the world reserve currency. Most other markets are denominated as so. You dont see much GBP/BTC parings as there isnt much demand to trade in that obviously but what does that have to do with using the correct language?
Why would you leave out everything in my quote besides that 1 point? My original statement was:
"
Obviously American English. The British have been hostile to cryptocurrencies thus far. How often do you see pound/BTC pairing?
--British banks won't deal with anyone related to cryptos.
"
You don't see the pound/BTC pairing mainly because British banks won't work with crypto exchanges so there is very limited ways to get pounds into crypto. With Britain being resistant to bitcoin and America accepting it....I think that is a pretty fair reason to write it in American English.
It honestly makes very little difference if you want to use 'z' or 's' etc, but that's my 2 cents.
That would be because as I said the fact that you don't see GBP/BTC should have any bearing on which version of English you use. There is not limited ways to get GBP into crypto as I and many of my associates have done without any problems.
It makes little difference of course but that as a reason to use AE just isn't a proper one IMO.
Maybe you can educate me then. What exchange has a GBP/BTC trade pairing that primarily uses a British bank? I'm guessing that you won't come up with one and your talk is just smoke and mirrors (as is a lot of internet speech)...but I'll give you the benefit of the doubt as I would love to be wrong in this case.
November 24, 2014, 10:19:00 PM
Ladies and gentlemen, are you ok ?
November 24, 2014, 09:03:12 PM
I'm waiting for Monday Monero Massive
Some have tried. Good luck with that
We should just start taking bets on what corner of the globe fluffypony can't post in this time, every monday!
November 24, 2014, 08:00:31 PM
Good luck with that Cheesy
November 24, 2014, 04:33:22 PM
I'm waiting for Monday Monero Massive
Some have tried. Good luck with that
I believe
Last Reward: 13.005 soon 12 / Can you imagine how few coins will receive the miners as the price rises /
Jump to: