Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mas.to is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hello! mas.to is a fast, up-to-date and fun Mastodon server.

Administered by:

Server stats:

12K
active users

mas.to: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#queue

1 post1 participant0 posts today
Public
Andreas Gütter
So ganz allmählich wird es wohl Zeit, mir eine kleine Liste zu machen, zu welchen Zeiten ich in meiner Pension was mache. Erster Eintrag: Gehe nie samstags zum Recyclinghof! Da steht gerade die ganze Stadt, um ihren Schrott loszuwerden. Und ich hatte nur ein paar große Kartons, die nicht in die heimische Tonne passten. Schlange stehen, Wartezeit, tausend Leute... Das mache ich dann also später an einem anderen Tag, zu einer anderen Zeit.
#Zeiteinteilung #Zeitleiste #queue
GIF
#queue
Public
jexner

Phew! I need to figure out a way to get data from a Raspberry Pi into a database on a server over an unreliable network.
The data is not a stream, but there is a new data point being generated every 5 minutes.
I'm thinking I need something like a local queue on the Pi, and once Internet is there, the elements from the queue need to be transferred, one by one, then added into the database.
Rabbit hole, here I come!
#BuildInPublic #Internet #database #queue

Public
Fedify: an ActivityPub server framework

Got an interesting question today about #Fedify's outgoing #queue design!

Some users noticed we create separate queue messages for each recipient inbox rather than queuing a single message and handling the splitting later. There's a good reason for this approach.

In the #fediverse, server response times vary dramatically—some respond quickly, others slowly, and some might be temporarily down. If we processed deliveries in a single task, the entire batch would be held up by the slowest server in the group.

By creating individual queue items for each recipient:

  • Fast servers get messages delivered promptly
  • Slow servers don't delay delivery to others
  • Failed deliveries can be retried independently
  • Your UI remains responsive while deliveries happen in the background

It's a classic trade-off: we generate more queue messages, but gain better resilience and user experience in return.

This is particularly important in federated networks where server behavior is unpredictable and outside our control. We'd rather optimize for making sure your posts reach their destinations as quickly as possible!

What other aspects of Fedify's design would you like to hear about? Let us know!

A flowchart comparing two approaches to message queue design. The top half shows “Fedify's Current Approach” where a single sendActivity call creates separate messages for each recipient, which are individually queued and processed independently. This results in fast delivery to working recipients while slow servers only affect their own delivery. The bottom half shows an “Alternative Approach” where sendActivity creates a single message with multiple recipients, queued as one item, and processed sequentially. This results in all recipients waiting for each delivery to complete, with slow servers blocking everyone in the queue.
#ActivityPub#fedidev
Public
Daniel H

@eikedrescher Hallo Eike,
zufällig über Deine Podcast App Queue gestolpert.

Hab eine lange Podcasthistorie unter Apple:
- begonnen mit Apple Podcasts & iPod nano
- iOS und Overcast
- Pocketcasts
- dann lange Castro
- seit einem Jahr wieder Overcast

Experimentiere gerne mit Podcast Apps und Deine neue App sieht schon einmal sehr schick und minimal aus. Schon einmal ein guter Start.

#queue#podcast
ExploreLive feeds
About