B
Hacker NewsDurable queues, streams, pub/sub, and a cron scheduler – inside your SQLite file
#HackerNews #DurableQueues #SQLite #Streams #PubSub #CronScheduler
GoffiNew progress note available (after 3 years during which I posted here on ActivityPub instead of on the blog):
https://www.goffi.org/id/libervia-progress-note-2026-w16-ooph
I'm talking about current work on installation/configuration simplification and the new forge, focus on web frontend and redesign and work done with current metadata reduction and serverless XMPP (Tor, contacts e2ee, new pubsub implementation).
#Libervia #progress #XMPP #NLnet #NCI0 #Tor #pubsub #decentralized #forge #metadata #serverless
I've just pushed a new pubsub implementation (basically a reimplementation of SàT/Libervia Pubsub on top of Libervia Backend).
May not sound exciting like that, but it's a major thing for many reasons, I hope that I can find time to blog about that tomorrow.
Also it implements XEP-0496 (Pubsub Node Relationships) and XEP-0499 (Pubsub Extended Discovery) which means node hierarchy, useful for things like forums.
This is context of https://nlnet.nl/project/ServerlessXMPP/
Saad khanKafka: Queue & Pub-Sub Together 📨
Queue (1-to-1):
1 consumer group, consumers = partitions
Each message → 1 consumer only
Pub-Sub (1-to-many):
Multiple consumer groups
Each group → all messages
Traditional systems need separate tools.
Kafka does both natively!
lmorchard's linksServer-Sent Events Beat WebSockets for 95% of Real-Time Apps (Here's Why) - DEV Community
"Everyone defaults to WebSockets for real-time features. Most shouldn't.
The reality: 95% of "real-time" applications only need server → client updates. Chat notifications. Live dashboards. Stock tickers. Log streams. AI responses.
WebSockets give you bidirectional communication. But bidirectional comes with a tax: complexity, resource overhead, scaling challenges, debugging nightmares.
Server-Sent Events (SSE) do one thing: stream data from server to client. They do it brilliantly. And for..."
https://dev.to/polliog/server-sent-events-beat-websockets-for-95-of-real-time-apps-heres-why-a4l?context=digest
#events #http #pubsub #sse #webdev
"Everyone defaults to WebSockets for real-time features. Most shouldn't.
The reality: 95% of "real-time" applications only need server → client updates. Chat notifications. Live dashboards. Stock tickers. Log streams. AI responses.
WebSockets give you bidirectional communication. But bidirectional comes with a tax: complexity, resource overhead, scaling challenges, debugging nightmares.
Server-Sent Events (SSE) do one thing: stream data from server to client. They do it brilliantly. And for..."
https://dev.to/polliog/server-sent-events-beat-websockets-for-95-of-real-time-apps-heres-why-a4l?context=digest
#events #http #pubsub #sse #webdev
Broadcast Channel API - Web APIs | MDN
"The Broadcast Channel API allows basic communication between browsing contexts (that is, windows, tabs, frames, or iframes) and workers on the same origin.
By creating a BroadcastChannel object, you can receive any messages that are posted to it. You don't have to maintain a reference to the frames or workers you wish to communicate with: they can "subscribe" to a particular channel by constructing their own BroadcastChannel with the same name, and have bi-directional communication between a..."
https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API
#pubsub #webdev
"The Broadcast Channel API allows basic communication between browsing contexts (that is, windows, tabs, frames, or iframes) and workers on the same origin.
By creating a BroadcastChannel object, you can receive any messages that are posted to it. You don't have to maintain a reference to the frames or workers you wish to communicate with: they can "subscribe" to a particular channel by constructing their own BroadcastChannel with the same name, and have bi-directional communication between a..."
https://developer.mozilla.org/en-US/docs/Web/API/Broadcast_Channel_API
#pubsub #webdev
Qiita - 人気の記事Broadwayを嗜む③：ProducerのレートリミッターとbatcherのタイムアウトによるQoS
https://qiita.com/piacerex/items/0f01fa84ad2c30e4b6f5?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Broadwayを嗜む②：データ順を維持しながら並行・並列を高めるコントロール
https://qiita.com/piacerex/items/7fad1e57b954b41a274f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
hallunke23 🇺🇦
Da würde ich gerne mal die Frage in die Runde stellen:
Hat sich schon mal jemand Gedanken gemacht, wie man ein soziales Netzwerk gestalten könnte, dass:
• Kommentare erlaubt, die dem VErfasser gehören,
• das Beschreiben fremder Social Feeds erlaubt und
• mit #ActivityPub UND #PubSub interoperabel ist?
Ich habe die Befürchtung, dass das auf eine Quadratur des Kreises hinausläuft.
(6/6)