Hello Steemians, this is @upvu.witness! It's already half a year ago. We submitted the DIP proposal below in early October of last year, and received a call from the Steemit Team and CDR to start developing the DIP. We are very honored that our team is the first to start DIP.
You can check the details of the DIP proposal we submitted through the link above, and briefly introduce it again below.
We plan to start setting up our own server environment for Condenser testing for full-scale development next week, with the goal of completing all development within 8 weeks.
Proposal Overview
Num | Entity | API Endpoint URL |
---|---|---|
01 | API Endpoint Options | - Collecting a list of available API endpoints |
02 | Templates and Drafts* | - Add customizable header and footer features, Provides several fixed useful templates, Add draft save and load function |
03 | Loading comments | - Add a separate [Load comments] button to the bottom of the post and load it separately from the post content |
Common tasks of deliverable above
- Check component codes, file and folder structure
- Implement the code changes following the conventions of the project
- Post-changes software compatibility testing
- Reviews, corrections, final tests, pull request
[NOTE]
- A cloud provider is required to store drafts in the cloud, and for steemit.com, it is appropriate to use a cloud owned by Steemit Inc.
- It is also possible for our team to provide a separate cloud, but as a public frontend for steemit.com, we need to consult with Steemit Inc in the future.
Since the Steemit Team responded that it is difficult to provide a separate cloud for security reasons, the @upvu.witness team will initially provide a separate cloud server. (The cloud operating budget is not included in the DIP budget as mentioned above) Our team will resubmit the budget related to cloud costs as a separate proposal next quarter.
API Endpoint Public Confirmation Request
We intend to openly collect information on all API endpoints operated by Witness teams, developers, and general individuals, including the basic API endpoints operated by the Steemit Team.
All API endpoints that have been collected are provided as one of the options that users can select from the list. (Please make sure that it works normally)
If your API Endpoint is not listed below, please leave the URL of your API Endpoint in the comments!
In particular, the following witness teams are the teams receiving community governance votes from @upvu.proxy and strongly request that they provide at least one API Endpoint.
We plan to refresh the governance vote in Q2 2023, at which time inactive witness teams may be excluded from the vote.
@alexmove.witness @bangla.witness @boylikegirl.wit @cotina @dev.supporters @dlike @etainclub @ety001 @future.witness @italygame @jswit @justyy @maiyude @mascosdk @newsteem.witness @pennsif.witness @protoss20 @rnt1 @roadofrich @seven.wit @starlord28 @steem.history @steemchiller. @steemit-market @steemit.kor @successgr.with @symbionts @tomoyan.witness @xpilar.witness
DIP Development Roadmap
Our team's outline development timeline is as follows: We will share details with the community through development progress reports every 2-3 weeks. Of course, this development progress report will also be posted on the @dip.team account in collaboration with CDR.
All development schedules and progress are managed through a separate schedule table that can only be viewed by Steemit Team and CDR members.
Week No. | Start Date | End Date | Plans (To-Do) |
---|---|---|---|
WEEK 1 | 2023-03-20 | 2023-03-27 | - Collect available API Endpoint data / - Open collection of API endpoints that can be newly added through Steemit postings |
WEEK 2 | 2023-03-27 | 2023-04-03 | - Check code convention, component codes, file and folder structure / - Server environment setup and execution test for condenser test |
WEEK 3 | 2023-04-03 | 2023-04-10 | - Implementation of API Endpoint selection options (on steemitwallet condenser) / - Changed code application, software compatibility test, review |
WEEK 4 | 2023-04-10 | 2023-04-17 | - Draft & Templates storage server installation / - Build Restful API / - Creating and saving templates |
WEEK 5 | 2023-04-17 | 2023-04-24 | - User verification function through active key signature / - Added Draft & Templates function to Condenser / - Development of template import function |
WEEK 6 | 2023-04-24 | 2023-05-01 | - Added Draft & Templates function to Condenser / - Draft writing and saving function / - Draft import and modification function |
WEEK 7 | 2023-05-01 | 2023-05-08 | - Develop details related to the Loading Comments feature |
WEEK 8 | 2023-05-08 | 2023-05-15 | - Wrapping up development progress (Reviews, corrections, final tests, pull request) |
We aim to complete development within the previously promised period, but our more important goal is to release a product with a high degree of completion rather than rushing to complete development within the deadline.
We are truly excited to join the Steemit Team, CDR and Steemians on this great journey called Steemit DIP. We look forward to more exciting news coming to the Steem ecosystem.
Best Regards,
UPVU Team
That is very nice news! I am very happy that development is continuing.
I currently have a seed and witness node set up, but no API endpoint yet. That will definitely follow though. Will it be possible to expand the API selection list later (in development phase or even after the rollout)?
There should also be the possibility to remove addresses that no longer work.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I am very happy that real development work is starting. I wish you success.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Good news, positive changes for a better future.
Hope you can choose us in the future which can allow us to collaborate further together in building an Ecosystem on the Steem Blockchain.
Please consider and review my presence as a witness on Steem, thank you very much.
Good luck !
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
!test !thumbsup
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hello @upvu.witness! You are wonderful!
command: !thumbsup is powered by witness @justyy and his contributions are: https://steemyy.com
More commands are coming!
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hi there,
Seems that you missed our api: https://api.futureshock.world
Cheers,
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I added url. Thanks.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Seems that you missed our api to @xpilar.witness
https://api.worldofxpilar.com/ is my api endpoint
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
I added url. Thanks.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit
Hi, these features could test on https://steemitdev.com .
BTW, the images service is not working on https://steemitdev.com now.
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit