BitShares Forum
Main => General Discussion => Topic started by: ak on February 01, 2015, 01:05:43 am
-
It is with great pleasure that I announce the launch of the new bitshares.org website! It's now live!
We really came together as a community on this one. We received a lot of great feedback from people on the forums, as many of our community members ideas and suggestions were incorporated into the new site. It's important to point out that nothing is set in stone here and that this website will always be a work in progress, as we will continue to seek ways to modify the site over time to improve the user experience and increase new user acquisition conversion rates.
When it comes to acknowledging individual efforts, there were so many people involved in the project, I almost don't know where to start…
BIG THANKS to cass (whom I know first-hand worked on this project day and night in order to see it through to completion), nikolai and prometheus for creating some really awesome content, the NullStreet Marketing team, and anyone else that was involved whom I might be leaving out!!!
2015 is going to be a great year for BitShares!!
-
+5% Well done guys I like it very good work!
-
+5% We're beginning to put on the professional polish. Nice job.
-
So awesome!
Love the new look.
Well laid out and functional.
+5%
-
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 (https://bitsharestalk.org/index.php?topic=13888.msg180641#msg180641) 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.
-
+5%
-
Three cheers for @cass! 8)
-
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.
+5%
:o arhag has identified a significant attack vector. Let's bang a gong or something. This sounds serious.
-
+5%
-
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 (https://bitsharestalk.org/index.php?topic=13888.msg180641#msg180641) 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.
Good catch arhag. Yes, all downloads should be https at least. I am sure they are watching this thread and will make the changes asap. +5%
-
Nice Work !! :)
-
Amazing!
I finally got a chance to sit down and go through the website, and it's a work of art! Highly functional art.
Well done Cass, and everyone who contributed!
We are on our way. 8)
-
Link ;) www.bitshares.org/?r=whiskey
-
Really great job!
-
Great to see the "official" website up!
Please, move 'what are the risks' below the fold.
-
It's so awesome. We now have probably the most professional looking branding on our main site, and the best, most user friendly funnel as well. Click get started, look at some explanatory pictures, download the light wallet, start trading bitcoin to BTS, BitUSD, BitCNY directly in your wallets with shapeshift and similar services, perhaps soon also BitGold, Bitsilver, BitOIL, BitEUR. Then once you're experienced with the system and interface of our wallet, you can download the full node and start doing fully decentralized trading with all the assets you are used to, plus UIA's, and at lower spreads. And of course at all times you can instantly cash in or out through the most mature decentralized financial infrastructure, bitcoin, to services like coinbase, bitcoin accepting prepaid debit cards, bitpay and coinbase merchants. It's like BitShares leaps completely past all the issues earlier altcoins have had with adoption/network effect.
-
https://github.com/cassiopaia/BitShares-Decentralized-Exchange
ssl cert is in the works!
-
Had a talk with cass about SSL at bitshares.org yesterday .. CA is currently waiting for a reply from stan to sign the cert ... so its a matter of a few days until we have ssl there ..
-
The new site is very nice, well structured and very nice designs so +5% +5% +5%
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 +5% +5% +5%
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.
Come on, everyone uses those moving backgrounds. They're just temporarily a fad because html5 video is new fancy tech. A distracting image on the front page isn't good, the call to action button needs to be the focal point.
-
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.
We do have a moving a background: http://bitshares.org/resources/vision (http://bitshares.org/resources/vision) :D
-
hahaha :D
-
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!"
-
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!"
corrected - pls use https://github.com/cassiopaia/BitShares-Decentralized-Exchange/issues for future issues
thx
-
I think the 'What are the risks?' link should go on the download page instead. I understand that being up-front with risks shows credibility, however based on my experience with conversion funnels, the button in this position will have negative effects that outweigh this:
Most people won't click through to the risks, and will be left feeling a certain amount of uneasiness (depending on the person, ranging from no uneasiness to complete paranoia), leading them to either not click through to the 'Create Account' button, or to decrease download conversion rate on the next page.
We can infer that if people do click through to see the risks, that means the risks are important to them on some level. They will either read it or they won't.
If they do read it, this is the best possible outcome for somebody who clicks through to the risks link- from here they can make their own informed decision and know a little more about how BitShares works. However, they still need to exit the modal, and click through to the account page, increasing the number of steps for conversion. Maybe a 'I understand the risks, continue to create my account' button would help here. It's also important to consider that someone who is totally unfamiliar with the BitAssets may not understand the risks at all, leading to confusion, thus leaving the site.
If they don't read the text, this means that despite the risks being important to them, their time and energy to inform themselves is worth more to them. From here they will probably just leave. The only way to address this problem directly would be to make the risks more brief, but I think the quality of the content would suffer from this, and would not make much difference anyway.
In its current state, it's like the website welcomes the user at the front desk, then says,
"Create an account with us! Want to know why it's risky? No? Ok, suit yourself. Follow me."
or
"Create an account with us! Want to know why it's risky? Yes? Ok, here's a sheet of paper loaded with content you probably won't understand, which you can take to that chair over there to read. You'll have to come back and ask me again if you want to create an account."
When it could be,
"Create an account with us! Yes? Follow me."
From here, the prospective customer is making a small commitment. Small commitments are important, because they greatly reduce the probability of bailing in a later step. (As a related aside: I once completed a comprehensive IQ test that took over an hour to complete. At the very end, they said I needed to pay $5 to see the results. Even though I felt it was a dirty trick, I paid, as the value of the time committed combined with the value of knowing the result was worth more than $5 to me, something which was already demonstrated by me making it all the way through the test. This is a dramatic example, but a similar principle applies here.)
The download links to the client should be inline in the step-by-step guide for creating an account, and the risks link should be below them in small text:
By downloading the client above, I understand the risks of downloading open-source cryptocurrency software. (http://By downloading the client above, I understand the risks of downloading open-source cryptocurrency software.)
Which would then open the modal.
-
yes thx for your input! we have to consider this yes... but before also we should check if this could cause problems with implemented tracking codes...
-
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/
-
Well done, Cass. Love your work!
-
Nice job.
What about a link for Merchants? Wasn't uptake by merchants supposed to be one of the keys to getting widespread adoption by the masses?
-
(http://i.imgur.com/p7Yvxu7.png)
-
"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".
-
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/
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 ...
-
"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".
done
http://bitshares.org/resources/downloads
-
Maybe the create account buttons should be green? Orange is like "Danger" or "Warning", green is like "Go" or "Money".
-
Had the same initial reaction... Great minds....
I vote for a green risk button too - and also green around the "200%" and "300% collateral" points
-
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.
-
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 (https://bitsharestalk.org/index.php?topic=13888.msg180641#msg180641) 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.
Edit: Other than that the new site looks great!
-
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/
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 ...
Awesome :)
-
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.
2: its from bitsharesblocks, using the same feed I've prepared for cmc. They're currently just scraping the price off my site but that means they're using the median feed price instead of the actual prices.
-
Maybe the create account buttons should be green? Orange is like "Danger" or "Warning", green is like "Go" or "Money".
green was my initial layout ! yes
-
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 (https://bitsharestalk.org/index.php?topic=13888.msg180641#msg180641) 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.
as i said before - orderd SSL cert over week bafore but have to wait for an approval mail which contains priv key etc.
Domains are hosted via namecheap and approver mail is admin@bitshares.org.
I'Ve to hold down until i get this message! I've also contacted Stan about this … have to wait
-
Thank you for your work website makers. Really really niiice!
-
awesome site!
-
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 8) 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
-
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 8) 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
yup thx for your input - will fix it soon !
-
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 8) 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
pls check again .. should be solved now!
-
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).
yes maybe i'll check this later on .. but honestly ... it's a mess to get sites generelly working in older browers ...
-
i must say it is very simple!
After this how about provide different language ?
-
i must say it is very simple!
? you mean site? .. yes it should be ... doesn't it?
After this how about provide different language ?
language support will be added soon ...
-
+5% love those individual colors for each of the bitassets!
-
@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!
-
@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!
+5%
-
SSL is working now! Thx to stan
https://bitshares.org/resources/downloads
-
SSL is working now! Thx to stan
https://bitshares.org/resources/downloads
+5%
But please make the website redirect to HTTPS if it is accessed through HTTP.
I think you need this in .htaccess:
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.
-
But please make the website redirect to HTTPS if it is accessed through HTTP.
I think you need this in .htaccess:
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://bitshares.org/$1 [R,L]
done
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.
yeah - we've ordered a wildcard ssl cert .. so guess this should ne problem .. will check it later on .. guess i've to send ssl .crt .key .. etc to wiki and faucet vps server admin, so they can include it ony their server structure!? Or i'm wrong with this!?
-
ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!
-
pls use github for issues
https://github.com/cassiopaia/labs.bitshares.org
or
https://github.com/BitShares/bitshares.org
-
ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!
That isn't all:
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 (http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) 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).
-
thx - yes we should do this but yet all sites like wiki etc are hosted on different vps ... will add conflicted files local now!
Thanks for your help arhag
-
ok fixed font ssl and highcharts ssl issues .. disabled highcharts.js for now cause currently we're not using it anywhere on site .. (installed for testing purposes only)
-
ok https is gonna cause issues with the tickers, since svk doesn't has an https api server yet!
That isn't all:
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 (http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) 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).
I actually switched over from using CORS to JSONP a few months ago because CORS was being unreliable and only worked half the time. JSONP is better because it allows you to bypass the issue, but it appears it doesn't work for https -> http calls.
Anyway I've made the /cmc api call non-jsonp and added CORS to it, checking with Cass it that works.
-
update: svk will order a ssl cert soon!
-
update: svk will order a ssl cert soon!
Update: It's done, thanks Cass for chipping in :)
Like Cass I was able to pay the $95 certification using Bitshares thanks to Shapeshift, it was quite simple and fast! :)
-
ok charts are working again! https for faucet.bitshares.org is in the works!
-
Are u going to do the ecommerce and bts login section?
-
Are u going to do the ecommerce and bts login section?
yup next steps on roadmap .. will publish more ideas soon! :)
-
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).
That is a very good point. Here is the demo:
http://demo.aboutbts.com/
http://www.aboutbts.com/2015/01/how-to-try-out-bitshares-wallet-without-installing-it.html
-
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).
You can also get that on bitsharesblocks.com
-
@cass
I don't see on the home page any link to the bitshares github repository !
Please add the link https://github.com/BitShares
somewhere to the bottom of the page ;)
-
@cass
I don't see on the home page any link to the bitshares github repository !
Please add the link https://github.com/BitShares
somewhere to the bottom of the page ;)
ok yes you'll find github link under downloads .. but will add it to bottom menu also !
-
This will seem weird but please, remove the github icon and only link it at the bottom on the "The BitShares source code is also available via the GitHub" as a text link.
Currently it's the first link they see and you're sending users to a confusing site they don't understand instead of the executable.
-
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/downloads
I think there should be a direct link on the thanyou page in case it do not start download automatically.
-
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/downloads
I think there should be a direct link on the thanyou page in case it do not start download automatically.
thanks yes will update downlaod page this week! Yes its caused due Thank you page i guess, which should track downloaded wallets!
ut yes, we've to find another workaround. I'm planning to add hidden frame/layer to solve this issue!
Will post here if done!
Anyone of you got same issues with WIN download, pls let me know!
-
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
-
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
+1
-
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
+1
updated!
-
it would be great for future issue if you could use github for issuering, thx!
https://github.com/cassiopaia/labs.bitshares.org/issues
-
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
+1
updated!
Thank you for updating this.
Could you please tell me what was the reason to do this back then?
-
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
+1
updated!
Thank you for updating this.
Could you please tell me what was the reason to do this back then?
?
-
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
+1
updated!
Thank you for updating this.
Could you please tell me what was the reason to do this back then?
?
I mean you must had reasons back then. Could you share it?
-
I wanted to show USD vs BTS and BTC vs BTS and to have it look something like:
(http://1.bp.blogspot.com/-b8NvInmgrp8/TkKrhx82eVI/AAAAAAAAFI8/tcu6HkwrZqg/s400/stocks.jpg)
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:
(http://1.bp.blogspot.com/-b8NvInmgrp8/TkKrhx82eVI/AAAAAAAAFI8/tcu6HkwrZqg/s400/stocks.jpg)
I never wanted to it display BTS vs BitBTC or USD vs BitUSD.
…
-
hey Cass, digging the new site. One suggestion:
On the page https://bitshares.org/resources/thankyou
<p>If you'll need help etc please visit our forum for more detailed infos</p>
doesn't read very well... and it does not provide new users an easy way to access our forums! I suggest the following:
<p>If you need additional help, please visit our <a href="www.bitsharestalk.org">forum</a> for more information.</p>
Thanks for all of your hard work!
-
Added the above to github. Cheers!
-
I wanted to show USD vs BTS and BTC vs BTS and to have it look something like:
(http://1.bp.blogspot.com/-b8NvInmgrp8/TkKrhx82eVI/AAAAAAAAFI8/tcu6HkwrZqg/s400/stocks.jpg)
I never wanted to it display BTS vs BitBTC or USD vs BitUSD.
Right.
BTS is the "base currency" in bitshares ecosystem whose price only matters.
When comes to bitassets, we can display its totoal supplies and places(like websites, merchants or applications) to spend them. Bitassets don't have a "price", it's only a means of circulation, like paper currency, don't have the ability to speculate to profit.
-
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 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 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!
-
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 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!
BTA's price is pegged, period. This is the mechanism. This is why tradebts.com running its business on.
BTA is not designed to be speculated to achieve its peg, it's a intrinsic nature. You know why, right?