0 Members and 1 Guest are viewing this topic.
Quote from: theoretical on February 19, 2015, 05:10:50 pmQuote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.Quote from: bytemaster on February 17, 2015, 09:02:33 pmI never wanted to it display BTS vs BitBTC or USD vs BitUSD.I thought showing BTC : BitBTC and USD : BitUSD was a great idea. Market pegged BitAssets are the main thing we have that other altcoins don't. Showing that the peg works, front and center on our website, is a concise statement of our value proposition and our product's identity. Of course we can maybe do a better job of explaining what the data means and where it's coming from, maybe in hover text or a link when you click on it.Just showing the price of BTS : BTC -- you can go to coinmarketcap.com and see that kind of chart for hundreds of altcoins. A BTS : BTC price graph doesn't say anything about what makes BitShares special.Thank you!
Quote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.Quote from: bytemaster on February 17, 2015, 09:02:33 pmI never wanted to it display BTS vs BitBTC or USD vs BitUSD.I thought showing BTC : BitBTC and USD : BitUSD was a great idea. Market pegged BitAssets are the main thing we have that other altcoins don't. Showing that the peg works, front and center on our website, is a concise statement of our value proposition and our product's identity. Of course we can maybe do a better job of explaining what the data means and where it's coming from, maybe in hover text or a link when you click on it.Just showing the price of BTS : BTC -- you can go to coinmarketcap.com and see that kind of chart for hundreds of altcoins. A BTS : BTC price graph doesn't say anything about what makes BitShares special.
Pls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.
I never wanted to it display BTS vs BitBTC or USD vs BitUSD.
I wanted to show USD vs BTS and BTC vs BTS and to have it look something like: I never wanted to it display BTS vs BitBTC or USD vs BitUSD.
Quote from: merlin0113 on February 17, 2015, 12:56:05 amQuote from: cass on February 16, 2015, 06:46:52 pmQuote from: bytemaster on February 16, 2015, 05:17:50 pmQuote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.来自我的 M040 上的 Tapatalkupdated!Thank you for updating this. Could you please tell me what was the reason to do this back then??
Quote from: cass on February 16, 2015, 06:46:52 pmQuote from: bytemaster on February 16, 2015, 05:17:50 pmQuote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.来自我的 M040 上的 Tapatalkupdated!Thank you for updating this. Could you please tell me what was the reason to do this back then?
Quote from: bytemaster on February 16, 2015, 05:17:50 pmQuote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.来自我的 M040 上的 Tapatalkupdated!
Quote from: merlin0113 on February 16, 2015, 05:02:17 pmPls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.来自我的 M040 上的 Tapatalk
Pls remove the rate of bitcny/cny,bitusd/usd,etc. on the topside of front page. I think its very misleading, not to mention where you grasped this data in the first place.来自我的 M040 上的 Tapatalk
i find a problem. when i click the windows edition icon at the follow page, it just would‘t start to download sometimes.https://bitshares.org/resources/downloadsI think there should be a direct link on the thanyou page in case it do not start download automatically.
@cassI don't see on the home page any link to the bitshares github repository !Please add the link https://github.com/BitSharessomewhere to the bottom of the page
How can one view the bitshares market using the browser.I know I used a link once for a shared wallet for testing.Would it not be a good idea to have a link on the website to a neat GUI showing the active markets (spread, charts, orders etc).
Would it not be a good idea to have a link on the website to a neat GUI showing the active markets (spread, charts, orders etc).
Are u going to do the ecommerce and bts login section?
update: svk will order a ssl cert soon!
Quote from: cass on February 03, 2015, 08:33:25 amok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!That isn't all:Code: [Select] Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Roboto:700,400,300,200,100'. This request has been blocked; the content must be served over HTTPS.(index):152 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://faucet.bitshares.org/widgets/1/w.js?ref='. This request has been blocked; the content must be served over HTTPS.(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v1/cmc?callback=jQuery21305609141846653074_1422953063792&format=json&_=1422953063793'. This request has been blocked; the content must be served over HTTPS.jquery.js:8625 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://coinmarketcap-nexuist.rhcloud.com/api/bts?format=json'. This request has been blocked; the content must be served over HTTPS.app.js:80 Object {readyState: 4, getResponseHeader: function, getAllResponseHeaders: function, setRequestHeader: function, overrideMimeType: function…}jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v3/pricehistory/USD/%7B%22start%22:%222015-0…0Z%22%7D?callback=jQuery21305609141846653074_1422953063792&_=1422953063794'. This request has been blocked; the content must be served over HTTPS.First, you can use HTTPS with code.highcharts.com and fonts.googleapis.com and coinmarketcap-nexuist.rhcloud.com. Then that just leaves faucet.bitshares.org and api.bitsharesblocks.com.Also, why are we not hosting the various javascript scripts that we are using ourselves rather than linking to other sites (even if it's over HTTPS) to provide them, such as highcharts, jquery, google, facebook, to name a few (not to mention others from hosts I know nothing about and don't personally trust).And, rather than using JSONP to get data from api.bitsharesblocks.com, I would prefer if svk could enable CORS on api.bitsharesblocks.com for at least the bitshares.org origin (but he might as well do it for * so that anyone can use that data without JSONP).
ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!
Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure resource 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.bitshares.org/:1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Roboto:700,400,300,200,100'. This request has been blocked; the content must be served over HTTPS.(index):152 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://faucet.bitshares.org/widgets/1/w.js?ref='. This request has been blocked; the content must be served over HTTPS.(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/highstock.js'. This request has been blocked; the content must be served over HTTPS.(index):1 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://code.highcharts.com/stock/modules/exporting.js'. This request has been blocked; the content must be served over HTTPS.jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v1/cmc?callback=jQuery21305609141846653074_1422953063792&format=json&_=1422953063793'. This request has been blocked; the content must be served over HTTPS.jquery.js:8625 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://coinmarketcap-nexuist.rhcloud.com/api/bts?format=json'. This request has been blocked; the content must be served over HTTPS.app.js:80 Object {readyState: 4, getResponseHeader: function, getAllResponseHeaders: function, setRequestHeader: function, overrideMimeType: function…}jquery.js:8693 Mixed Content: The page at 'https://bitshares.org/' was loaded over HTTPS, but requested an insecure script 'http://api.bitsharesblocks.com/v3/pricehistory/USD/%7B%22start%22:%222015-0…0Z%22%7D?callback=jQuery21305609141846653074_1422953063792&_=1422953063794'. This request has been blocked; the content must be served over HTTPS.
But please make the website redirect to HTTPS if it is accessed through HTTP. I think you need this in .htaccess:Code: [Select]RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://bitshares.org/$1 [R,L]
RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://bitshares.org/$1 [R,L]
Also, something has got to be done about subdomains like wiki.bitshares.org and faucet.bitshares.org. Those cannot be accessed through HTTPS. So you would want to make those available on the bitshares.org domain instead and set up .htaccess to redirect to https://bitshares.org/wiki/$1 and https://bitshares.org/faucet/$1 for example. Also, before changing the faucet domain, we better be sure it doesn't break account registration from the BitShares client.
SSL is working now! Thx to stan https://bitshares.org/resources/downloads
@stan, dan : any reply to my ssl cert approval request (it was send to admin[at]bitshares.org) !? We have to install SSL asap IMO!Feeback appreciated!
i must say it is very simple!
After this how about provide different language ?
IEs (9 to be specific - of course a pain for sure and really not a biggie in regard of importance but should be taken care of later).
While you are at it looking for the cert and stuff please also double check overall speed of the site, got some mixed results really, opening and trying the download link (checked from 4 different locations whereas it appeared reaaly slow from at least two). Maybe you can beef up server-provider side?More serious: there are at least 5 HTTP500 timeouts for some font-files referenced + at least one javascript error. Also cross-browser testing shows the site isn't working in older IEs (9 to be specific - of course a pain for sure and really not a biggie in regard of importance but should be taken care of later).So just a little nit-picking from my end and hope you get those little itches sorted out to give a real professional impression also in this technical regard.Thanks for your hard work
Quote from: arhag on February 01, 2015, 01:39:49 amIt is a huge improvement!Is the source of the website hosted on GitHub somewhere? The last commit to https://github.com/BitShares/bitshares.org was May 15, 2014, so that can't be it. There are a few typos or minor issues on the website that I would find more convenient to correct myself as I discover them and submit as a pull request. And I assume more will pop up as the website continues to evolve, so collaborative editing would be useful. I would also like to reiterate that downloading the client binaries from the website is currently insecure. The best way to solve it would be to implement HTTPS on bitshares.org as soon as possible. Until then, a better-than-nothing fix is to point the download links to the binaries hosted on GitHub (protected by HTTPS), get rid of the SHA1 hashes on bitshares.org (because that provides a false sense of security since they can be changed by a MITM attacker of bitshares.org serving its own SHA1 over HTTP), and just tell people to refer to the SHA1 hashes on https://github.com/BitShares/bitshares/releases if they want to verify the binaries downloaded from a source other than GitHub. This is of course not a great solution, because victims visiting a MITM-modified bitshares.org may not pay attention to (or realize the security implications of) the fact that they are downloading the executable via HTTP. I don't want to hear about a user complaining that their money was stolen even though they downloaded THE client from the official "bitshares.org" website, which gives us a bad name.Exactly my same concerns. Especially #2 -- I will not point anybody at this website until HTTPS is in place.
It is a huge improvement!Is the source of the website hosted on GitHub somewhere? The last commit to https://github.com/BitShares/bitshares.org was May 15, 2014, so that can't be it. There are a few typos or minor issues on the website that I would find more convenient to correct myself as I discover them and submit as a pull request. And I assume more will pop up as the website continues to evolve, so collaborative editing would be useful. I would also like to reiterate that downloading the client binaries from the website is currently insecure. The best way to solve it would be to implement HTTPS on bitshares.org as soon as possible. Until then, a better-than-nothing fix is to point the download links to the binaries hosted on GitHub (protected by HTTPS), get rid of the SHA1 hashes on bitshares.org (because that provides a false sense of security since they can be changed by a MITM attacker of bitshares.org serving its own SHA1 over HTTP), and just tell people to refer to the SHA1 hashes on https://github.com/BitShares/bitshares/releases if they want to verify the binaries downloaded from a source other than GitHub. This is of course not a great solution, because victims visiting a MITM-modified bitshares.org may not pay attention to (or realize the security implications of) the fact that they are downloading the executable via HTTP. I don't want to hear about a user complaining that their money was stolen even though they downloaded THE client from the official "bitshares.org" website, which gives us a bad name.
Maybe the create account buttons should be green? Orange is like "Danger" or "Warning", green is like "Go" or "Money".
1. Under "Get started", shouldn't the user be told/shown that syncing with the blockchain the 1st time after installing can take a while, so that they are patient and don't give up in frustration? Another picture of what the wallet screen looks like while syncing would be helpful here.2. What is the source for the BitUSD price info at the top of the welcome page? It seems to be off compared to coinmarketcap.com.
Quote from: MrJeans on February 01, 2015, 04:20:55 pmCool site.I believe the site would benefit from having a greater focus on the exchange rates.This will make it look more like an exchange.The exchange rates (currently very small and at the top) should be larger with indicators and updating every few seconds.The way that this site updates prices (the constant change and information makes this site exciting to watch):http://bitcoincharts.com/markets/yup we'll integrate more stats/charts soon ... i want also something add like you can see on https://paymium.com/ - right sidebar for assets ...
Cool site.I believe the site would benefit from having a greater focus on the exchange rates.This will make it look more like an exchange.The exchange rates (currently very small and at the top) should be larger with indicators and updating every few seconds.The way that this site updates prices (the constant change and information makes this site exciting to watch):http://bitcoincharts.com/markets/
"What are the risks" should definitely be moved to a slightly more obscure location. Most people are not going to understand how the economics of Bitshares works and will leave thinking "sure it's stable but it's also risky".
typo:http://bitshares.org/get-started"At this point, the BitShares application will ask you for a location to save your wallet file. Selection the location of your choosing, click Save, and you are done!"
However, what I expected to see was a website with moving backgrounds like ripple so this disappointed me a bit. I guess these things are more costly but I think that the future of banking should have moving backgrounds.
The new site is very nice, well structured and very nice designs so However, what I expected to see was a website with moving backgrounds like ripple so this disappointed me a bit. I guess these things are more costly but I think that the future of banking should have moving backgrounds.
The website needs HTTPS ASAP.Now the downloads are served from bitshares.org directly over HTTP (http://bitshares.org/resources/downloads). Before they were at least served via GitHub download links which used HTTPS. Please correct this since otherwise users are vulnerable to man-in-the-middle attacks.....downloading the client binaries from the website is currently insecure. The best way to solve it would be to implement HTTPS on bitshares.org as soon as possible. Until then, a better-than-nothing fix is to point the download links to the binaries hosted on GitHub (protected by HTTPS), get rid of the SHA1 hashes on bitshares.org (because that provides a false sense of security since they can be changed by a MITM attacker of bitshares.org serving its own SHA1 over HTTP), and just tell people to refer to the SHA1 hashes on https://github.com/BitShares/bitshares/releases if they want to verify the binaries downloaded from a source other than GitHub. This is of course not a great solution, because victims visiting a MITM-modified bitshares.org may not pay attention to (or realize the security implications of) the fact that they are downloading the executable via HTTP. I don't want to hear about a user complaining that their money was stolen even though they downloaded THE client from the official "bitshares.org" website, which gives us a bad name.