Viewing a response to: @builderofcastles/re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t034721599z
Here is some info on the technical side. https://steemit.com/steemit/@timcliff/instructions-for-installing-a-steemit-com-instance-for-developers-interested-in-working-on-changes-to-steemit-com All of the changes are submitted via the GitHub repository via pull requests. https://github.com/steemit/steemit.com/ If you are interested in working on things, you should email sneak@steemit.com. (He is the project manager.) I'm also happy to help if you have any questions.
post_id | 1,846,344 |
---|---|
author | timcliff |
permlink | re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t035603269z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "links": ["https://steemit.com/steemit/@timcliff/instructions-for-installing-a-steemit-com-instance-for-developers-interested-in-working-on-changes-to-steemit-com", "https://github.com/steemit/steemit.com/"], "tags": ["bounty"]}" |
created | 2017-01-27 03:56:00 |
last_update | 2017-01-27 03:56:00 |
depth | 2 |
children | 7 |
net_rshares | 5,172,899,664,336 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.282 SBD |
curator_payout_value | 0.038 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 473 |
author_reputation | 262,354,724,187,317 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
transisto | 0 | 5,172,899,664,336 | 100% |
Thanks you I had questions and enthusiasm... but, they went badly unanswered, so interest has waned. Several people wanted to work on multiple documents at a time. Does Steemit.com store the draft on the server, or in some way on the person's computer? Does Steemit.com want a feature as such? Or do the want to avoid it because of database bloat, or needless complexity? steemit.com finds the first image in the post (or in H1) and then runs it through a process to make the thumbnail. Many people would like to select a thumbnail, because they do not want to use the first image. It would also be nice for sites like steemimg to provide a link to the thumbnail stored there so as to avoid bandwidth usage. I believe this would require a change to the block chain, does it?
post_id | 1,846,411 |
---|---|
author | builderofcastles |
permlink | re-timcliff-re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t040525855z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "tags": ["bounty"]}" |
created | 2017-01-27 04:09:57 |
last_update | 2017-01-27 04:09:57 |
depth | 3 |
children | 6 |
net_rshares | 36,718,074,463 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 SBD |
curator_payout_value | 0.000 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 784 |
author_reputation | 24,609,971,519,844 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
timcliff | 0 | 36,503,628,035 | 25% | ||
leongkhan | 0 | 214,446,428 | 25% |
I'm not sure what you mean as far as documents. All of the code changes are managed by GitHub pull requests. If you read up on GitHub branches, pull requests, and merging - that should give you an idea of how it works. There will be changes to the images soon, in that users will be uploading directly to steemit.com (instead of using third party sites like steemimg). As far as selecting which image to use as the thumbnail - I think that is a highly desired feature. The image logic shouldn't need a blockchain change. The blockchain will just store the links to the images (like it does currently). Steemit will be hosting the images, and the Steemit UI is what controls the thumbnail. An update may need to be made to how the data gets stored in the json_metadata of the post (in the blockchain) - but I am pretty sure this would not be a change to the actual blockchain.
post_id | 1,846,474 |
---|---|
author | timcliff |
permlink | re-builderofcastles-re-timcliff-re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t042302743z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "tags": ["bounty"]}" |
created | 2017-01-27 04:23:00 |
last_update | 2017-01-27 04:23:00 |
depth | 4 |
children | 4 |
net_rshares | 0 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 SBD |
curator_payout_value | 0.000 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 877 |
author_reputation | 262,354,724,187,317 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |
GitHub is a non-issue to me, all of my problems are with humans. I could completely rebuild steem, fix all the bugxs... and no one would know. It would just sit there on GitHub. I do not know the header structure of steem. I am pretty sure that a steemit.com looks at the text in each post and determines the image to resize into a thumbnail. The links are in the body of the post. I am suggesting that the link to the thumbnail should be stored in the same place that the title of the post is stored. It is a simple change, but unless it is already a field in the block, then it requires a change to the block chain.
post_id | 1,846,522 |
---|---|
author | builderofcastles |
permlink | re-timcliff-re-builderofcastles-re-timcliff-re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t043307626z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "tags": ["bounty"]}" |
created | 2017-01-27 04:37:39 |
last_update | 2017-01-27 04:37:39 |
depth | 5 |
children | 1 |
net_rshares | 0 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 SBD |
curator_payout_value | 0.000 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 624 |
author_reputation | 24,609,971,519,844 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |
https://steemd.com/tx/2cf51fe18bfc502fd7b378092fb70886c9a83ff1 As you can see, on this view of the post, there is no field for a thumbnail. It should be just under title, which, now, I am fairly certain requires a change to the block chain. It also looks like it can be added to the json_metadata as another tag, and this would not require a change to the block chain. That is, if the json_metadata is not dynamically built. I can see three solid ways to do this, but it requires a lot of changes, one to each part of the system. And, like I said, coordinating with people is the hard part. Who is @sneak? And how is the best way to not send a c,old letter to his spam folder?
post_id | 1,846,639 |
---|---|
author | builderofcastles |
permlink | re-timcliff-re-builderofcastles-re-timcliff-re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t050247276z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "users": ["sneak"], "links": ["https://steemd.com/tx/2cf51fe18bfc502fd7b378092fb70886c9a83ff1"], "tags": ["bounty"]}" |
created | 2017-01-27 05:07:21 |
last_update | 2017-01-27 05:07:21 |
depth | 5 |
children | 1 |
net_rshares | 330,467,472,632 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 SBD |
curator_payout_value | 0.000 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 680 |
author_reputation | 24,609,971,519,844 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
robrigo | 0 | 330,467,472,632 | 100% |
Sorry, just got what you were saying about the drafts.. Yeah, that would be an awesome feature too! You should email @sneak if you are interested in working on those things. Ultimately it would be on you to develop the change and ensure you were following the coding conventions of the project, but he should at least be able to let you know if what you are working on is something they are interested in - and point you in the right direction.
post_id | 1,846,511 |
---|---|
author | timcliff |
permlink | re-builderofcastles-re-timcliff-re-builderofcastles-re-timcliff-update-on-bounty-splitting-blog-and-resteem-into-separate-tabs-20170127t043423731z |
category | bounty |
json_metadata | "{"app": "steemit/0.1", "users": ["sneak"], "tags": ["bounty"]}" |
created | 2017-01-27 04:34:21 |
last_update | 2017-01-27 04:34:36 |
depth | 4 |
children | 0 |
net_rshares | 0 |
last_payout | 2017-02-27 03:35:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 SBD |
curator_payout_value | 0.000 SBD |
pending_payout_value | 0.000 SBD |
promoted | 0.000 SBD |
body_length | 444 |
author_reputation | 262,354,724,187,317 |
root_title | "Update on Bounty - Splitting Blog and Resteem into Separate Tabs" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 SBD |
percent_steem_dollars | 10,000 |