We have a sign-up because we ensure users accept our terms of service and acceptable use policy before creating their first video, which affirms they understand how their data is used (legally required in most US states) and will not use our technology to cause harm.
Funny how other sites can do this with a birthday dropdown, an IP address, and a checkbox.
>We have a sign-up because we ensure users accept our terms of service and acceptable use policy before creating their first video
So your company would have no problem going on record saying that they will never email you for any reason, including marketing, and your email will never be shared or sold even in the event of a merger or acquisition? Because this is the problem people have with sign-up ... and the main reason most start-ups want it.
I am not necessarily for or against required sign-ups, but I do understand people that are adamantly against them.
Do you realize that this or similar technology will eventually end in every computer really soon? By building walls, you're essentially asking your potential users to go elsewhere. You should be as open as possible now that there is still room and time for competition.
This thread has opened my eyes to how many similar products exist; beyond your companies' and OP's. Was yours the first? Could the other companies make the same claim about yours? Do you make the same claim about the others?
I welcome competition, but they have made disingenuous claims about being first after having chatted with our team (in person), are using celebrity deepfakes for their advertising, and have 1-1 copied our UI down to the three panel mobile layout and autocrop button.
To be fair your UI looks much better and the layout of both these sites is so basic (not a bad thing), it should be the last thing to worry about. Better product will win so focus on that, because except for ones ego, no one else cares who's "first".
You've expressed this concern, and your comment has been upvoted. The brigade of newly registered users echoing these talking points on this topic is not necessary and undermines your point.
Interesting! Are you saying you would first want tools to really design your character, and only after start making videos with the character you built? That's interesting.
How convenient that new user ‘jenintogen’ replied to new user ‘genaiguy’’s mentioning Hedra by asking for a link, giving you an opportunity to organically reply with the URL of your service.
Looks like there’s an enthusiastic marketplace of real grassroots users.
Super curious if you're evaluating options what you're finding on the market we (hedra.com) are evaluating options right now and the cost is astronomical when you go above 500,000 contacts. We're exploring Brevo (FKA sendinblue which allows unlimited contacts) vs. Salesforce.
I'm using this just for transactional emails. I have another solution for marketing emails.
I was using SendGrid's WYSIWYG templates for many emails, but I'm re-doing them in my own code so that I can more easily change providers in the future. I'll just need the ability to send HTML emails.
If you are looking for just the visual email template builder part, check out EmailBuilder.js (https://github.com/usewaypoint/email-builder-js) - it's a free and open-source builder that also has a hosted playground.
> That's a bold claim. Migrating from NCM + clangd integration is absolutely slower.
You'll have to define slower (time to diagnostics, time to completion, are you really talking about the performance of nvim-cmp instead, etc.) preferably in a bug report with benchmarks. I've done several rounds of performance optimization since 0.5, and I haven't heard any complaints since 0.6 when I swapped out our json decoder.
I would just back up @mjlbach here, and provide my datapoint as a neovim user: I have no complaints with regards to neovim's builtin LSP client, especially with regards speed.
Lspconfig currently has 3 parts, the default settings for the servers, an implicit project detector to trigger when to launch the servers (conditioned on filetypes and some patterns), and the infrastructure to manage launching/shutting down/attaching buffers to servers as you open files within the same project.
Eventually we'd like parts 2 & 3 to be in core as a "projects" module, leaving separate "project patterns" and "server settings" as mostly metadata containing repositories.
That would open the door for third party plugins to create customized project templates which map keybindings, set formatexpr, pass custom server settings, etc. similar to how coc.nvim has coc-pyright, coc-gopls, etc. These plugins could also handle installing language servers automatically should they choose to offer that.
There's also nvim-lsp-installer, but I really don't like the approach it takes of hijacking lspconfig's setup.
Source? We have an extremely extensive test suite for the built-in client that must pass for every merge, and we currently have ~30 open issues on the issue tracker (with a good chunk of those being feature requests).
Yeah I can second this. I've been using native LSP since 0.5 nightly and it's been nothing but solid. The only thing that occasionally gave me issues were tree-sitter crashes (unrelated to LSP), but even those seem to have all been fixed by now.
If you're having a powershell issue, you can file an issue. I'm not a Windows user or powershell user, but when I tested the PR (before merging it) I was able to get it running in a minute.
This is fine in the nvim-cmp world, there's a config example in the lspconfig wiki, it's about 5 lines for the integration. The recommended lspconfig configuration (included snippets and autocompletion) has less lines of code than the example in the readme for coc.
> formatting
This is built-in to neovim's LS client (vim.lsp.buf.formatting()), adding an external formatter can be done with formatexpr (built-in)
