Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bitcoinerS

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 ... 40
136
Technical Support / BitShares X integration with Ubuntu
« on: September 28, 2014, 10:44:15 pm »
When I build BitShares X binary for Ubuntu it launches with icon in left top corner instead of top right panel.



I wonder  how to properly integrate BitShares X into Ubuntu desktop.

137
General Discussion / Re: Someone please tell DACsunlimited not to use MD5
« on: September 28, 2014, 08:21:36 pm »
Good work. Thx.

If/when you are in contact with DSL please tell them to setup ppa repository for Ubuntu binaries. They keep ignoring linux users.

user: maqifrnswa

maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares

This needs to be published by DSL.

138
General Discussion / Re: Are feeds temporary?
« on: September 28, 2014, 01:49:29 pm »
Hopefully feeds are indeed temporary and some time in the future we wont use them.

139
I wish there was less background noise and random laughter while bytemaster speaks.

140
If BM and the dev team really don't want account transferring, perhaps they could implement an 'account burn' feature, which allows you to permanently disable an account from sending/receiving/transacting. Any person attempting to send this account funds would get their funds sent back, with the memo that the account burner used in their burn transaction.

On second thought, maybe the memo feature would be too useful to an account hacker, eg "btercom has a new address, please send funds to xxblademasterxx for all future deposits instead."

When you revoke an account it would make everyone else's wallet be super paranoid about that account. That is better than being able to transfer which makes compromises deadly.

In your example, the memo field could be crossed out in red with a tooltip "this account is revoked - do not trust any interactions with this account", and disable transferring at the wallet level.

Instead of telling all to be afraid of some account or disabling transfers to it, it would be better to indicate that an account has recently been "registered/transferred/has new owner"
If an account has registration date less than 1 (month, or year) it can be made visually stand out as new. That is enough to let people know to be careful with an account.  Account names should be cancel-able/transferable, and as I already mentioned previously, this is a serious design limitation that will have to be removed sooner or later.

141

I think this is already possible.  wallet_account_update_registration has a data field which can contain arbitrary JSON data.  You can access it via the "Edit" tab in your account in the GUI.

As, I already mentioned this is possible today, only that this needs to be made easier to use with a special field on account page. Also, what is needed is BitShares X authentication for website loaded from that ip. It needs to be formally integrated with BitShares X to be useful.

142
Interesting. What would the point of this be?

One of the possibilities would be for people to publish web pages that are authenticated with BitShares X.

We could have websites reachable with

btsx://<account>

143

Anyone?

144
А кстати, как лучше перевести margin? Может залог?

probably, but what about 'margin call' then?

margin = маржа, гарантийный взнос, залог
margin call = автоматическое покрытие залога или гарантийного взноса, при определённых условиях.

145
General Discussion / Re: new api: supply and debt
« on: September 25, 2014, 08:02:22 pm »
There seems to be a small error


>>> supply USD
367,640.2909 USD

>>> debt USD
367,640.2537 USD

146
General Discussion / Re: new api: supply and debt
« on: September 25, 2014, 07:50:34 pm »
Latest stats on USD. I wonder why supply is down about $200k..

Code: [Select]
>>> supply USD
367,640.2909 USD
default (unlocked) >>> debt USD
367,640.2537 USD
default (unlocked) >>> blockchain_get_asset USD
{
  "id": 22,
  "symbol": "USD",
  "name": "United States Dollar",
  "description": "1 United States dollar",
  "public_data": "",
  "issuer_account_id": -2,
  "precision": 10000,
  "registration_date": "20140719T000000",
  "last_update": "20140719T000000",
  "current_share_supply": 3676402537,
  "maximum_share_supply": 1000000000000000,
  "collected_fees": 56533932
}

147
General Discussion / Re: Block Explorer and Delegates Listing
« on: September 25, 2014, 07:47:01 pm »
Asks are 'for sale orders' and Bids are 'buys'. Your naming them opposite on charts is very confusing. Please correct.

149
General Discussion / Re: The BitShares Big Picture
« on: September 25, 2014, 08:46:07 am »

Heads of to Dan

hahaha

Now that is an idea worth considering  :D

How is that for a headline?  :)

150
I was looking over video "Introduction to Keyhotee" from last year
https://www.youtube.com/watch?v=3pZaTdEtK-8

It mentions DomainShares DAC that maps Name to IP and Public Key.
I thought how about adding ability to map registered account names to ip in BitShares X?
This is already possible with public data of account, but could be made easier to use by adding appropriate field to account page.

Once this feature is enabled we can have an internal BitShares X sub net right inside the wallet..

One of the possibilities would be for people to publish web pages that are authenticated with BitShares X.

We could have websites reachable with

btsx://<account>

Also, I would like to be able to offer service(s) from website(s) authenticated with my accounts. One way this can be done is to build such ability into BitShares X client.

If someone opens page
/#/accounts/<account>

Currently one can see date of account registration and recent transactions. Some extra info about delegates.

If my proposal is implemented users would be able to integrate external web-content inside their account  pages authenticated with BitShares X.

We would have benefits of BitSharesX account reputation and web of trust features + extra services.

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 ... 40