HiveSuite Development Update: Inbox Media, Web2 & Web3 Authentication

Words
954
Reading
5 min
6d
Listen to this post
~6 min

Image

HiveSuite

HiveSuite โ€” Inbox Image Rendering Fixes

A key focus of this update was improving image rendering inside Inbox notifications and reply detail views, especially for images stored through the 3Speak IPFS infrastructure.

Direct 3Speak IPFS Image Support

  • Added direct handling for 3Speak IPFS images.
  • This bypasses unsupported Hive image proxy routing when the image source is already an IPFS resource.
  • Improved compatibility for media shared through 3Speak within HiveSuite conversations and notifications.

Multi-Gateway IPFS Fallback

To make image loading more reliable:

  • Implemented automatic fallback across multiple public IPFS gateways.
  • If an image fails to load through one gateway, the application can attempt another available gateway.
  • This improves resilience against individual gateway availability or connectivity issues.

Broken Image Placeholder Cleanup

  • Removed empty <figcaption> placeholders from failed image rendering.
  • Prevented stray "Image" text from appearing when an image cannot be loaded.
  • Improved the overall visual quality of Inbox and reply interfaces when media is unavailable.

Inbox & Reply Rendering

  • Fixed 3Speak IPFS images displaying incorrectly or failing to render in Inbox notifications.
  • Fixed the same rendering behavior in reply detail views.
  • Ensured supported IPFS images are displayed consistently across relevant conversation and notification interfaces.

Inbox IPFS Image Rendering

Inbox IPFS Image Rendering

3Speak IPFS Image Fallback

3Speak IPFS Image Fallback


Web2 & Web3 Authentication Integration

A major part of this update was the continued development of a unified authentication experience that supports both traditional Web2 login methods and Hive-native Web3 authentication.

The goal is to make onboarding easier for new users while continuing to provide the authentication methods expected by existing Hive users.


Hive Authentication Package

The shared Hive Authentication Package received a significant authentication UI and functionality upgrade.

Modern Login UI

  • Redesigned the authentication experience into a responsive split layout.
  • Created dedicated sections for Web2 and Web3 authentication.
  • Improved the visual separation between traditional account login and Hive-native authentication methods.
  • Designed the experience to remain clear and accessible across different screen sizes.

Web2 Authentication

Added support for:

  • Google OAuth
  • Email / Password authentication
  • Anti-bot verification

This provides an easier onboarding path for users who may be familiar with Web2 authentication but are new to Hive-native login workflows.

Web3 Authentication

Integrated multiple Hive authentication providers, including:

  • Hive Keychain
  • HiveAuth
  • HiveSigner
  • Private Key
  • PeakLock

The authentication flow now supports a progressive 2-step login experience, helping users move through the authentication process in a more structured way.

Mobile Authentication Experience

  • Added tabbed navigation for switching between Web2 and Web3 authentication on mobile devices.
  • Improved accessibility of the different login methods on smaller screens.
  • Reduced the need for a large desktop-style authentication layout on mobile devices.

Glassmorphism Authentication UI

  • Implemented a glass-style authentication modal.
  • Added click-outside dismissal behavior.
  • Improved the overall presentation of the login interface while maintaining a focused authentication workflow.

Web2 Authentication Feature Flag

Added the enableWeb2Login configuration option to dynamically control Web2 authentication.

This allows applications using the authentication package to:

  • Enable Web2 authentication when required.
  • Disable Web2 authentication when only Hive-native login should be available.
  • Dynamically adjust the authentication modal layout based on the enabled authentication methods.

Web2 Avatar Support

  • Added support for Google profile avatars for Web2 users.
  • Added Gravatar avatar support.
  • Improved the user experience by providing recognizable profile imagery after authentication.

Firebase Improvements

  • Created an isolated Firebase application instance for authentication.
  • Resolved OAuth and referrer-related issues caused by shared Firebase configuration.
  • Improved separation and reliability of the Web2 authentication flow.

Web2 & Web3 Authentication UI

Web2 & Web3 Authentication UI

Mobile Authentication Experience

Mobile Authentication Experience


HiveSuite Application โ€” Authentication Integration

HiveSuite was updated to integrate the new authentication capabilities from the shared Hive Authentication Package.

Local Package Linking

  • Linked hive-authentication through a local dependency.
  • Allows faster development and testing of authentication changes.
  • Enables HiveSuite to work directly with the latest local package implementation.

Feature Flag Integration

Added:

VITE_ENABLE_WEB2_LOGIN

This environment-based feature flag controls whether Web2 authentication is available within HiveSuite.

This provides flexibility for different development, testing, and production configurations without requiring changes to the core authentication implementation.

Backend Integration

  • Connected the Web2 authentication flow with HiveSuite backend login endpoints.
  • Added graceful client-side fallback support when backend authentication is unavailable or cannot be completed.
  • Improved resilience across different authentication environments.

Development Support

  • Added Vite aliases for seamless local package development.
  • Improved hot reloading when working on the local authentication package.
  • Reduced development friction when testing authentication changes across HiveSuite and the shared library.

HiveSuite Authentication Integration

HiveSuite Authentication Integration


Backend โ€” Hive Inbox Web2 Authentication

The Hive Inbox backend was also extended to support the new Web2 authentication flow.

Web2 Login Endpoint

Implemented:

POST /login/web2

The endpoint:

  • Receives Firebase ID tokens.
  • Verifies the Firebase authentication token.
  • Creates an authenticated application session.
  • Issues an application JWT for continued API access.

Session & Permissions

The backend now returns authenticated user information along with application roles.

Supported role information can include permissions such as:

  • Curator
  • Approver

This allows the application to maintain authentication and authorization context after the Web2 login process.

CORS Support

  • Configured cross-origin request handling.
  • Added support for preflight requests.
  • Ensured the authentication endpoint works across both local development and production environments.

Backend Web2 Authentication Flow

Backend Web2 Authentication Flow


๐Ÿš€ 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 AppVote as WitnessSupport via Discord

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

HiveSuite Development Update: Inbox Media, Web2 & Web3 Authenticati... | Ecency