Leave a comment below to introduce yourself! You can talk about what brought you here, what you're learning, or just a fun fact about
yourself.Reply to someone's comment, either with a question or just a hello. 👋
Come back next week to greet our new members so you can one day earn our [Warm Welcome Badge](https://dev.to/community-badges?badge=warm-welcome
Top comments (837)
Hey everyone! Hope you are having a great week so far wherever you are!
Just want to say welcome to DEV. Glad you came onto this platform! I promised @javz that my ultimate introduction will be in the Welcome Thread v400, so at this point, I am counting down lol.
In the meantime, I would recommend reading my guide on dev.to to get a good start on blogging and interacting with the community.
Get Started on Dev.to! A Beginner's Guide to Engage with the Community! 💡
With that said, again, welcome to DEV! To kick things off, what brings you here and why did you choose DEV?
hello
Hello and welcome.
Hi! 👋 Nice to meet you. I'm also excited to learn and participate in Hacktoberfest. All the best! 🚀
All the best to you too!
hello
hello
HI
hello wassup
hii
Hello
hello
hello
HELLO
hey
Hello
Heyyy
Hello
hello
Hi
Hey! Thank you
Claude recommended I join when I was chatting back and forth with it working on my [current] side project
Good to be here in this community of fellow developers
Welcome to @robertbutler714 ! Hi
Welcome Robert! Glad you came and thanks for sharing!
Hey, welcome! What are you learning these days?
Heelo
hi
hello
nice
hello world
hello
Hello
hello
hello
hello
hiiiii
What's up everyone!
Hi
Hey everyone. Nice to meet y'all. Very excited to be a part of the community
hii
hello,
Hello, new to dev
Hey everyone, I am Sonam from Telnyx .. just wanted to hello to everyone here :)
Hi and wish you good luck!
Hello
Tbh like everyone else, I too joined the Hacktober train but as the days go by, I’m finding myself exploring DEV as well. It’s genuinely nice to connect with developers who have been through the whole journey as well as those who are still figuring things out in the same boat as me.
Looking forward to learning, contributing and seeing where this rabbit hole takes me 🙌
hi
hello all!
Hello
Hello
hello
hellooo
Hello Everyone
I choosed dev because i love computers
hellooo
Hello
hi
Hello
Hello and Welcome
Hello and welcome!
Hello there, cool!
hello
Hello
Hi !! Happy to get to know you all
hi
hello
Hi Everyone,
New to blogs and interested to gain advise/insights from you all.
Alan
hello
Hello
hello wsg
hello
Hellooo👋🏼
hello that you for he question, am here to build and explore with great minds
Thank you for the guide!
Hello bro
hlw!
Hi
hello
Hey everyone! 👋 Greetings from Hungary!
I’m building ENTENCY UP, a browser and workstation runtime, and ENTENCY GNS, the distributed infrastructure behind it.
I joined DEV to share what I’m learning, document the messy parts of development, and meet other builders. Right now, I’m taking my networking experiments beyond localhost — where things get interesting. 😄
Anyone else working on peer-to-peer networking or distributed systems? I’d love to hear what you’re building!
Welcome! Not P2P exactly, but "beyond localhost" is where I spend most of my time too, with long-lived websocket connections to exchange feeds. The biggest surprise for me was how often a connection looks perfectly healthy while delivering nothing, so I ended up judging health by message flow rather than by connection state. How do you handle liveness between peers in ENTENCY GNS: plain heartbeats, or something smarter?
Good question — and that distinction is important in GNS too.
We deliberately keep discovery/path availability, authentication and actual CONNECTED state separate. For example, knowing a peer or having a relay path available does not by itself promote that peer to connected; the connection still has to go through path selection and the identity-bearing handshake.
For liveness specifically, I don't want to overclaim where the implementation currently is. We have transport/peer diagnostics and network-state measurements, but I wouldn't describe the current implementation as a mature message-flow-based liveness detector yet.
Your point about a connection being technically alive while carrying no useful traffic is exactly the kind of distinction we need to preserve. A heartbeat can tell us the transport responds; it cannot necessarily tell us the peer or application path is making useful progress.
So the direction is closer to layered health signals than treating a socket/heartbeat as “the peer is healthy.” Message-flow/progress health is something worth making explicit as that part of GNS matures.
Thanks for raising it — this is a genuinely useful edge case.
One approach that might fit what you're seeing is to separate transport liveness from application progress. A ping/pong can tell you the WebSocket is responsive, while a separate progress signal — last received sequence, ACK, processed item, or whatever represents useful advancement in your feed — can tell you whether the connection is actually doing its job.
That gives you a useful distinction between alive, active, and stalled. I’d also avoid treating silence alone as failure if the feed can legitimately be idle; only start a progress deadline when progress is actually expected.
Interestingly, your question made us look at the same distinction in GNS. We already keep path availability, authentication and connected state separate, but explicit transport-liveness vs. useful-progress health is something worth modelling separately too. Thanks — you may have just given us a useful requirement. 🙂
Makes sense, and "layered" is the right word. One thing that bit us: a single silence threshold doesn't work, because "quiet" means different things on different streams. On the exchange websocket we treat 45 s of silence as a dead subscription and rebuild it; on the on-chain log stream we wait 5 minutes, because there silence usually just means nobody traded. So the threshold has to come from the expected traffic of that particular stream, not from the transport. Good luck with GNS!
That's a really useful distinction — the silence budget belongs to the stream semantics, not the transport. Your 45s vs. 5min example makes that very clear.
I'm making a note of this for GNS, because a single global liveness timeout would create exactly the kind of false signal you're describing. Thanks for sharing the real-world numbers — very useful. 🙂
Hello
I working on some distributed systems. we should share ideas sometime.
Okay Larry, if you have any question feel free to ask 🙂
Hello, nice to have you with us!
Hey everyone! Great to be here. Came in on the HacktoberFest train :)
I've been a all-round dev for around 8 years ranging from front-end to back-end dev. Enjoy meeting fellow devs with similar interests. Currently learning to thrive in our AI-powered industry and applying this in my company's EdTech space. Love a good cuppa-coffee and play drums in my spare time
Welcome to DEV Arno!
Great
Hi everyone , I am Kunal, currently an undergrad this is my first time here and I’m here to learn, connect with other developers, contribute to open source, and explore software development opportunities. Always happy to connect and collaborate!
Welcome to DEV Kunal!
Hey! I'm Yudees, a software engineer working in data engineering and AI/ML. I'm really interested in understanding how things work under the hood from data pipelines and distributed systems to LLMs, RAG, and model infrastructure.
I like building things, breaking them, figuring out why they broke, and then going way too deep into the rabbit hole trying to understand what's actually happening behind the scenes.
I'm still learning, experimenting, and occasionally overengineering things that probably didn't need to be overengineered but that's half the fun, right?
Welcome to DEV!
Hey everyone!
I'm a CS student working mostly with SpringBoot and currently picking up Go. I recently started a Freelance agency of my own as a side gig, & right now I’m looking for a community to learn with, get feedback, and fuel my growth.
Excited to be here and check out what everyone is building
Hey everyone! 👋
I’m Kevin from Kenya. I’m a biomedical engineer getting deeper into software engineering, AI, and data systems.
I build projects around healthcare workflows, AI-assisted systems, APIs, and data. I’m especially interested in how we can build software that actually fits the way people work.
I joined DEV to learn from other developers, share what I’m building, and document the journey.
It's great to be here!
Hi everyone! 👋
I'm a developer exploring Cloudflare Workers, AI, and edge computing. Currently building small projects with Workers AI and Bun, and learning as I go.
I'm here to share what I figure out, ask questions, and connect with people building cool things.
Happy to be here! 🚀
Welcome to all our new members. Take a few minutes and check out the TOP 7 posts of the week.
From 3D libraries to local AI music
Top 7 Featured DEV Posts of the Week
hey everyone!
Some comments may only be visible to logged-in visitors. Sign in to view all comments.