artski

12 ms·

1.
Show HN: Volt – Fast, Git-native API client written in Zig (Postman alternative)(github.com)
5 points by artski 6mo ago|0 comments
2.
by artski 1y ago
I don’t know how South Korea works politically but Ik an example of Malaysia - they spent years on their nuclear road map -> new administration comes in who hates nuclear it gets scrapped. And now they are back to one that doesn’t mind i
3.
by artski 1y ago
Yeah I think the world is screwed. These aren't things you can shut down instantly without losing a bunch of money/the time not spent building better alternatives - all these projects have long lead times.
4.
Maybe we should be designing for machines too(substack.com)
3 points by artski 1y ago|1 comments
5.
by artski 1y ago
I’ve been thinking a lot about how new features and systems are built lately, especially with everything that’s happened over the past few years. It’s interesting how most of the AI stuff we see in products today is basically tacked on afte
6.
by artski 1y ago
Yeah I thought about this and maybe down the line, but wanted to start with the pure statistics part as the base so it's as little of a black box as possible.
7.
by artski 1y ago
Crazy how far people go for these things tbh.
8.
by artski 1y ago
For each spike it samples the users from that spike (I set it to a high enough value currently it essentially gets all of them for 99.99% of repos - though that should be optimised so it's faster but just figured I will just grab ev
9.
by artski 1y ago
It's a project I'm making purely for myself and I like to share what I make - sorry I didn't put up most effort in the commit messages, will not do that again.
10.
by artski 1y ago
Well I initially planned to use GraphQL and started to implement it, but switched to REST for now as it's still not fully complete, just to keep things simpler while I iterate and the fact that it's not required currently. I’ll br
11.
by artski 1y ago
It would still count as "trustworthy" just wouldnt come out to 100/100 :(.
12.
by artski 1y ago
Not a bad idea tbh, maybe an additional how long issues are left open, would be a good idea. Though yeh thats why I was contemplating of not necessarily highlighting the actual number and more have a range e.g. 80-100 is good, 50-70 Moderat
13.
by artski 1y ago
I haven't done that before so it would be a small learning curve for me to figure that out. Feel free to make a pull request.
14.
by artski 1y ago
Lol yeah tbh - I just made it without really thinking of an audience, just was looking for a project to work on till I saw the paper and figured it would be cool to check it out on some repositories out there. That part is just me asking gp
15.
by artski 1y ago
Yeah to be fair would be great, sometimes just giving a nudge and showing people want these features is the first step to getting an official integration.
16.
by artski 1y ago
Fair take—it's definitely context-dependent. In some cases, solo-maintainer projects can be great, especially if they’re stable or purpose-built. But from a trust and maintenance standpoint, it’s worth flagging as a signal: if 90% of c
17.
by artski 1y ago
Basically what I mean by it is for example a repository appears to be under a permissive license like MIT, Apache, or BSD, but actually includes code that’s governed by a much stricter or viral license—like GPL or AGPL—often buried in a sub
18.
by artski 1y ago
Yeah to be fair I need to clean it up, was stuck in the testing diff strategies and making it work and just wanted to get feedback asap before moving on to the next step (didn't want to spend too much time on something and turns out I
19.
Show HN: CLI that spots fake GitHub stars, risky dependencies and licence traps(github.com)
122 points by artski 1y ago|72 comments
20.
Scaling AI agent tooling: ideas for dynamic discovery and execution workflows
2 points by artski 1y ago|1 comments
21.
Show HN: FluffyTagProcessor – Lightweight streaming parser for LLM tagged output(github.com)
1 points by artski 1y ago|0 comments