OnCue Liveblogging

Regjistër ndryshimesh

1.2.0

• A dropped connection now delays a post instead of losing it. Every update
  written in the live console goes into an outbox and is sent from there, so a
  post that can’t get through sits in your own feed marked “waiting for a
  connection,” with the text intact, and goes out by itself when the network
  returns. The queue is kept in the browser, so it survives a reload, a closed
  laptop, or a crashed tab. A post the site itself refused (coverage ended, the
  session expired) stops and waits for you, with Try now and Discard on it.
• Late posts keep their place in the timeline. A post held up by a connectivity
  gap publishes at the time it was written and reads in order with everything
  around it, rather than jumping to the top. That covers the console’s outbox,
  the wait while a photo uploads, and messages from Slack, Telegram, and
  Messenger, which are now dated from the platform’s own send time. A stamp in
  the future, or more than a day old, is ignored and the post takes the time it
  arrived. Twilio SMS carries no send time, so a delayed text still dates from
  when it reached the site.
• A retry can no longer post twice. Each console post carries the id it was
  written under, and the site returns the existing update for an id it has
  already seen — the same protection chat messages get from their platform’s
  message id.
• A post belongs to whoever wrote it. Editing, deleting, pinning, starring, and
  pushing a post to Bluesky or Threads are now permitted only to that post’s
  author, or to an Editor or Administrator. Creating the event, or being
  assigned to it, no longer carries authority over another contributor’s words.
  This is a change for existing sites: an Author who could previously edit
  anything in an event they created can now edit only their own posts. Refusals
  say which rule applied instead of a flat “you cannot edit this entry,” and the
  Slack emoji shortcut for sharing a post follows the same rule as the button.
• Photos stay true to the file. A photo is turned the right way up on the way in
  (Slack stripped the orientation tag, Telegram and the REST route did not), and
  is scaled to a sensible size before WordPress sees it. If something on the
  site’s upload path reshapes the pixels — an image optimization plugin is the
  usual cause — OnCue puts the original back, and says so in the log when it
  can’t.
• Photos in the reader are never drawn out of shape, including against themes
  whose own rules would stretch them, and the enlarged view now shows the photo
  at its true proportions. A line under each photo says it can be tapped to
  enlarge; it is left off images too small to be worth enlarging, and emoji are
  no longer treated as photos.

1.1.0

• Connections are checked live when you save them. The Connections screen says
  what OnCue reached (the Slack workspace, the Bluesky account, the AI model,
  and so on) or gives the service’s own reason for refusing, and a connection
  whose keys stop working reads “Needs attention” instead of “Connected.”
  Microsoft Teams and Google Chat webhooks are confirmed with a one-line test
  message.
• Every connect, sign-in, and save now confirms itself inside the card or
  prompt you used, instead of in a notice at the top of the page. Steps that
  finish outside WordPress, such as inviting the bot to a private Slack channel
  or tapping Start in the Telegram app, update the page on their own.
• The approval gate is simpler and easier to follow. When it is on, posts from
  anyone other than an Editor, an Administrator, or the event’s creator are
  held, whatever channel they came from; the per-source setting is gone, so an
  event that held only some sources now holds all of them. Held posts sit in
  the live console feed at the time they were written, marked “Awaiting
  approval,” with Approve and Reject on the post. Approved posts keep their
  original time, and open reader pages still receive them. A rejected post
  stays visible to its author until they dismiss it. In Slack, the hourglass
  on a held message changes to a check mark or a cross once it is decided.
• The prefix that keeps a chat message off the liveblog is now %%. Slack,
  Teams, and Telegram open a command menu on a leading slash, which made the
  old // awkward to type.
• The More Coverage tag picker is searchable and reaches every tag on the site.
  The old list stopped at 200 tags, and re-saving an event could drop a saved
  tag past that point. It warns as soon as a broad tag is picked, and says so
  when a saved tag has been deleted.
• A link typed on the first line of a console post now becomes a preview card.
• Fixed connecting a Slack account from event setup or the live console, which
  could fail with “the link you followed has expired.” Returning from Slack
  while signed out of WordPress now asks you to sign in and completes the link.

1.0.9

• Compatible with WordPress 7.1. The liveblog block, the live console, and the
  event setup screens were reviewed against 7.1’s always-iframed editor, its
  persistent admin toolbar, and its refreshed editor components.
• Pictures added from the live console stay a sensible size when they are
  inserted moments after uploading. WordPress 7.1 prepares image sizes in the
  browser, and a picture chosen before that finished could previously be placed
  at its full original resolution.

1.0.8

• Share cards are generated only for posts that carry an image. A text-only post
  is no longer rendered into a picture and saved to the Media Library. Its social
  preview uses the event’s fallback share image instead, or no preview image at
  all when the event has none set.
• Generated share cards now leave with the post they belong to. Retracting a
  post, deleting an event, or uninstalling the plugin clears its cards, and cards
  created by earlier versions are swept out once on update. Images posted to a
  liveblog, from WordPress or from a connected chat platform, are never touched.

1.0.7

• Security hardening throughout, in response to the WordPress.org review.
  Request data is sanitized at the point it is read, and every dynamic value is
  escaped on the line that prints it.
• Telegram sign-in payloads are reduced to the fields Telegram actually sends,
  each cleaned for its own field type, and the verified account ID must be a
  positive integer before it is stored. A payload that fails either check is
  rejected rather than trusted.
• Analytics no longer reads a server value without sanitizing it first, and the
  client IP is validated as a real IP address before it is hashed. It is still
  never stored.
• Event setup sanitizes the authors, tags, colors, module toggles, and
  per-module settings it receives, instead of relying on a later pass.
• Credentials for Slack, Telegram, Google Analytics, and the AI providers are
  sanitized as they are read from the settings forms.

1.0.0

• First stable release, and OnCue’s first release on WordPress.org.
• Core liveblog: events, the OnCue Liveblog block and [oncue] shortcode, and
  the live console for posting, editing, pinning, and moderating updates.
• Opt-in field posting from Slack and Telegram, with an optional per-event
  approval queue for contributors’ posts.
• Opt-in modules: More Coverage, reader share cards, reader reactions, polls,
  per-event appearance, link preview cards, and outbound relay to Slack,
  Telegram, Bluesky, Twilio SMS, Microsoft Teams, Google Chat, and Signal.
• Built-in cookieless per-event analytics that require no third-party account.
• Bring-your-own-key “Key highlights” summaries with grounded, cited output,
  supporting Anthropic Claude, OpenAI, Google Gemini, and OpenAI-compatible or
  self-hosted endpoints.
• Channel credentials encrypted at rest with libsodium, using a key held
  outside the database.
• Fully translatable, with a bundled POT file.

Releases below predate the WordPress.org listing and were distributed directly.

0.1.34

• Reader reactions: an opt-in, per-event thumbs-up on individual updates, with
  no sign-in required and counts that refresh live.
• Bluesky threads can now carry a per-event official hashtag, set in Event Setup.

0.1.33

• New Appearance tab: per-event accent, card background, border, and muted-text
  colors with a readability check, plus contained or full-width layout.
• Links pasted in the console, or shared from Slack or Telegram, now render as
  preview cards with headline, description, image, and source.
• Expanded Bluesky support.

0.1.25

• Built-in per-event analytics that need no Google account: reader numbers,
  unique readers, shares, interactions, sources, devices, countries, and a live
  “reading right now” count.
• Collection is cookieless and stores no personal data. Visitor counts use a
  daily-rotating fingerprint; IP addresses derive an approximate country and are
  never stored. All data stays in your own database.

0.1.24

• First public release.