HiveSuite Development Update

HiveSuite — Feature Discovery Toast Improvements

Lifetime-Based Feature Discovery

• Added lifetime-based feature discovery toasts across HiveSuite.
• Each feature can now display its discovery toast a maximum of 3 times.
• This provides users with helpful introductions to features without repeatedly interrupting their normal workflow.
• The lifetime-based approach ensures that once a user has become familiar with a feature, the application gradually stops showing unnecessary discovery messages.

Per-Feature Display Tracking

• Implemented separate localStorage counters for individual features.
• Feature discovery tracking is maintained independently for areas such as:
  • Inbox
  • Chat
  • Maps
  • OpenPods
  • HiveComb
  • Snaps
  • Videos
  • And other application features
• This allows each feature to maintain its own discovery lifecycle instead of relying on a single global counter.

Toast Duration & React StrictMode Fix

• Set the feature discovery toast duration to 3 seconds.
• Added a rate-limiting guard to prevent duplicate toasts from appearing during development or rendering cycles.
• Fixed duplicate feature discovery messages caused by React StrictMode triggering component lifecycle behavior more than once.
• This keeps the discovery experience clean and prevents users from seeing repeated notifications unnecessarily.

Feature Discovery Toasts

---

HiveSuite — HiveSigner Authentication Integration

HiveSigner OAuth Integration

• Added a dedicated HiveSigner callback route and integrated it with the HiveSuite authentication flow.
• Updated the authentication process to correctly handle the OAuth callback and establish the authenticated session.
• Added HiveSigner as an additional authentication pathway alongside the existing login options.

Access Token Integration

• Updated the authentication store to use the HiveSigner access token for authenticated requests.
• The access token is also used when handling authenticated image uploads.
• This keeps authenticated application operations connected to the HiveSigner session after successful authorization.

Visible Login Option

• Added HiveSigner as a visible option within the HiveSuite authentication dialog.
• Users can now clearly identify and select HiveSigner when choosing their preferred Hive authentication method.
• The integration provides another familiar Hive-native authentication route for users who prefer OAuth-based authorization.

Static OAuth Callback Page

• Added a lightweight static hivesigner.html callback page.
• The dedicated callback page provides a reliable location for handling OAuth token responses.
• Keeping this callback lightweight helps simplify the OAuth return flow and reduces unnecessary application initialization during authentication.

HiveSigner Application Configuration

• Updated the HiveSigner application identifier to thehivemobileapp.
• This configuration aligns the HiveSuite OAuth flow with the required HiveSigner application authorization setup.
• Verified the authorization flow after updating the application identifier.

HiveSigner Login Integration

HiveSigner Authentication Flow

---

HiveSuite — Feed Publisher Filter Improvements

Improved Publisher Detection

• Fixed publisher filtering for both parsed and raw json_metadata formats.
• Improved metadata handling so publisher information can be detected consistently regardless of how the metadata is represented.
• This makes publisher-based feed filtering more reliable across different Hive applications and publishing formats.

Base Application Name Extraction

• Improved application detection by extracting the base application name from publisher strings.
• For example, a value such as peakd/2026.6.14 is now correctly interpreted as the base application PeakD.
• This prevents version information from interfering with publisher matching.

Reliable Publisher Matching

• Added reliable matching for multiple Hive publishing platforms, including:
  • PeakD
  • Ecency
  • HiveSuite
  • ThreeSpeak
  • InLeo
  • Custom publishers
• The improved matching logic makes publisher filters more predictable when browsing and organizing Hive content.

Improved Feed Experience

• Publisher filtering can now work consistently across different metadata structures.
• Users can more reliably identify and filter content based on the application that originally published it.
• This improves the usefulness of feed discovery and filtering while supporting a wider range of Hive publishing clients.

Feed Publisher Filters

Publisher Detection & Matching

---

🚀 Powering the Hive Ecosystem

• Continuously improving HiveReactKit with reusable components that make Hive applications richer and more responsive.
• Building shared infrastructure for media rendering, translations, and smoother community navigation across the Hive ecosystem.
• Contributing open-source enhancements that improve usability, consistency, and long-term maintainability for Hive frontends using HiveReactKit.

---

Final Note

This post has been refined with the help of AI to improve readability and structure.
The development updates and optimized version are both available for reference.

---

🔗 More Links

HiveSuite App	Vote as Witness	Support via Discord

Use HiveSuite. Invite your friends. Stay active. Earn rewards.

_{Posted via HiveSuite}