Callicles

5 ms·

1.
by Callicles 2mo ago
Done
2.
by Callicles 2mo ago
I added runtime by adding a resolver and removing it. I also made the map responsive.
3.
by Callicles 2mo ago
ha that could be less handy but cooler
4.
by Callicles 2mo ago
I added the ability to specify a config file for the resolvers definition. This is not runtime, though. I will keep that in mind for another release. Thanks for the follow-up :)
5.
by Callicles 2mo ago
Addressed the feedback
6.
by Callicles 2mo ago
Released a new version with the suggestion ;)
7.
by Callicles 2mo ago
Thanks for the feedback!
8.
by Callicles 2mo ago
This was 100% vibe-coded with Claude Code and Fable. https://x.com/thatsFrScience/status/2073741209592295866 Thanks for the feedback, though, and for taking the time to look at the code. I can ship a round of clea
9.
by Callicles 2mo ago
Yeah, I used to use https://www.whatsmydns.net/ . I wanted it in the terminal without ads.
10.
by Callicles 2mo ago
That's what the tool is doing - querying a bunch of public resolvers around the world to see the state of what they resolve to. Since end users usually use DNS servers close to their location, this gives an idea, around the world, of w
11.
DNSGlobe – Rust TUI to watch DNS propagate around the world(github.com)
83 points by Callicles 2mo ago|70 comments
12.
Show HN: Contributor License Agreement Bot for GitHub – Next.js and Postgres(cla.fiveonefour.com)
1 points by Callicles 5mo ago|0 comments
13.
by Callicles 11mo ago
Hey, We went from the get go to that infrastructure for multiple reasons in the first place: * Having a durable buffer before ensures if you have big spikes that gets eaten by the buffer, not OLAP which when it is powering your online dashb
14.
by Callicles 1y ago
Not yet, but we have that on the roadmap!
15.
by Callicles 1y ago
MooseStack maintainer here. I helped author the post. Happy to answer any questions, but very curious to get feedback. We’ve been thinking a lot about developer experience for the OLAP stack.
16.
by Callicles 1y ago
I believe I am saying child processes can write to stdout as the main process is shutting down. Also, if the child processes are not shut down properly and are left dangling, and the child processes were set up as 'inherit' to be
17.
Fixing Ctrl+C in Rust terminal apps: Child process management(fiveonefour.com)
110 points by Callicles 1y ago|58 comments
18.
Live Stream Diffusion: AI-Powered Video Makeovers in Real Time(about.decart.ai)
1 points by Callicles 1y ago|0 comments
19.
by Callicles 1y ago
Not sure if this is what you are asking about, so if I misread feel free to correct me. You don’t have to install moose first on the deployment machine, in the tutorial I go through that to generate a dummy moose application to be deployed.
20.
by Callicles 1y ago
Hi! We are built on top of them. Right now the techs above are what’s backing the implementation but we want to add different compatibilities. So that you can eventually have for example airflow backing up your orchestration instead of temp
21.
by Callicles 1y ago
Interesting. How do you do dependencies between those pieces of infrastructure if there's any? For example, in our Docker Compose file, we have temporal that depends on progress and then moose depends on temporal. How is that expressed
22.
by Callicles 1y ago
I put this Docker-Compose recipe together to make kicking the tires on Moose—our open-source data-backend framework—almost friction-less. What you get: • A single docker compose up that spins up ClickHouse, Redpanda, Redis and Temporal with
23.
Self-Hosting Moose with Docker Compose, Redis, Temporal, Redpanda and ClickHouse(docs.fiveonefour.com)
50 points by Callicles 1y ago|15 comments
24.
by Callicles 1y ago
;)
25.
by Callicles 1y ago
Not yet, but if you are interested in using we could chat and add support for it. We want to expand support eventually for all major OLAP provider.
26.
by Callicles 1y ago
We are currently in Production on Boreal https://www.fiveonefour.com/boreal , our hosting solution for Moose with F45 https://f45training.com , a global studio fitness studio brand. We wrote a case study with them
27.
by Callicles 1y ago
Founder here. Thanks for the interest! We built Moose because we were tired of the complexity involved in setting up and maintaining data pipelines. What makes Moose different is how it simplifies the entire workflow - from ingestion to pro
28.
Open Source Tiny Bird(getmoose.dev)
3 points by Callicles 2y ago|0 comments
29.
by Callicles 3y ago
Probably not what the people are asking for but it is what they need
30.
Rust Authorization as a Service – Oso Cloud Launches(osohq.com)
3 points by Callicles 4y ago|1 comments

More ›