90 results for “realtime”
📢 New #updates · 19 Oct #14.1
· lightdash 2.616.0 — Merge queries now generally available
· mirrord 3.276.0 — Added namespace support for DB branches
· Asterisk certified-22.8-cert5
Browse everything at https://selfhost.directory?utm_source=mastodon&utm_medium=social
@eff
is it also about the ad-industry
... RealTimeBidding ?
#Adblocker
#AdFection
#DiscoverTechLTD
with certain kinds of security risks ?
Flavor South Florida returns with dining deals at more than 100 restaurants from Boca Raton to Port St. Lucie https://www.diningandcooking.com/us/56370/ #BreakingNews #BreakingNewsVideo #Florida #FloridaDining #LiveSpeeches #LiveUpdates #LiveVideo #PressConference #RealTimeCoverage #VideoUpdates
A recording from Jeff Pele's recent talk "Real-time Software On #Linux: How Hard Can It Be?" is now available here:
https://www.youtube.com/watch?v=-0D0rFdU6HY
From the abstract[1]: ""Are you sure your software is running? What about in the next few microseconds? Let’s walk through how to answer this question, and write latency-critical software on Linux. You’ll get a headstart from the hardware to userspace, learning about BIOS quirks, kernel settings, paging, tools, application design, and common pitfalls. We’ll squeeze determinism out of PREEMPT_RT Linux, reduce the jitter in our cycle-times and networking from milliseconds to microseconds, and talk about some applications from the industrial automation field.""
[1] https://softwareyoucanlove.ca/talks/real-time-software-on-linux/
#LinuxKernel #Kernel #Realtime #softwareyoucanlove #Preempt_RT
🇹🇼 Meishi Daren Co., Ltd. (85cafe.com) a été victime d'une cyberattaque autour du 21 octobre 2026.
Meishi-KY (Meishi Daren Co., Ltd.) a annoncé que certains de ses systèmes d'information ont été victimes d'une cyberattaque. La société a immédiatement activé son mécanisme de réponse aux incidents de sécurité et fait appel à des experts externes pour l'enquête et la réparation. Selon l'évaluation préliminaire, l'incident n'a pas encore eu d'impact majeur sur les opérations ou les finances de l'entreprise.
👉 https://ww2.money-link.com.tw/RealtimeNews/NewsContent.aspx?SN=2434180002&PU=0010
ElevenLabs wypuściło dwa modele speech-to-speech do agentów głosowych: Mini i Max. Wersja Max ma osiągać 98,8 proc. w Big Bench Audio przy czasie odpowiedzi 0,57 s.
#si #ai #sztucznainteligencja #wiadomości #informacje #technologia
https://aisight.pl/technologia/generatywna-ai/llm/elevenlabs-speech-to-speech-realtime/
Quaest e Datafolha divulgam nova rodada de pesquisas para o segundo turno nesta quarta (21) e quinta-feira (22)
Real-time chat applications are a great way to understand how modern web applications communicate beyond traditional request-response cycles. From customer support tools to team collaboration platforms, messaging systems need to deliver messages quickly, maintain consistent state, and handle multiple users communicating simultaneously.
React provides a flexible foundation for building interactive chat interfaces, while Node.js makes it possible to manage concurrent connections efficiently. When combined with Socket.IO, these technologies enable bidirectional communication between clients and servers without requiring users to refresh their browsers.
In this article, we will build a practical real-time messaging foundation using React concepts, Node.js, Express, and Socket.IO. We will cover the message lifecycle, room-based communication, connection management, basic validation, and important considerations for taking a chat application into production.
Designing a Real-Time Chat Application with React, Node.js, and Socket.IO
A typical chat application consists of three main layers: the React frontend, the Node.js backend, and a communication layer that connects them. React manages the conversation interface, including the message list, text input, connection status, and user interactions. The backend validates incoming messages, determines which users should receive them, and broadcasts events to connected clients.
Socket.IO is useful because it provides event-based communication, automatic reconnection attempts, and room-based messaging. Unlike ordinary HTTP requests, which typically finish after returning a response, a WebSocket connection can remain open so the server and client can exchange events in both directions. Socket.IO can also fall back to HTTP long-polling when WebSocket transport is unavailable, depending on configuration.
The following example implements a runnable Node.js chat server with Express and Socket.IO. It supports joining a named room, broadcasting messages to other participants in that room, tracking connected users, validating message content, and logging each important step. The example uses in-memory state to keep the implementation approachable, so messages and room membership are not persistent across server restarts.
On the React side, create a Socket.IO client and register event listeners inside a useEffect hook. Keep the socket lifecycle synchronized with the component lifecycle, remove listeners during cleanup, and use functional state updates when appending messages. In production, authenticate connections, authorize room membership, apply rate limits, validate payloads on the server, and store messages in a database when conversation history must survive restarts.
const express = require("express");
const http = require("http");
const { Server } = require("socket.io");
const { randomUUID } = require("crypto");
// Step 1: Create the Express application and HTTP server.
const app = express();
const server = http.createServer(app);
// Step 2: Configure Socket.IO for browser clients.
const io = new Server(server, {
cors: {
origin: process.env.CLIENT_ORIGIN || "http://localhost:5173",
methods: ["GET", "POST"]
}
});
// Step 3: Keep lightweight connection metadata in memory.
// Use a database or shared store for a production deployment.
const connectedUsers = new Map();
const MAX_MESSAGE_LENGTH = 1000;
// Step 4: Add a simple health endpoint for monitoring.
app.get("/health", (req, res) => {
res.json({ status: "ok", connectedClients: io.engine.clientsCount });
});
// Step 5: Register handlers whenever a client connects.
io.on("connection", (socket) => {
console.log(`[CONNECT] Client connected: ${socket.id}`);
// Each client must choose a display name before chatting.
socket.on("join-room", ({ username, room } = {}) => {
if (typeof username !== "string" || typeof room !== "string") {
socket.emit("chat-error", { message: "Username and room are required." });
return;
}
const cleanUsername = username.trim().slice(0, 30);
const cleanRoom = room.trim().slice(0, 60);
if (!cleanUsername || !cleanRoom) {
socket.emit("chat-error", { message: "Username and room cannot be empty." });
return;
}
// Leave the previous room when a client switches conversations.
const previous = connectedUsers.get(socket.id);
if (previous) {
socket.leave(previous.room);
socket.to(previous.room).emit("user-left", {
username: previous.username
});
}
// Socket.IO automatically keeps track of room membership.
socket.join(cleanRoom);
connectedUsers.set(socket.id, {
username: cleanUsername,
room: cleanRoom
});
console.log(`[ROOM] ${cleanUsername} joined ${cleanRoom}`);
// Confirm the join only after the server has processed it.
socket.emit("room-joined", {
username: cleanUsername,
room: cleanRoom
});
// Notify other participants without echoing to the joining client.
socket.to(cleanRoom).emit("user-joined", {
username: cleanUsername
});
});
// Step 6: Validate and broadcast a new chat message.
socket.on("send-message", (payload = {}) => {
const user = connectedUsers.get(socket.id);
if (!user) {
socket.emit("chat-error", { message: "Join a room before sending messages." });
return;
}
if (typeof payload.text !== "string") {
socket.emit("chat-error", { message: "Message text must be a string." });
return;
}
const text = payload.text.trim();
if (!text || text.length > MAX_MESSAGE_LENGTH) {
socket.emit("chat-error", {
message: `Messages must contain 1 to ${MAX_MESSAGE_LENGTH} characters.`
});
return;
}
// Build a consistent server-controlled message object.
const message = {
id: randomUUID(),
username: user.username,
room: user.room,
text,
createdAt: new Date().toISOString()
};
console.log(`[MESSAGE] ${user.username} in ${user.room}: ${text}`);
// Broadcast to everyone in the room, including the sender.
// The sender therefore receives the same canonical message object.
io.to(user.room).emit("new-message", message);
});
// Step 7: Clean up user metadata when a connection closes.
socket.on("disconnect", (reason) => {
const user = connectedUsers.get(socket.id);
if (user) {
socket.to(user.room).emit("user-left", {
username: user.username
});
connectedUsers.delete(socket.id);
console.log(`[DISCONNECT] ${user.username}: ${reason}`);
} else {
console.log(`[DISCONNECT] ${socket.id}: ${reason}`);
}
});
});
// Step 8: Start the server and report its address.
const PORT = Number(process.env.PORT) || 3001;
server.listen(PORT, () => {
console.log(`[STARTUP] Chat server listening on port ${PORT}`);
console.log(`[STARTUP] Health endpoint: http://localhost:${PORT}/health`);
});
Conclusion
Building a real-time chat application is an excellent exercise in frontend state management, event-driven backend development, and network communication. React handles the interactive user experience, Node.js processes application events, and Socket.IO keeps connected clients synchronized without relying on continuous polling.
The example provides a foundation for room-based conversations, but a production-ready system requires additional engineering. Add authenticated user identities, room-level authorization, persistent message storage, rate limiting, structured error handling, monitoring, and appropriate deployment configuration before exposing the application to real users.
Start with a single conversation room, verify that messages reach all connected participants, and then introduce features such as typing indicators, unread counts, message history, and private conversations. Which feature would you implement first when extending this chat application?#javascript #react #ai #webdev #software #coding #development #engineering #inclusive #community
Building Real-Time Chat Applications with React and Node.js
Free real-time Certificate Transparency stream, no API key https://certstream.dev/free-certstream-api.html
How can Django power smooth, real-time applications?
From the archives, Ganesh Swami explores WebSockets, Django Channels, state, deployment, scaling, and common async challenges.
Watch: https://youtu.be/BRCx6lSA0fM
Sponsor DjangoCon US 2027: https://2027.djangocon.us/sponsors/information/
#Django #WebSockets
The Wind Up: Two Distinct Flavours of Mido’s Multifort TV Big Date
Readtime: 9 min Every product is carefully selected by our editors and experts. If you buy from a…
#NewsBeep #News #Technology #AU #Australia #mido #Ressence #TheWindUp
https://www.newsbeep.com/au/933499/
VAST has open-sourced EdenLive, a real-time generative renderer that turns simple game footage into detailed video. The 5 billion parameter model runs at over 24 frames per second at 720p on a single RTX 5090 graphics card. The system keeps the game state in upstream code while EdenLive renders the detailed frames.
Volkswagen’s ID. Buzz Reimagines and Electrifies an Icon
Readtime: 4 min Every product is carefully selected by our editors and experts. If you buy from a…
#Germany #DE #Europe #EU #Europa #Volkswagen #nounruly
https://www.europesays.com/germany/112936/
ESPN, Lucasfilm and the NFL team up to bring 'Star Wars Funday Football' real-time animated special to Disney+, Disney Channel and Disney XD. #StarWars #NFL #Disney #animation
https://www.animationmagazine.net/2026/10/star-wars-funday-football-brings-super-bowl-lxi-to-a-galaxy-far-far-away/
Edge AI for Smart Cities: From Insight to Cognitive Action https://content.knowledgehub.wiley.com/edge-ai-for-smart-cities-from-real-time-insights-to-cognitive-urban-systems/?utm_source=IEEE
I am seeing "LLMs = more code = more CI pipelines/jobs= stressing/saturating the infra" in real time and its not pretty #llm #infrastructure
[Blog Archive] Nakivo v11.2.1 with #Proxmox VE 9.1 full support
The new Nakivo v11.2.1 has been released, providing full support for Proxmox VE 9.1 and Real-time Replication in #vSphere 9,
This update expands platform compatibility and boosts operational efficiency for customers, unlocking fresh upgrade and cross-sell opportunities for your business.
What's new in Nakivo v11.2.1 http://rviv.ly/WOqoYd
Lawrence Times: KDOT launches tool to track snowplows on Kansas highways. “An online tool will now allow travelers to track active snowplows on Kansas highways in real time, the Kansas Department of Transportation has announced…. KDOT will also have 12 trucks across the state with cameras that appear on the online map as blue truck icons. People can click those icons to see recent images from […]
https://rbfirehose.com/2026/10/20/lawrence-times-kdot-launches-tool-to-track-snowplows-on-kansas-highways/
Detailed ink study of a pumpkin mecha warrior with heavy mechanical limbs, a rusted hook arm, and a carved jack-o'-lantern chassis. Real-time drawing video available on YouTube: https://youtu.be/DuYitG2Jvqc
#InkDrawing #MechDesign #CharacterArt #Sketchbook #LineArt #TraditionalArt #ASMRDrawing
Firefly, whose AI software connects with existing cameras, radios, and sensors to detect incidents and coordinate real-time responses, raised a $20M Series A (Chris Metinko/Axios)
https://www.axios.com/pro/enterprise-software-deals/2026/10/20/safety-software-ai-firefly
http://www.techmeme.com/261020/p26#a261020p26
A cinco dias do segundo turno, Flávio Bolsonaro e Lula estão em empate técnico, aponta Real Time Big Data
