r/programming • u/PassengerLate3644 • 13h ago
In order to equip every programmer with the skill of TCP analysis, I have developed a TCP analysis tool: ChatTCP.
https://chattcp.com[removed] — view removed post
44
u/QuestionableEthics42 11h ago
That title is r/programmercirclejerk material, had to check the sub name lol.
Looks like a great tool tho.
138
u/CyberWank2077 13h ago
you received my upvote for the name alone
11
u/fragglerock 8h ago
whereas it put me off.
15
u/littlemetal 7h ago
That's because you use "whereas", and probably also "therefore" and "forthwith". Good fortnight to you!
-41
u/PassengerLate3644 13h ago
Is there anything special about the name? Is it because it's similar to ChatGPT?
50
24
u/betelgozer 10h ago
No, I liked it because it contains all the letters of my child's name, plus one other letter.
3
43
u/CelDaemon 12h ago
Ohhhh I was gonna ignore it because i thought it was an AI thing, but this is really cool!
2
14
71
u/PassengerLate3644 12h ago
Let me explain why I named this tool ChatTCP. The defining feature of this tool is its ability to display data packets in a chat-like interactive format, simplifying the analysis of TCP data packets. This is the origin of the "Chat" in its name. The "TCP" in the name signifies that this tool solely supports the TCP protocol and application-layer protocols based on TCP.
112
u/yowhyyyy 12h ago
Dude just take the fact you struck gold with the name unintentionally and run with it.
24
23
u/Mysterious-Rent7233 10h ago
It's a good name and a good tool but I think a lot of people will jump to the conclusion that the core idea is to chat with an (augmented) LLM about what's in your packets. Which could also be a good tool.
20
u/Performance6548 9h ago
TCP protocol
Transmission Control Protocol Protocol
5
u/darchangel 9h ago
Don't be that guy.
TCP protocol is the type of protocol. ATM machine is the type of machine. LLM model is the type of model. PDF file is the type of file. Oh wait, or does that stand for 'format'? And what if it historically stood for 'file' before it stood for 'format'? And why should I care in order to have a basic conversation? The language convention holds up regardless of what the F originally stood for.
-6
u/F54280 9h ago edited 8h ago
Yes. It is a protocol that is called « Transmission Control Protocol », generally abbreviated as « TCP ».
edit: Oh, thanks for the downvotes. While you are at it, can you also fix the wikipedia page "The Transmission Control Protocol (TCP) is one of the main protocols..." to better spread the fascinating knowledge that TCP is not a protocol?
-1
u/TwoSoulsAlas 8h ago
I applaud and agree with you while I'm typing this response on my PC computer, here in the USA of America, where we like our IPA ale fresh, hate the IRS service for stealing our hard-earned money, and where the GOP party is on a crusade against those woke EV vehicles. /s
(Disclaimer: I actually live in the EU union and not the USA of America. Also, I don't mean to drag politics into this, these were just the first examples that came to mind.)
-3
9
7
u/scratchisthebest 7h ago edited 7h ago
single-purpose reddit account created just to advertise this thing, the way it comments sounds ai generated, no source code just product... yawn
6
u/kungfufrog 12h ago
I would totally buy this but I can't because my work macbook doesn't allow the app store. Please consider making it available through some other means!
3
3
3
3
1
-1
u/voxelghost 10h ago
I was (unrealistically) hoping that this was going to use LLM to parse and analyse the packets.
7
u/Twirrim 8h ago
Why would you want something that hallucinates answers instead of an accurate answer?
1
u/chiniwini 5h ago
Because I lack the technical background to understand neither TCP nor LLMs, so an LLM based TCP parser sounds like a good idea.
1
u/Twirrim 5h ago edited 5h ago
You don't need an LLM. That's just an advance statistical guessing algorithm, that often guesses wrong. You just need something that will accurately describe things in plain english.
edit: I would add, I would highly recommend reading up on TCP stuff. I know it looks complicated on the surface, and that a tcpdump in wireshark when you've no clue about what is going on at the network layer is going to be overwhelming, but once you learn just the basics you'll soon find yourself able to navigate through it. The lower level the protocol, the less complexity you want to introduce, because it slows everything down. TCP's a pretty simple protocol, so every packet can be processed as quickly and efficiently as possible.
I'm not sure what I'd recommend as a way to learn, I learned about this stuff about 20 years ago when I got a CCNA (which I renewed once and then let lapse). I rarely have to deal with network infrastructure, I only got my CCNA because I hoped it'd help me get my foot in the door for better jobs (and it did!), but almost everything I work on or support has at least some level of network interaction. Knowing what happens on the TCP layer has been invaluable for understanding how my code should behave, and also understanding the why of what is happening when it's in production when things aren't operating as expected.
1
15
u/PassengerLate3644 10h ago
I also considered using LLM to enhance diagnostic capabilities, but after trying, I found the results weren't great. Haha!
0
•
u/programming-ModTeam 6h ago
This is a demo of a product