Announcing hive.micro: A New Microblogging Platform on Hive

avatar

Hey everyone,

Today I'm excited to announce the soft launch of a new project I've been working on: hive.micro.

What is hive.micro?

062.png

hive.micro is a microblogging platform built on the Hive blockchain, similar in spirit to Twitter, Threads, or Mastodon. The core idea is to provide a space for simple sharing without the complexities of the rewards mechanism. Sometimes you just want to share a quick thought, link, or update without thinking about votes or payouts.

063.png

To achieve this, the platform uses custom_json operations instead of standard posts or comments. This means your micro-posts are stored permanently on the blockchain but don't create rewardable content. Because it reads blocks in small chunks, there's a slight delay between posting and seeing your message appear, but that's just the nature of blockchain technology.

Features

The platform is designed to be a familiar and straightforward experience. It uses your existing Hive account and following list to build your feed and profile.

Some of the key features include:

  • Light and Dark Modes: Easily switch between a light or dark theme to suit your preference.
  • Standard Social Features: The platform supports mentions, tags, likes (hearts), replies, and user profiles.
  • Quorum-Based Moderation: To prevent abuse, the platform has a simple, quorum-based moderation system that can be customized by community operators.
  • Fully Customizable: For those who want to run their own instance, the entire platform is configurable through environment variables, allowing you to create your own unique community with its own rules.

064.png

Call for Testers

This is a soft launch, and the platform has not yet been tested under any significant load. I would greatly appreciate some more testers and eyes on the project. If you're interested, please head over to the site, login with Keychain, and start posting. Let me know what you think!

As always,
Michael Garcia a.k.a. TheCrazyGM

hiveproject dev micro archon tribes pimp proofofbrain
0
0
0.000
15 comments
avatar

Congratulations @thecrazygm! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You got more than 1500 replies.
Your next target is to reach 1750 replies.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out our last posts:

Our Hive Power Delegations to the August PUM Winners
Feedback from the September Hive Power Up Day
Hive Power Up Month Challenge - August 2025 Winners List
0
0
0.000
Reply
avatar

Using custom_json to skip rewards is a smart call. It removes the pressure and makes quick posts feel natural, like jotting a sticky note that sticks forever. How are you picking quorum defaults for moderation and what threshold seems to curb spam without blocking normal chatter? If instances can tweak rules with env vars, could they also route certain tags into custom streams?

0
0
0.000
Reply
avatar

The moderators is a comma separated list of accounts, and you can set it to anything starting with single mod (1/1) to any amount (it just count number of mods that agree post should be hidden) (x/y) all the mod attempts are logged and there is a control panel with options. e.g.

image.png

image.png

The idea was that anyone could spin up a feed based on their custom_json tag (if i change the env for hive.micro to bob.place it changes everywhere in the app and only reads those custom_json) and each group could set their own moderators etc.

Originally I was against adding moderation at all, but then, not that I'm aware that it has ever happened, I don't want to be responsible for CSAM or anything like that.

RE: the routing tags, I might look into that e.g. sending #NSFW to its own page. Always looking for input, thanks for the idea!

0
0
0.000
Reply
avatar

That quorum setup makes sense, and the audit log is a solid call. Could the threshold be set per group and include an unhide path, like a separate vote type or timed review, and are those logs available via a public endpoint so others can audit decisions? For routing, you could let instance owners define simple rules in env or a JSON file to map tags to streams, plus user level filters so people can auto hide or divert tags they pick. Also curious if you plan a soft hide that collapses posts in the main feed while keeping them reachable on the author profile.

0
0
0.000
Reply
avatar

Honestly, I hadn't thought that far, but those are all fantastic ideas. Noted!

0
0
0.000
Reply
avatar

Love it. If you add an audit endpoint, a simple GET that lists decisions with post id, group, voter, vote, and timestamp would let anyone verify the quorum math. For moderation config, per group vars like MODS and THRESHOLD keep it clear, and a route rule that maps a tag in custom_json to a stream would cover most needs. When you get to routing, letting users mute tags and accounts at the client layer will make feeds feel clean.

0
0
0.000
Reply
avatar

Builders are gonna build! Nice work, my friend, and I like the idea of taking voting and payouts out of the equation, as I think that would remove a lot of the pressure about writing an 'acceptable' post. I don't have a lot of spare time, but I'll certainly give it a whirl. 😁🙏💚✨🤙

0
0
0.000
Reply