[pletnes]

I agree, mostly. But since when isn’t it obvious that posting data with a browser will send that data somewhere? And the users here are (from what I can tell) developers.

I think this is a cool tool for public data and obviously I can’t paste private data sets on any public website, ever.

[TeMPOraL]

It's not obvious ever since some of those tools started to blur the line; there are plenty of such little utilities that do everything client-side, or at least claim so. I don't use them with anything but public data, as it takes one mistake or one silent update for the data to get shipped off my machine, but there's a whole generation of devs now who were growing up with webapps and online-first software, so I can easily see some developers making this mistake.

Plus, they offer a VS Code extension. It's not so obvious that it's just the same public website underneath.

Additionally, developers who understand those concerns kind of expect that other developers also understand them, and thus would not create an on-line tool like this in the first place.

[simplotek]

> I agree, mostly. But since when isn’t it obvious that posting data with a browser will send that data somewhere?

I'd be surprised if anyone at all, specially developers, expects a browser to do anything other than transfer data to/from the internet.