Bitcoin Forum
December 09, 2016, 11:41:44 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 [4]  All
  Print  
Author Topic: [ANN] GLBSE has a new look!  (Read 4556 times)
MrTeal
Legendary
*
Offline Offline

Activity: 1246


View Profile
May 02, 2012, 02:28:04 PM
 #61

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:



I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

I did the same thing.

As did I. Tongue
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481326904
Hero Member
*
Offline Offline

Posts: 1481326904

View Profile Personal Message (Offline)

Ignore
1481326904
Reply with quote  #2

1481326904
Report to moderator
1481326904
Hero Member
*
Offline Offline

Posts: 1481326904

View Profile Personal Message (Offline)

Ignore
1481326904
Reply with quote  #2

1481326904
Report to moderator
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
May 03, 2012, 09:31:05 AM
 #62

Trading fees have returned, currently only buy fee at 0.5%

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
May 04, 2012, 12:22:08 AM
 #63


Re-posting from the other 2.1 thread ...

So ... at the risk of being perceived an insistant bloke ... whare's mah .csv history download ?

More seriously: this would be a *really* useful feature: my /portfolio page is
very long by now and is getting close to impossible to process by eyballs.

Another - probably simpler to implement - equivalent feature would be to have
the portfolio API call return *everything* that is visible in the /portfolio page.

Right now it only returns current stuff, not the whole history, whereas the
/portfolio page returns everything.

Maybe with an option ... something like:

https://glbse.com/api/portfolio/ID/KEY?opt=all

Right now, I am reduced to perl-parse the HTML output
of the /portfolio page ... giant PITA.

Thanks for considering the suggestions.

Hey znort987, I'll be adding csv for account details (buys/sells/deposits/withdrawals/transfers etc).

What would you think would be the best way to have this? By the month?

For the API we'll add a history function, where you can pull all your histories.

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
OgNasty
Donator
Legendary
*
Offline Offline

Activity: 2030


Powered by NastyFans


View Profile WWW
May 04, 2012, 12:36:03 AM
 #64

Looks good Nefario.  I'm looking forward to having some time to check out the API one of these days. 

BITSLER                 ▄███
               ▄████▀
             ▄████▀
           ▄████▀  ▄██▄
         ▄████▀    ▀████▄
       ▄████▀        ▀████▄
     ▄████▀            ▀████▄
   ▄████▀                ▀████▄
 ▄████▀ ▄████▄      ▄████▄ ▀████▄
█████   ██████      ██████   █████
 ▀████▄ ▀████▀      ▀████▀ ▄████▀
   ▀████▄                ▄████▀
     ▀████▄            ▄████▀
       ▀████▄        ▄████▀
         ▀████▄    ▄████▀
           ▀████▄▄████▀
             ▀██████▀
               ▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄            
▄▄▄▄▀▀▀▀    ▄▄█▄▄ ▀▀▄         
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄      
█  ▀▄▄  ▀█▀▀ ▄      ▀████   ▀▀▄   
█ █▄  ▀▄   ▀████       ▀▀ ▄██▄ ▀▀▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█  ▀▀       ▀▄▄ ▀████      ▄▄▄▀▀▀  █
█            ▄ ▀▄    ▄▄▄▀▀▀   ▄▄  █
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█ ▄▄   ███   ▀██  █           ▀▀  █ 
█ ███  ▀██       █        ▄▄      █ 
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀  
▀▄            █        ▀▀      █  
▀▀▄   ███▄  █   ▄▄          █   
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀    
▀▀▄   █   ▀▀▄▄▄▀▀▀         
▄▄▄▄▄▄▄▄▄▄▄█▄▄▀▀▀▀              
              ▄▄▄██████▄▄▄
          ▄▄████████████████▄▄
        ▄██████▀▀▀▀▀▀▀▀▀▀██████▄
▄     ▄█████▀             ▀█████▄
██▄▄ █████▀                ▀█████
 ████████            ▄██      █████
  ████████▄         ███▀       ████▄
  █████████▀▀     ▄███▀        █████
   █▀▀▀          █████         █████
     ▄▄▄         ████          █████
   █████          ▀▀           ████▀
    █████                     █████
     █████▄                 ▄█████
      ▀█████▄             ▄█████▀
        ▀██████▄▄▄▄▄▄▄▄▄▄██████▀
          ▀▀████████████████▀▀
              ▀▀▀██████▀▀▀
            ▄▄▄███████▄▄▄
         ▄█▀▀▀ ▄▄▄▄▄▄▄ ▀▀▀█▄
       █▀▀ ▄█████████████▄ ▀▀█
     █▀▀ ███████████████████ ▀▀█
    █▀ ███████████████████████ ▀█
   █▀ ███████████████▀▀ ███████ ▀█
 ▄█▀ ██████████████▀      ▀█████ ▀█▄
███ ███████████▀▀            ▀▀██ ███
███ ███████▀▀                     ███
███ ▀▀▀▀                          ███
▀██▄                             ▄██▀
  ▀█▄                            ▀▀
    █▄       █▄▄▄▄▄▄▄▄▄█
     █▄      ▀█████████▀
      ▀█▄      ▀▀▀▀▀▀▀
        ▀▀█▄▄  ▄▄▄
            ▀▀█████
[]
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
May 04, 2012, 05:41:24 AM
 #65

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
BinaryMage
Hero Member
*****
Offline Offline

Activity: 546


Ad astra.


View Profile
May 04, 2012, 05:54:28 AM
 #66

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

Thank you. Quite an improvement, let me say.

-- BinaryMage -- | OTC | PGP
teek
Hero Member
*****
Offline Offline

Activity: 664


ASICMINER Official Canadian Distributor


View Profile
May 06, 2012, 08:01:07 PM
 #67

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets?  Has this changed?  I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek

Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
May 07, 2012, 02:51:32 AM
 #68

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets?  Has this changed?  I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek


Hi Teek,
All you're fees can be seen here https://us.glbse.com/portfolio/fees after logging in.
That link shows from the asset page when logged in.

Regarding fees for sub-assets there has always been fees for them, and we've never said any different.

It also shows you the fee you will be charged right above the "Create" button when creating an asset.

Quote
Fee

You will be charged 8.0BTC to create this security, this charge is not refundable.

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
teek
Hero Member
*****
Offline Offline

Activity: 664


ASICMINER Official Canadian Distributor


View Profile
May 07, 2012, 03:00:18 AM
 #69


Regarding fees for sub-assets there has always been fees for them, and we've never said any different.



I must have been thinking of something else.  Thanks!

gabbynot
Sr. Member
****
Offline Offline

Activity: 338


View Profile
May 08, 2012, 01:28:32 PM
 #70

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

The servers are located in the US?
Nefario
Hero Member
*****
Offline Offline

Activity: 602


GLBSE Support support@glbse.com


View Profile WWW
May 08, 2012, 02:00:52 PM
 #71

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

The servers are located in the US?

The proxy server is located in the US.

PGP key id at pgp.mit.edu 0xA68F4B7C

To get help and support for GLBSE please email support@glbse.com
REF
Hero Member
*****
Offline Offline

Activity: 526


View Profile
May 08, 2012, 06:26:52 PM
 #72

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets?  Has this changed?  I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek


Hi Teek,
All you're fees can be seen here https://us.glbse.com/portfolio/fees after logging in.
That link shows from the asset page when logged in.

Regarding fees for sub-assets there has always been fees for them, and we've never said any different.

It also shows you the fee you will be charged right above the "Create" button when creating an asset.

Quote
Fee

You will be charged 8.0BTC to create this security, this charge is not refundable.

tested us.glbse. i live in the US. it is a little fast the biggest improvement if that there are no large spikes.

pings to glbse.com
Code:
C:\Documents and Settings\LaptopXP>ping -t glbse.com

Pinging glbse.com [67.222.146.58] with 32 bytes of data:

Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=160ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=281ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=258ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=61ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=65ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=285ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248

Ping statistics for 67.222.146.58:
    Packets: Sent = 87, Received = 87, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 285ms, Average = 61ms
Control-C
^C

to us.glbse.com
Code:
C:\Documents and Settings\LaptopXP>ping -t us.glbse.com

Pinging us.glbse.com [67.222.146.58] with 32 bytes of data:

Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=61ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248

Ping statistics for 67.222.146.58:
    Packets: Sent = 77, Received = 77, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 61ms, Average = 51ms
Control-C
^C
The00Dustin
Hero Member
*****
Offline Offline

Activity: 806


View Profile
May 14, 2012, 02:16:14 AM
 #73

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:



I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

I did the same thing.

As did I. Tongue
glad to see I'm notalone here...
Pages: « 1 2 3 [4]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!