2025 is off to an interesting start! There are a lot of eyes on the Hive price, since it is making bigger moves.
I'm continuing to work on user experience and error handling for vscode2hive. The goal is to bring it from proof of concept to public app store listing. The biggest missing feature is image support.
Difficulty of inserting images could be a show stopper for this project. Attempting to paste an image into the VSCode editor tab adds a markdown image placeholder, but does not do anything with the image file. i.e. .
Ideally, there can be a way to extend VSCode to attach a customer event handler for the paste event. Such that pasting images can be as seamless as it is with PeakD and other front-ends. Magically uploading the image to a Hive community image server, and then inserting the unique URL of the image in markdown.
If a custom event handler is not possible, I may have to add a separate command for the "upload image" action. This solution is less convenient but it could work, something like this. Ctrl-Shift-P to open the command palette, then choose "vscode2Hive: upload image", then choose the path to image file, presto!.
I also want to add a feature that records when and where document is published. Markdown support comments, kinda. You can do something like this: [comment]: <> (This comment will be invisible) and the text will hidden in the rendered view.
VSCode2Hive, after broadcasting the post, would modify the document, and add a header with comments to record metadata. When it was published, where it was published (permlink), and for convenience, a link to popular Hive front-ends where the post can be viewed. Also title, tags, community, etc.
The metadata comment would appear at the top of the markdown file saved on your computer. Such that the history can saved there and the author can see that the document was previously published. Without this, duplicate publishing could be an issue.
vscode2hive extension itself can read the metadata header in the markdown file. This scenario can have special handling. The extension can publish revisions to the document using the same permlink, instead of publishing duplicate posts.
Other updates:
This week I connected with
@alohaed who is actively exploring the Hive ecosystem. Ed is reminding me about many things around Hive that I take for granted. There is much Hive honey to taste when you dig deep enough into the Hive.
I am still enjoying Crownrend. I had to adjust my strategy a few times. Alliances are "work in progress", and I'm looking forward to teaming up with some friendly kingdoms. 👀
@dadspardan
If you made it this far, thanks for reading.
Cheers,
HiveTrending
Broadcast via vscode2Hive
