iiinova — where your digital self keeps evolving

iiinova is part of the Atmosphere — an open, public network where you own your identity.

Hollo :hollo:

@hollo.hollo.social.ap.brid.gy

:hollo: A federated single-user microblogging software. [bridged from hollo.social/@hollo on the fediverse by fed.brid.gy ]

Posts Replies Media

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 20/05/2026

Hollo 0.9.0 is out. github.com/fedify-dev/hollo/discuss… The biggest change this release is a complete redesign of every server-rendered page. Pico CSS is replaced by a new design system built on UnoCSS, and your chosen theme color now tints your […] [Original post on hollo.social]

0110 10

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 20/02/2025

#Hollo v0.6.0, the next minor release, will have theme colors on your profile pages. Powered by Pico CSS, see the list of all available colors in the _Colors_ section from their docs. Want to give it a try in advance? Try v0.6.0-dev.397, an unstable release, at your own risk.

015 5

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 31/12/2024

@liaizon Does it? We see the quote post being expanded in @phanpy though.

000 0

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 27/12/2024

Starting with #Hollo 0.4.0, you can allow your profile to be discovered in the public directory. Under the hood, this option corresponds to Mastodon's `toot:discoverable` property.

034 4

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 22/12/2024

Okay, testing #Hollo with #Node.js is cruising along. It's consuming up to 3 GB of memory at peak times, but that's a huge improvement over Hollo with #Bun, which was consuming over 8 GB of memory at peak times. So, yes, starting with Hollo 0.4.0, we'll use Node.js instead of Bun!

Memory usage chart for the hollo.social server. You can see that before December 18th, the point at which we switched to Node.js, the memory usage fluctuated between 1 GB and 8 GB, but since then, it's been mostly stable around 1 GB. It did spike to 3 GB at peak times, but only briefly during the entire test period.

010 1

Hollo :hollo: @hollo.hollo.social.ap.brid.gy · 17/12/2024

#Hollo is currently testing #Node.js instead of #Bun. (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun. The main reason for switching […] [Original post on hollo.social]

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.

211 2