cxam

If you're using Chrome (65+), you can easily bypass any validations/logic by using local overrides (https://developers.google.com/web/updates/2018/01/devtools#o...). As marcolussetti said, it's worth trying out.

You should also consider how you intend to backup the data as there currently isn't a process to do that outside of writing something yourself to periodically download the keys. This will add to your usage cost depending on what your strategy is, for example, backing up old keys that gets updated vs only new keys by keeping track of the cursor.

I believe NX is aiming to bring in Vue support through their plugin system, but yea, I understand that it would make it easier in your case since it already supports Angular. If you like the monorepo setup and looking for a more generic solution then checkout lerna (https://github.com/lerna/lerna).

> I really do love Vue, but I need structure, because as a human I have terrible memory. I don't love unit testing, and I barely love integration testing, so strict typing and good naming is key to my style of coding.

Vue, as simple as it is, can have structure and easily adopt to large scale projects. As I mentioned in my previous comment, you would have not had any issues using TypeScript with it.

> I hit a wall with Vue, which I've similarly hit with AngularJS, at some point I hit a level of complexity that Angular doesn't allow, but Vue does.

What exact issues did you have with Vue? Just curious as nothing you've mentioned so far are actual issues, but rather, you having better experience with using Angular.

Funnily enough, I went through a similar thought process but between React and Vue. What's uncanny is that it was also for a video annotation service I was building (https://tagx.io/). I ended up going with Vue and like Plopdown, used Plyr (https://plyr.io/) as the video player (also a great project). Your three reasons for not continuing to use Vue, I'm wondering if that's really because Angular was your comfort zone?

  [1] Typescript + Vue works well (that's how I built mine). 
  [2] You could have used RxJS with Vue. 
  [3] Vue has less boilerplate code than Angular and wouldn't have made this project any more difficult to maintain

However, it doesn't overlay any annotations over the video like plopdown does (which is a great feature!), only on the side of the video.

I've been using Caddy v2 all through beta/RC and glad it's finally stable with a proper release. I moved away from using nginx for serving static content for my side projects and prototypes. I'm also starting to replace reverse proxying from HAProxy as well. The lightweight config and the automated TLS with Let's Encrypt makes everything a breeze. Definitely has become part of my day-to-day.

Thanks again for the feedback, if you do have any other ideas and this post gets locked for commenting after two weeks, then please don't hesitate to create an issue or drop me an email as listed here: https://tagx.io/support/general/contact

This is already possible using hotkeys and documentation for it can be found here: https://tagx.io/support/advanced/hotkeys

(2) then compose tracks by selecting any two timestamps, with the ability to add tags to timestamps or tracks while the video is still playing or after

Just to clarify, do you mean the ability to add the current point in time of the video to different tracks? In which case, this is already possible using multiple hotkeys as outlined above. Please let me know if this is not what you meant.

(3) with the link just playing between timestamp a and timestamp b

You are able to create a loop between a tag or a set of tags, please see loop settings outlined here: https://tagx.io/support/interfaces/video

With regards to autoplay, this is a bit finicky depending on the browser and is usually not recommended due to the negative user experience so I didn't include an option to enable this feature.

Hope this is clear, let me know if you have any more questions.