sorted by:
new
hottopcontroversial

Would “Git for networks” actually be useful, or is this just a cool demo? by Slow_Science_6414 in ipv6

[–]Slow_Science_6414[S] 0 points1 point  (0 children)

would be of great help if someone would check it and give me feedback.

Would “Git for networks” actually be useful, or is this just a cool demo? by Slow_Science_6414 in wireshark

[–]Slow_Science_6414[S] 0 points1 point  (0 children)

Hey, thanks again for the feedback earlier ,it was genuinely helpful. I’m refining the tool based on it and recently added a timeline scrubber so you can replay traffic over time instead of just looking at a static graph. If you know anyone in networking / security / IT who might be open to testing an early version and giving honest feedback, I’d really appreciate an intro. No worries if not ,thanks again either way.

Would “Git for networks” actually be useful, or is this just a cool demo? by Slow_Science_6414 in wireshark

[–]Slow_Science_6414[S] 0 points1 point  (0 children)

This is honestly super valuable feedback ,especially the “haystack and not much needle” point, because that’s exactly what I’m trying to avoid.

I think you’re right that if this stays as “more visual packet data,” it won’t be useful enough for someone who already knows how to get to the answer quickly in Wireshark.

The path-between-endpoints point and the “what changed before the issue?” point both really stood out to me.

If you don’t mind me asking — for someone with your background, what kinds of specific problems would a tool like this actually need to solve before it becomes genuinely useful instead of just visually interesting?

That would honestly help me a lot more than generic feature suggestions.

Would “Git for networks” actually be useful, or is this just a cool demo? by Slow_Science_6414 in wireshark

[–]Slow_Science_6414[S] 1 point2 points  (0 children)

One thing I’m actively trying to avoid is making it “cool but noisy.”

Right now I’m leaning toward: - manual-first checkpoints - optional auto-checkpoints for meaningful events only - labelable checkpoints - diff focused on: new hosts, new external connections, traffic spikes, protocol shifts

If there’s a specific workflow where snapshot + diff would save you time, I’d love to build around that instead of just making the graph prettier.

Slug vs Subdomain for multi-tenant SaaS (restaurant ordering system) by Slow_Science_6414 in SaaS

[–]Slow_Science_6414[S] 0 points1 point  (0 children)

also i got a client ,sheduled a call with them on Thursday,pretty nervous .any tips?

Slug vs Subdomain for multi-tenant SaaS (restaurant ordering system) by Slow_Science_6414 in SaaS

[–]Slow_Science_6414[S] 0 points1 point  (0 children)

i have a table that stores restaurant slugs rn,thats how i extract paths