izakfr

This looks cool! Stablecoin on-ramps are still not perfect. I think it's important to meet customers where they're at, so a lot of the banking-centric onboarding options won't work everywhere. Don't really understand a lot of the criticism on this thread, seems to mostly be caused by the "crypto = bad" opinion. Good luck with Karsa, keep up the good work!

CTO of Vigilant here. Does anyone have ideas on how to do versioning for an SDK that you change often? Would putting new features in a "beta" release version make sense?

This is really awesome, great job!

Thank you for the feedback, this is helpful!

One of the features we're excited about adding is a way to cache values locally. Having control of cache ttl and refresh intervals would be a must if we added that. You're right that the tool should just work without the developer worrying about affecting latency.

You could make a variable like `rollout_percent` that is an number. It could be set to 1. Then in your app you could do something like:

const rollout_percent = await varse_client.getNumber('rollout_percent');

const random_number = Math.random() * 100;

if (random_number <= rollout_percent) {

// do gated action and will trigger for 1% of users when rollout_percent === 1

}

The axios point is helpful, thank you for mentioning it. I'll make a bug ticket to fix.

Also, we should probably put restrictions the keyname scheme. Ideally, it should be something readable.

Just updated the repo. Thanks for the clarification.

Yeah that's a good point. We meant application config. I will change the repo's description to reflect this.

Feature Flags looks like it's crafted around automated rollouts. Varse was designed to be more manual, just for reading / writing key - value pairs. You can use it to store long-lived variables like database_url. It could also be used for short lived variables like percent_db_migration_rollout.

Have you used Feature Flags in the past? I'm curious what your experience was.

It's a variable or config that gets injected into a server at runtime. At least that's what I've heard it called in the past. I think it's interchangeable with environment variable.

The two-way sync does seem to be another problem with these export tools. Thanks for sharing, I'll take a look!

This is awesome! I’ve been working on optimizing a javascript library recently and am feeling the pain of performance testing. I’ll check this out.

Since almost all websites use HTML / CSS, its the output format we wanted to target. If you don't use HTML it breaks things like SEO, accessibility, etc.

Our current API is design in the editor -> HTML / CSS. Exposing the internal data structure wouldn't work well. We've changed the structure multiple times in the past few months. We have plans to change it rather dramatically in the future.

Wow, this is really cool! Thanks for sharing.

At the top of this post there is a link to the playground.

Here's the link: https://app.repaint.com/playground

Yes, repaint.com is made in Repaint.

What do you mean drawn live? The content is animated, but is still present in the DOM for indexing purposes.

We actually looked into Tldraw. I read a lot of the source code and their editor is impressive. We ran into performance problems at around 1000 nodes when panning and zooming. After seeing that, we decided to make the jump to WebGL.

The engine is written in Typescript.

Here's a good place to start for the basics: https://webglfundamentals.org/

We added a link to a playground in the post so that you can try Repaint without creating an account.

This has been linked in the comments already, but check this out: https://faultlore.com/blah/text-hates-you/

What makes you want to host the website outside of Repaint? Is it related to website performance? We want to do things like optimize website speed and use CDNs to cache images. Is there something specific you need a hosting platform to have?

That's the default speed that Loom plays, unfortunately we can't update it.

Thanks for the screenshot and info, we'll fix this!

We agree that making the editor match the browser is super important. At some point we'll have implemented the whole CSS spec. Then, it should always match exactly.

Or at least we'll match Chrome. Sometimes browsers don't match each other.

Do you mean make Figma's editor in Repaint's editor? We can't even make Figma outside the editor :)

There's likely a few settings that you'll have to update on the sections. If the page is a block layout the width of the navbar and container should be auto (to fill the page).

We're currently working on our onboarding to solve this. It should be easier to make a basic responsive page from the templates.

That's a good point. We built repaint.com in Repaint and we don't currently have videos in our editor. We will likely add a demo video on the site once we can.

What do you mean by embedded? Like the editor can be embedded on other sites? Or the websites we publish are embeddable?

We've looked over this essay a few times and we can relate. Rendering text is not for the faint of heart :)