hive-139531 community on Hive

HiveSuite Development Update: Scheduled Posts Management & Blockchain Data Profile

sagarkothari88 — Sat, 03 Oct 2026 06:00:30 GMT

HiveSuite Development Update: Scheduled Posts Management & Blockchain Data Profile

HiveSuite — Scheduled Posts Management

Edit Modal Enhancement

Continued improving the scheduled publishing workflow in HiveSuite by bringing schedule configuration directly into the existing edit experience.

Added a Publish At datetime picker to the scheduled post edit modal.
Added a localized date and time preview for the selected publishing schedule.
Added minimum scheduling validation to prevent invalid scheduling times.
Configured the minimum scheduling window as:
- 5 minutes for development environments.
- 15 minutes for production environments.
Improved the editing experience by keeping schedule configuration directly inside the Edit Modal.

Publish At Date & Time

Unified Edit Flow

Simplified the scheduled post editing workflow by combining content metadata and scheduling updates into a single action.

Merged metadata changes and schedule updates into one Save action.
Removed the need for users to perform separate actions when modifying scheduled content.
Improved the overall editing flow for scheduled posts.
Reduced unnecessary UI steps while preserving existing scheduling functionality.

This provides a more straightforward workflow for users managing their scheduled Hive content.

Unified Scheduled Post Editing

Automatic Refresh & Sorting

Improved how the scheduled posts list responds after an edit.

Updated scheduled posts immediately after saving changes.
Automatically refreshed the updated post information.
Automatically re-sorted the scheduled posts list after editing.
Ensured the latest publishing schedule is reflected without requiring a manual page refresh.

This makes schedule management feel more responsive and keeps the list synchronized with the latest changes.

Scheduled Posts Refresh

UI Simplification

Cleaned up the scheduling interface and removed redundant controls.

Removed the separate Reschedule button.
Consolidated scheduling changes into the existing edit workflow.
Removed unused scheduling components.
Simplified the overall scheduled-post management interface.
Reduced duplicate actions and unnecessary UI complexity.

The result is a cleaner workflow where users can manage both post information and publishing time from the same editing experience.

Simplified Scheduling UI

HiveReactKit — Blockchain Data Profile Tab

New Blockchain Data Tab

Expanded the shared HiveReactKit profile functionality by adding a dedicated Blockchain Data tab for deeper account and blockchain-related information.

Added a dedicated Blockchain Data profile tab.
Integrated blockchain information directly into the user profile experience.
Designed the tab to organize account-level and blockchain-specific information in a readable format.
Built the functionality as reusable HiveReactKit components for integration into Hive applications.

Blockchain Data Profile Tab

Witness Data Integration

Added dynamic witness information retrieval using the currently selected Hive RPC node.

Fetches witness details dynamically from the selected Hive RPC endpoint.
Displays relevant witness information when the account is a registered witness.
Added witness properties and related blockchain information.
Displays exchange rate information.
Displays the last blockchain data update time.
Added a friendly fallback state when the current user is not a registered witness.

This makes the profile's blockchain section useful for both regular Hive users and accounts participating in Hive witness infrastructure.

Witness & Blockchain Information

Parallel Data Fetching

Improved blockchain profile loading performance by retrieving independent data simultaneously.

Loads account details and blockchain properties in parallel.
Reduces unnecessary sequential API waiting time.
Allows multiple pieces of profile information to become available faster.
Improves the overall rendering experience of the Blockchain Data tab.

This approach makes better use of the selected Hive RPC endpoint while keeping the profile experience responsive.

Read the full post

Building the Future of Web3 Freelancing: Escrow Protection, Anti-Abuse Gating, and Mobile Network Hardening on HivePostify

hivepostify — Fri, 02 Oct 2026 19:05:09 GMT

Over the past few weeks, HivePostify reached a point that had been in progress for a while. What started as a decentralized blogging and publishing front-end on the Hive blockchain is now growing into a Web3 freelancing and services marketplace.

More creators and freelancers are joining. Thousands of pages are already indexed across major search engines. That growth shifted the focus from publishing alone to the real problems of online hiring: security, spam, transparent escrow, and mobile performance on networks that do not behave like a clean office broadband line.

This update covers the decisions behind the latest release, the problems that showed up in production, and the code that shipped. It is not a product pitch. It is what changed.

Decoupling Services into Two Distinct Engines: Gigs vs Custom Jobs

One of the first design questions on a freelancing platform is how work should be offered. Fiverr-style products are packaged services. Upwork-style products are client requests. Those are not the same search.

The first marketplace prototype put both into one tabbed view. It looked tidy in the mock. It failed in real use. People looking for a fixed package and people looking for a custom bid were fighting the same screen.

Service Gigs (/marketplace):

Freelancer-driven. The freelancer sets fixed packages (Basic, Standard, Premium), states delivery time, and the buyer purchases a ready offer.

Job Board (/jobs):

Client-driven. The client describes a custom problem, sets a target budget in USD / AHPT, and freelancers send tailored proposals.

Putting them in one interface created clutter. Filters meant different things depending on which tab was open. They are now two discovery engines, each with its own route, search, and flow. Both still sit on the same wallet and the same escrow ledger. The split is in the product, not in the money path.

                 +-----------------------------------+
                 |         HivePostify Engine        |
                 +-----------------------------------+
                                   |
         +-------------------------+-------------------------+
         |                                                   |
         v                                                   v
   +-----------------------+                           +-------------------+
   |  Gigs (/marketplace)  |                           |   Jobs (/jobs)    |
   |  - Fixed tier pricing |                           |  - Custom RFPs    |
   |  - Direct purchase    |                           |  - Bids & Escrow  |
   +-----------------------+                           +-------------------+
             |                                                   |
             +-------------------------+-------------------------+
                                       v
                        +-----------------------------+
                        |   Postify Wallet & Escrow   |
                        |  Dynamic Settings & Ledger  |
                        +-----------------------------+

The practical result is simpler navigation. A buyer who wants a logo package does not land in a bid board. A client who wants a custom build does not have to pretend it is a gig.

Anti-Abuse & Spam Protection: Account Verification Middleware

Open job boards attract the usual noise: scrapers, unverified accounts posting fake offers, and low-effort proposal spam. The job board should not be a place where confirmed users have to filter garbage before they can work.

The gate sits at the API route. A project cannot be published, and a proposal cannot be submitted, unless the account is confirmed. That check runs against the SignupTicket ledger before the request goes any further:

// Middleware: Verify confirmed standing before allowing jobs/proposals
async function checkUserPermission(username) {
  if (!username) return { allowed: false, error: 'Authentication required' };

  const ticket = await SignupTicket.findOne({
    $or: [
      { hiveUsername: username.toLowerCase().trim() },
      { freshEmailUsername: username.toLowerCase().trim() }
    ]
  });

  if (!ticket) {
    return { allowed: false, error: 'Account verification record not found.' };
  }

  // Block pending or unconfirmed trial accounts from posting or bidding
  if (ticket.status !== 'confirmed') {
    return {
      allowed: false,
      error: 'Your account is currently pending verification. Only confirmed accounts can post projects or submit proposals.'
    };
  }

  return { allowed: true, ticket };
}

On the frontend, an Axios interceptor catches the 403 and shows a plain notice that points the user to verification. A dead button was not the goal. Trial or pending accounts posting jobs was not the goal either. Confirmed standing is the minimum bar for publishing or bidding.

Read the full post

HiveSuite Development Update: RPC Reliability, Mobile Navigation & Core Architecture Improvements

sagarkothari88 — Fri, 02 Oct 2026 06:00:27 GMT

HiveSuite

Core Application Architecture

Application Shell – Main React application and dashboard responsible for bringing the overall HiveSuite experience together.
Routing & Navigation – Manages application pages, layouts, routes, and navigation between different Hive features.
Global State – Uses Zustand to manage application-wide state and keep different features synchronized.
Wallet Integration – Supports Hive wallet and authentication functionality through Aioha.
Feed Management – Fetches and manages Blogs, Snaps, Waves, and other Hive feed experiences.
Feature Integration – Connects and orchestrates the different application features through a shared application architecture.

This structure allows HiveSuite to bring multiple Hive workflows together while maintaining a common interface and shared state across the application.

HiveSuite Application Common Detail Page

HiveReactKit — Shared Component Library

HiveReactKit provides the reusable component and service foundation used by HiveSuite and other projects that need Hive-specific functionality.

Core Library Architecture

Reusable UI Components – Shared React components designed specifically for Hive applications and workflows.
Profile & Post Components – Provides user profiles, post details, comments, feeds, and related content components.
Hive Service Layer – Provides direct Hive RPC integration for retrieving blockchain and application data.
Media & Interactions – Supports voting, replies, media embeds, navigation, and other common Hive interactions.
Library Distribution – Built and distributed as reusable ESM/CJS packages for integration across multiple projects.

Maintaining this functionality within a shared library allows improvements to be developed centrally and then consumed by HiveSuite and other applications.

HiveReactKit Components

HiveSuite — Default RPC Upgrade

More Reliable Hive API Startup

Improved the default Hive RPC configuration in HiveSuite to provide a more reliable starting point for blockchain API requests.

Changed the default Hive RPC node to api.deathwing.me.
Prioritized the new RPC endpoint during application startup.
Reduced dependency on the previous default node during initial application loading.
Addressed startup issues related to:
- CORS restrictions
- HTTP 429 rate-limit responses
Improved the reliability of initial Hive API requests.
Kept the RPC configuration compatible with the existing application architecture.

Using a more reliable default RPC endpoint helps HiveSuite establish its Hive data connection more consistently when users open the application.

HiveSuite — TypeScript & Callback Fixes

Blog Feed TypeScript Fix

Resolved a metadata type-narrowing issue in BlogFeedView.

Fixed metadata type narrowing in BlogFeedView.
Eliminated the related TypeScript compilation errors.
Improved type compatibility within the feed rendering flow.
Preserved the existing feed functionality while correcting the type definitions.

Snaps Callback Compatibility

Updated the callback signature used by SnapsUnifiedPage.

Made contextPosts optional in the callback signature.
Matched the callback with the expected component API.
Improved compatibility between SnapsUnifiedPage and its consuming components.
Prevented callback signature mismatches during compilation.

These changes improve the stability of the application codebase while keeping the existing functionality unchanged.

TypeScript & Callback Improvements - Recommendation Posts

HiveReactKit — Default RPC Update

Shared Hive API Reliability

The same RPC reliability improvement was applied to the shared HiveReactKit library.

Switched the package's default Hive endpoint to api.deathwing.me.
Improved the default endpoint used for Hive API requests.
Ensured applications consuming HiveReactKit receive the updated default configuration.
Kept the RPC configuration centralized within the shared library.

Updating both HiveSuite and HiveReactKit ensures the application and its underlying shared service layer use the same reliable default Hive endpoint.

HiveReactKit — Mobile Scroll & FAB Improvements

Floating Action Menu Touch Fix

Improved the mobile floating action menu experience by fixing an overlay issue affecting touch and scroll gestures.

Read the full post

🐗⚡ Building BOAR | How I Fit an Offline AI Research Engine Into a Phone

vaipraonde — Thu, 01 Oct 2026 17:05:45 GMT

"It all started with a suspicious link sent by a hacker named Vlad."

Building BOAR: How We Fit an Offline AI Research Engine Into a Phone

If you've been following me you know I love testing new things, pushing limits, and bringing dev energy into real world projects.

Whether its building terminal tools, testing Web3 in daily life or coding late into the night, the goal is sovereignty, autonomy, and building tools that works.

It all started Last Week, @xvlad sent me a DM with just a link...
You know me, I don't click on links, but hey, its from Vlad and poidh.xyz, I know that website...

So, looks like Kenny posted a bounty for building a true offline AI research app for Android: one that can answer complex research questions with zero internet signal, running inside strict limits of 12 GB of RAM and 50 GB of storage.

Mission accepted!!! Lets build!

It sounded as simple as "just put llama.cpp inside a mobile app"... It wasn't. The phone fought back at every single step.

Here is the story of how we built BOAR, the bloopers, the thermal throttling, and what happens when you run local LLMs in airplane mode.

1. From AOAIR to BOAR

The project actually started as AOAIR (Android Offline AI Researcher). But during testing, I kept looking at the name and reading it as "OAIR". Then my brain made the jump: BOAR.

Suddenly I could picture a wild boar out in the middle of nowhere: rugged, curious, independent, moving through the wild without needing anyone's Wi-Fi.

The idea stuck! Before the code was even finished, the mascot already existed in my head.

And that's how AOAIR became BOAR.

2. One Brain at a Time & The 4.5-Second Tax

Rule #1 of mobile hardware: a phone can't keep multiple AI models warm in memory at the same time. BOAR keeps exactly one model loaded. Switching models means unloading, loading from disk, and only then generating.

So instead of routing questions between models, BOAR routes by depth. The model you picked always answers. A confident lookup can be answered instantly from a source sentence with no LLM at all, a normal question goes to your model over a compact set of sources, and a "go deeper" answer uses a larger model only when one is installed and fits in memory.

We learned that the hard way: on the phone, every model switch cost 4.5 to 8.9 seconds. On a phone, which model is already warm in RAM matters just as much as which model is the smartest.

3. Why black holes bend spacetime?

One of our very first search tests was simple enough: "Why do black holes bend spacetime?"

Our local RAG engine located the relevant Wikipedia chunks instantly and BOAR delivered a crisp, accurate response. SUCCESS!

...But there is always a "but", isn't there? 🙃

When we pushed the engine with broader, multi-layered scientific queries like "How Do Vaccines Work?", the initial search setup hit a wall:

Vaccine ✅ (Found exact word match)
Immune system ✅ (Found exact word match)
CRISPR & Gene Therapy ⛔
Tim Peto / Key Researchers ⛔
Complementarity-determining regions ⛔

The early search engine was treating the prompt as one rigid phrase rather than understanding the underlying biological web of concepts. It either matched exact words or left crucial context out entirely.

The Fix:

To solve this, I completely rebuilt our RAG pipeline into a hybrid engine combining ultra-fast keyword relevance (SQLite FTS5) with vector semantic search. We also introduced smart context packing to ensure no single document crowded out the LLM's context window.

However, running this on everyday mobile hardware meant facing a brutal reality:

every vector similarity check comes with a heavy CPU and battery cost.

Balancing deep retrieval precision against battery health and sub-5-second offline response times is a constant tightrope walk when you’re building sovereign AI off-grid.

4. First full benchmark run

Instead of relying on "it feels fast," we built an automated on-device benchmark: 17 research questions tested across models.

Read the full post

HiveSuite Development Update: Root Post Editing & Custom Snaps Following Fix

sagarkothari88 — Thu, 01 Oct 2026 06:00:27 GMT

HiveSuite

HiveReactKit — Root Post Editing Fix

Reliable `parent_permlink` Handling

Continued improving the shared HiveReactKit editing workflow by strengthening how root-level Hive posts are handled when users edit existing content.

Added robust fallback logic to always provide a valid parent_permlink when editing root posts.
Updated edit actions across:
- UserDetailProfile
- HiveDetailPost
- SnapsFeedCard
When parent_permlink is missing, the edit flow now uses the post's primary category as the fallback value.
Ensured consistent metadata is passed into the edit modal from all supported post entry points.
Improved reliability when editing posts originating from different feed and profile interfaces.
Reduced the possibility of invalid or incomplete metadata being passed to Hive transaction workflows.

HiveSuite — Root Post Editing

Improved Edit Post Modal

Updated the HiveSuite EditPostModal to reliably resolve the correct parent tag when editing top-level blog posts.

Updated EditPostModal to automatically resolve the appropriate parent tag using:
- Post category
- Existing post tags
- A safe default fallback
Added handling for cases where parent_permlink is empty or unavailable.
Fixed Hive Keychain validation errors that occurred when editing top-level blog posts.
Improved compatibility with posts loaded from different Hive feed sources.
Ensured consistent metadata is passed through the complete editing workflow.
Verified that root posts can be edited without requiring a manually supplied parent permlink.
Confirmed the application builds successfully with zero compilation errors.

This improvement makes the editing experience more reliable across HiveSuite, particularly when the same post can be accessed through different feeds, profile pages, or post detail views.

Root Post Edit Metadata

Edit Post Success

HiveSuite — Custom Snaps Following Fix

Following Feed Improvements

Improved the Following experience in Custom Snaps by ensuring the user's actual following relationships are loaded before the feed is rendered.

Automatically loads the logged-in user's following list before displaying the Following feed.
Prevents the feed from being rendered before the required following data is available.
Ensures the Following tab is populated using the user's current follow relationships.
Improved the initial loading flow for authenticated users.

Following Feed

Accurate Follow Status

Fixed the follow status displayed on recommendation cards within Custom Snaps.

Recommendation cards now correctly display:
- Follow when the user is not following the account.
- Following when the user already follows the account.
Uses the user's actual Hive following relationships to determine the displayed state.
Prevents incorrect Follow/Following states caused by incomplete or stale following data.
Keeps recommendation interactions synchronized with the user's current social graph.

Follow Status

Authentication Sync

Improved following data synchronization when the authenticated Hive account changes.

Updated feed loading to refresh following data whenever the logged-in user changes.
Ensures the Following feed uses the correct account's relationships.
Prevents previous user's following information from being reused after an account switch.
Improves consistency between authentication state and feed content.

Improved Feed Filtering

The Following tab now applies the loaded following relationships correctly when filtering Custom Snaps content.

Ensures the Following feed displays Snaps only from users the current account follows.
Improved filtering consistency across feed refreshes.
Keeps the feed synchronized with the latest following data.
Prevents unrelated users' Snaps from appearing in the Following view.

Custom Snaps Following Filter

🚀 Powering the Hive Ecosystem

Read the full post

HivePulse.app Community Feedback Container — Week 3

hivepulse.app — Wed, 30 Sep 2026 20:30:57 GMT

Welcome to the Week 3 of HivePulse.app community feedback!

This is where we gather any feedback coming from the community that uses the app. As I've built this app for Hive users (myself included), I'd rather improve it based on real usage than simply assume I know what everyone wants.

If you use HivePulse, tell me:

Did you find a bug or facing an issue?
Do you encounter specific usability problems?
Do you have an idea or some additional stats that you want to see?

Or simply tell me what you like or dislike about it. Not all feedback has to be about fixing or improving something. If there is a feature you particularly like, let me know. It helps me understand what is actually useful and in what direction to switch my focus to.

That's all folks! Much appreciated! 🤗

HiveSuite Development Update: Global Post Filtering & Hide Game Posts

sagarkothari88 — Wed, 30 Sep 2026 06:00:24 GMT

HiveSuite

HiveReactKit — Global Post Filtering Support

Centralized Post Filter Architecture

Continued improving HiveReactKit by introducing a global post filtering mechanism that allows applications to control post visibility consistently across different feed experiences.

Added global post filtering support through:
- setGlobalPostFilter
- getGlobalPostFilter
- subscribeGlobalPostFilter
Created a centralized approach for managing post visibility preferences.
Rebuilt the HiveReactKit package to expose the new filtering exports in the production bundle.
Linked HiveReactKit locally using:
- file:../HiveReactKit
Enabled immediate development updates between HiveReactKit and HiveSuite.
Kept the filtering functionality reusable so it can be consumed across different feed implementations.

The new global filtering architecture provides a shared foundation for HiveSuite to apply content visibility preferences consistently instead of implementing separate filtering logic for every individual feed.

HiveReactKit Filter Integration

HiveSuite — Hide Game Posts

Feed Settings Enhancement

Added a new Hide Game Posts preference to the Snaps feed settings, giving users more control over the type of content they want to see while browsing HiveSuite.

Added a "Hide Game Posts" checkbox to the Snaps feed settings.
Connected the setting to the new global post filtering system.
Applied the filter consistently across multiple HiveSuite feed experiences.
Ensured the preference can control game-post visibility without affecting other types of Hive content.
Integrated the functionality using the shared HiveReactKit filtering APIs.

This provides a simple way for users who prefer to focus on blogs, discussions, Snaps, communities, and other Hive content to reduce game-related posts from their feeds.

Hide Game Posts Setting

Global Filtering Across HiveSuite

Consistent Content Filtering

The Hide Game Posts preference has been applied across the major content feeds and pages within HiveSuite.

The filtering is supported across:

Blogs
Snaps
Waves
Threads
Moments
HiFind
Tag Feeds
Custom Snaps
Other supported feed views using the shared post filtering system

When the setting is enabled, HiveSuite automatically hides posts identified as HiveSuite game-related content from these feed experiences.

This creates a consistent filtering experience instead of limiting the preference to a single Snaps page. Users can move between different areas of HiveSuite while maintaining the same content visibility preference.

Global Feed Filtering

Custom Snaps Filtering

HiveSuite Game Post Filtering

Supported Game Content

The filter automatically handles supported HiveSuite game posts, including content associated with games such as:

Hive Wordle
Hive Grove
TicTacToe
Eight Ball
Slots
Spin Wheel
Bomberman
Other supported HiveSuite game posts

When Hide Game Posts is enabled, these posts are removed from supported feed views while other content remains available.

The filtering is implemented at the shared post-processing level, allowing the same behavior to be reused across different feed components and pages.

This approach also provides a scalable foundation for expanding the supported game-post detection in the future without requiring independent filtering implementations throughout the application.

Game Post Filtering

🚀 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

Read the full post

Hive checks all the boxes

andablackwidow — Wed, 30 Sep 2026 02:43:27 GMT

Some time ago @small.minion wanted me to write him something about Hive, why it is better than other chains. Once I started doing the research the answer turned out to not be so obvious. Ultimately we've only discussed some aspects, but I did not make it in time for European Blockchain Conference (preparing somewhat coherent article takes me far too much time), but since I didn't want the effort to go entirely to waste, I'm writing this post.

The promise

A lot has changed since the early days of Bitcoin. The innovations tied to crypto are enormous, their adoption also grew aside mere "price go up". But it looks like something might have been lost in the process.

"Be your own bank" - that was the phrase connected to the crypto from the early days. But what does it mean?

_source

Clearly it is not about keeping a stash of gold and other valuables hidden in a place where no one can take it away from you. The treasure has value only if there are other people that want to exchange that treasure for the goods they produce and services they provide, and when there is a way to actually make that exchange (directly or indirectly). So being your own bank is inevitably tied to other people through some financial system, everyone just wants that system to work in their favor. People are different though - some are very wealthy, some are poor, some want to take risks, others prefer safety, some are knowledgeable in financial or technical matters, others have other interests and don't want to need to be IT experts to just spend some coin, some move their funds a lot, other just put them away for couple decades. So the system to work in everyone's favor needs to be safe, cheap and easy to use, and it needs to have little to none counterparty risks. Even if one decides they want to use it via a proxy (because they can't be bothered to do it themselves) it is still beneficial to them if they are not bound to a handful of powerful corporations that traditional banks are today. Let's see different aspects of banking:

Banks follow rules. Clear rules mean predictability and confidence.
Banks not just keep, but multiply money.
Banks keep their own records. They don't need to rely on external services to tell them what's in their books.
Banks are a utility - other businesses use them as a service.
Finally, banks keep things private.

Let's examine each point in the context of crypto. Why are those points important and how much of the "be your own bank" can an individual really achieve in today's blockchains.

Governance

One of the aspects that didn't change from the start is openness of the source code of blockchains. With AI even more people can actively check whether the rules of particular chain make sense and are properly implemented. Same goes with tools that are used to actually interact with the chains.

The openness has no practical impact if one group of people holds exclusive rights to apply the rules and also make adjustments to the code - someone else is enforcing or rewriting law and you have no say in it. Transaction exclusion is within natural rules of all blockchains - not all valid transactions will make it to the blocks, for various reasons, technical or deliberate censorship, it gives block producers power over individual users, even if no changes to the code are ever made and they all run only official code. Even if that power is widely distributed, but limitted to large corporations, it is still not comfortable situation. Such entities are easy targets for external pressure (f.e. regulatory from governments), their interests might not align with interests of smaller holders. While reviewing this aspect of blockchains we'll be looking at who produces blocks, who decides who can be one of block producers and what are practical limitations of that decision.

_source

Important aspect of block production is the incentive structure - does blockchain reward producers correctly in relation to the requirements put on them? The higher the costs or knowledge and time required, the greater the reward needs to be. The opposite is also true - blockchain can be run solely by enthusiasts if it is very cheap to run. If incentives are not alligned, there is a danger of the chain stopping entirely, or that producers will seek revenue elsewhere, which decouples their interest from interests of the blockchain and its users.

Read the full post

A Small RC Delegation Request for HivePostify

hivepostify — Tue, 29 Sep 2026 18:03:51 GMT

Hello all community,

I have a simple request for anyone who can help.

HivePostify is currently onboarding new users and we are working to make free Hive account access easier for people who want to join the platform.

For this, we need more Resource Credits.

Why We Need RC

Every new account we claim and manage requires blockchain resources. As more people join HivePostify, our available RC becomes a limitation.

Right now, I am looking for RC delegation so we can continue claiming free accounts and support more new users without slowing down the onboarding process.

Our goal is to reach 10,000+ account claims over time.

What You Can Do

If you have unused Hive Power and can delegate some RC support to @hivepostify, it would directly help us with account onboarding.

Even a small delegation can help us continue this work.

There is no request for funding here.

The support we need is RC delegation.

Why It Matters

HivePostify is not only about posting.

The main direction now is freelancing, where users can create a profile, list their skills and services, and build opportunities through the platform.

More available RC means we can onboard more people and give them a smoother way to get started on Hive.

If you can delegate RC to @hivepostify, please consider helping us.

Thank you to everyone who has supported HivePostify so far.

HivePostify

https://hivepostify.com

HiveScope Chat: a decentralized chat where your identity is your Hive account / HiveScope Chat: un chat descentralizado donde tu identidad es tu cuenta de Hive

rzazo24 — Tue, 29 Sep 2026 08:04:06 GMT

🇬🇧 English

I've been working on a simple idea for a while: a real-time chat whose identity is the one you already have on Hive: no sign-up, no new passwords. Today I'm presenting it: HiveScope Chat.

What it is

A chat organized in rooms where you sign in with your Hive account using Hive Keychain (browser extension or mobile app). You sign a short message once with your posting key to prove the account is yours. The app never sees or stores your private key, only that signature.

Under the hood it runs on the Nostr protocol. Every message is a signed event, stored by a relay of my own that only accepts verified Hive accounts. The relay checks the signature against the account's real posting key, fetched live from the blockchain.

What you can do

Rooms with an expiration you choose (1 hour, 24 hours, 7, 30 or 90 days). When it expires, the room and its messages are deleted. Every room has a direct link.
Live messages, with history that loads as you scroll up, clickable links and up to 2000 characters.
Mentions (@account) and replies, with autocomplete, "new" badges and optional browser notifications.
Emoji reactions, counted per Hive account.
Who's online, per room and overall, and "@someone is typing…".
Search and sort rooms by activity, people online, message count or name.
Delete your own messages, also from another device linked to the same account.
Optional: share a new room on Hive as a snap, only if you press the button.
English and Spanish, dark and light themes, works on mobile.

Things worth knowing

Everything is public. Messages are Nostr events anyone can read. This is not private or encrypted messaging: don't post anything you wouldn't want to be public.
Presence (who's online) is visible to anyone using the app.
Profile pictures are loaded from images.hive.blog, Hive's public image service.
This is an early version. I've tested it quite a bit, but I need real use to polish whatever I've missed.

Open source

Everything is open source (MIT):

Relay (Go): https://github.com/rzazo24/hivescope-relay
Web app (React + TypeScript): https://github.com/rzazo24/hivescope-relay-web

If you're curious about how Hive is linked to Nostr (the posting-key signature, the validation in the relay…), it's explained in the READMEs.

Thanks for reading!

P.S.: Thanks to Claude for his invaluable help on this project 😁

🇪🇸 Español

Llevo un tiempo trabajando en una idea sencilla: un chat en tiempo real cuya identidad sea la de siempre en Hive, sin registrarse y sin contraseñas nuevas. Hoy lo presento: HiveScope Chat.

Qué es

Un chat organizado en salas donde entras con tu cuenta de Hive usando Hive Keychain (extensión del navegador o app móvil). Firmas una sola vez un mensaje corto con tu clave posting para demostrar que la cuenta es tuya. La app no ve ni guarda tu clave privada, solo esa firma.

Por debajo funciona sobre el protocolo Nostr. Cada mensaje es un evento firmado, y lo guarda un relé propio que solo acepta cuentas de Hive verificadas. Ese relé comprueba la firma contra la clave posting real de la cuenta, consultada en la cadena.

Qué puedes hacer

Read the full post

hive-139531 community on Hive

HiveSuite Development Update: Scheduled Posts Management & Blockchain Data Profile

HiveSuite Development Update: Scheduled Posts Management & Blockchain Data Profile

HiveSuite — Scheduled Posts Management

Edit Modal Enhancement

Unified Edit Flow

Automatic Refresh & Sorting

UI Simplification

HiveReactKit — Blockchain Data Profile Tab

New Blockchain Data Tab

Witness Data Integration

Parallel Data Fetching

Building the Future of Web3 Freelancing: Escrow Protection, Anti-Abuse Gating, and Mobile Network Hardening on HivePostify

Decoupling Services into Two Distinct Engines: Gigs vs Custom Jobs

Service Gigs (/marketplace):

Job Board (/jobs):

Anti-Abuse & Spam Protection: Account Verification Middleware

HiveSuite Development Update: RPC Reliability, Mobile Navigation & Core Architecture Improvements

HiveSuite

Core Application Architecture

HiveReactKit — Shared Component Library

Core Library Architecture

HiveSuite — Default RPC Upgrade

More Reliable Hive API Startup

HiveSuite — TypeScript & Callback Fixes

Blog Feed TypeScript Fix

Snaps Callback Compatibility

HiveReactKit — Default RPC Update

Shared Hive API Reliability

HiveReactKit — Mobile Scroll & FAB Improvements

Floating Action Menu Touch Fix

🐗⚡ Building BOAR | How I Fit an Offline AI Research Engine Into a Phone

Building BOAR: How We Fit an Offline AI Research Engine Into a Phone

1. From AOAIR to BOAR

2. One Brain at a Time & The 4.5-Second Tax

3. Why black holes bend spacetime?

The Fix:

4. First full benchmark run

HiveSuite Development Update: Root Post Editing & Custom Snaps Following Fix

HiveSuite

HiveReactKit — Root Post Editing Fix

Reliable parent_permlink Handling

HiveSuite — Root Post Editing

Improved Edit Post Modal

HiveSuite — Custom Snaps Following Fix

Following Feed Improvements

Accurate Follow Status

Authentication Sync

Improved Feed Filtering

🚀 Powering the Hive Ecosystem

HivePulse.app Community Feedback Container — Week 3

Welcome to the Week 3 of HivePulse.app community feedback!

If you use HivePulse, tell me:

HiveSuite Development Update: Global Post Filtering & Hide Game Posts

HiveSuite

HiveReactKit — Global Post Filtering Support

Centralized Post Filter Architecture

HiveSuite — Hide Game Posts

Feed Settings Enhancement

Global Filtering Across HiveSuite

Consistent Content Filtering

HiveSuite Game Post Filtering

Supported Game Content

🚀 Powering the Hive Ecosystem

Final Note

🔗 More Links

Hive checks all the boxes

The promise

Governance

A Small RC Delegation Request for HivePostify

Why We Need RC

What You Can Do

Why It Matters

HivePostify

HiveScope Chat: a decentralized chat where your identity is your Hive account / HiveScope Chat: un chat descentralizado donde tu identidad es tu cuenta de Hive

🇬🇧 English

What it is

What you can do

Things worth knowing

Open source

Reliable `parent_permlink` Handling