kiselitza

11 ms·

31.
by kiselitza 1y ago
I've been reading this one and then the post itself a couple of times. Appreciate the suggestions and the time you took to write them down. Just not sure if those would help here (not saying they 100% wouldn't). I am all for story
32.
by kiselitza 1y ago
The Jupyter comparison isn't completely off base if you'd like to rationalise it that way. Similarity would be blending the code and the docs in a single file, where you can then also execute something . By definition, API Client
33.
by kiselitza 1y ago
It's an expression. Meaning it's not just allowing you to use some git sync workaround, but actually use it as if you would in your terminal, respecting all of its commands and conventions.
34.
by kiselitza 1y ago
Not sure how else to reply to this one, but it is the same thing as in its definition. Think less of client-server, think more of Postman, but without gazillion tabs and with docs at the same place with your API endpoint definition, headers
35.
by kiselitza 1y ago
Deb and rpm should be ready any day now. I got nothing on flatpak or appimages tho.
36.
by kiselitza 1y ago
To the best of my understanding, it is exactly what I wrote in the parent comment. It's the fact that the core lacks bits developed in the internal tool but not yet unglued from what will go in the plugins section. It's not unhear
37.
by kiselitza 1y ago
Oh, 100%. And I'm all for FOSS and an adapter architecture approach (no lock-ins of any kind). Team is aware of it, CTO wants it, so opening the core is happening. I've got no reason not to believe them. Ofc, can't expect a s
38.
by kiselitza 1y ago
Huhh, I think that may not be the worst idea. Feels like there’s room for a better shared language around this shift from everything-as-a-service towards owning your stack. Maybe even bringing back localhost is not the worst approach. Hmmm…
39.
by kiselitza 1y ago
Hey, I know you! I used to use Insomnia before all the lock-in mess while I was still a dev. Thanks for the kind words, the team will appreciate it. I hope you keep doing what you like!
40.
by kiselitza 1y ago
And we're happy to hear your feedback about it :)
41.
by kiselitza 1y ago
Well, it's a standalone, non-hosted, offline application. If you're designing your own API, you can do all the specs, docs, and if you get it up and running on localhost, you don't even need internet for testing it. If you wa
42.
by kiselitza 1y ago
The easiest way I can think of is for you to join the Discord server. Top right corner of the website (I'm aware that's not the best icon for it - addressed it to the team). Shouldn't take long until Linux is up there, tho. I
43.
by kiselitza 1y ago
Hmm, I appreciate this, for real. We'll have some more discussions on how to optimize the landing page. Curious, how do you feel about the tagline stuff? Happy to learn anything else you'd be willing to add here. We're all fo
44.
by kiselitza 1y ago
Yep, it's an Electron app. Looking to optimize it as well.
45.
by kiselitza 1y ago
Much appreciated :) Let me know how it feels, the goods and the bads, every bit of feedback is very welcome.
46.
by kiselitza 1y ago
That's correct. The intention IS to open source. Voiden evolved from an internal tool where the team bundled a lot of features into the core product. Currently separating certain things into plugins. By the time that is done, and some
47.
by kiselitza 1y ago
A repo, as in the project that contains the API specs and definitions, which you and your team are working on? Through terminal `git pull` Or you're asking me something else?
48.
by kiselitza 1y ago
Sweet, let us know how it feels. Happy to hear the feedback
49.
Show HN: Voiden – a free, offline, Git-native API Client(voiden.md)
79 points by kiselitza 1y ago|71 comments
50.
by kiselitza 1y ago
Try https://voiden.md/ As per your needs it's: - Markdown (everything in markdown, including testing and specing APIs) - Let's you write your docs in markdown around the API you're designing/testing - Gi
51.
Show HN: Progzee – open-source proxy management for ethical scraping (Python)(github.com)
1 points by kiselitza 2y ago|0 comments
52.
by kiselitza 3y ago
Just to congratulate you on going open source. I have nothing but high hopes and expectations for you folks.
53.
by kiselitza 3y ago
Well, we are the ones telling devs not to reinvent the wheel, the least we could do is offer them the means to do it smoothly. :)
54.
Show HN: Cerbos Hub - Authorization Management System
11 points by kiselitza 3y ago|2 comments
55.
by kiselitza 3y ago
If you've ever dealt w authZ, you know the pain of listing challenge. Imagine having to check permissions for every single piece of content, for every single user, on every single homepage tap (or other action that pulls abnormal amoun
56.
Unlocking efficient authZ with Cerbos’ Query Plan(cerbos.dev)
6 points by kiselitza 3y ago|1 comments
57.
by kiselitza 3y ago
Intro to Cerbos exportVariables. By transitioning from the old approach of using local variables to the new method of importing exported variables, policy authors can streamline their policies, reduce duplication, and further improve overal