UI optimizations for mobile devices
A much requested feature due to many of our users are uploading DTube videos from mobile devices (as well as for SEO optimization), I have made some modifications to the HTML/CSS code to ensure that the webpage is easy to read on mobile, as well as desktop. All it took was the line of code below, as well as some additional CSS code written specifically for mobile. For example resizing some text so that they're readable, and hiding the header text (but leaving the #onelovedtube logo visible) because there's no space for the text to be displayed correctly.
<meta name="viewport" content="width=device-width, initial-scale=1">
There are no server side code modifications in order to achieve this.
STEEM Article Body overwrite field!
Another feature that was missing, is here! Many DTubers would like to have some other content to be displayed on Steem frontends like Steemit and Busy.org, that is different than the description section of the DTube video watch page. This will not be a required field, leaving this blank will set the contents of the video description to be content of the article body in the Steem post (underneath the thumbnail).
Image uploads for STEEM article body overwrite
Not in the official DTube uploader at all, it's possible to upload images (not video thumbnail) for the Steem article body if the user would like to overwrite it with other content. All it takes is to select an image (all image formats supported, hence the
image/* wildcard here) after a button click, and it will upload the selected image to the server, and adds the file to IPFS. It then returns the link to the image (we're using cloudflare-ipfs.com gateway here) in a markdown style, and appends them to the end of the article body. It's up to the user to move it to the location where they want the image to be displayed.
More efficient uploads with async.js + js-ipfs-http-client
I have changed a huge amount of the backend code to improve the efficiency of how file uploads are processed. Now that I have successfully integrated the js-ipfs-http-client API (formerly known as js-ipfs-api) with trickledag add. It was due to incomplete docs that I couldn't figure this out so I used ShellJS when I first started developing DTube IPFS tools like this one, but now I figured out the right way (and the correct options args) to implement this API so we shall go with this.
One of the advantages of using this uploader instead of the official DTube uploader is that there are no IPFS/encoding queues, which means it's easier to scale with more users, therefore it will help DTube to achieve mass adoption as a mainstream video platform. In the previous versions, the IPFS operations and sprite generation were handled asynchronously only for code execution across multiple users at the same time. However, these individual operations were run in sequence, causing the callback hell that I recently found out.
Thanks to async.js, all IPFS add operations and sprite generation can be run at the same time, even though only one user is uploading at the time. This improves uploader efficiency, and allow scalability, should more code needs to be run to process uploads in future updates when more and more new features get introduced in this uploader, or DTube in general.
Optional video upload fields for lower res versions
Previously only source video files are supported, and the only video file that gets added to IPFS and have its hash submitted to the Steem blockchain. Now, users may encode source videos themselves into multiple lower res video files so that they can be uploaded separately in the advanced tab, in addition to the source video files itself. By doing so it will allow the video to play for users with poor internet connection smoothly, but at lower quality.
Updates with OneLoveIPFS service
I would like to take this opportunity to give you some updates with the hosting service offered by @onelovedtube.
Announcing https://video.oneloveipfs.com IPFS gateway
This would be a high performance IPFS gateway that serves only pinned videos. In order to achieve this, a NodeJS HTTP reverse proxy is required to handle it, in addition to the NGINX server that handles domains and HTTPS encryption.
Requests of files that are non pinned will return a 404 error instantly.
The reverse proxy source code can be found here.
Announcing the @onelovedtube embed player
We have forked DTube's embed player to adapt our IPFS gateway (as described above), and we're using @anyx's full RPC node instead of Steemit Inc's node that DTube uses. The embed player may be accessible through https://emb.oneloved.tube. The URL syntax is the same.
(will hide logo on player and will autoplay)
The forked source code may be found here
Over the past few months we have received some valuable feedback from our customers. They have made a DTube video about it and would like to link some of the good ones here, for those who are new to this and want to find out more.
- OneLoveDTube Uploader Test & Review -- W/Special Guest @Gray00 by @vladivostok
- Are Your Videos Getting Deleted On Dtube? Here Comes The Solution OneLoveIPFS | Step By Step Tutorial | MVD by @mvd
All review videos mentioned above are uploaded through https://uploader.oneloved.tube and are hosted on our servers.