littleFedi development wish list

• Web Interface Admin Dashboard: I would like to one day be able to adjust configuration settings for my littleFedi instance through the web interface. Currently, configuration changes can only be made by editing the littlefedi.toml file through my server's terminal interface.
• Compose Button: I'd like a floating compose button that follows me around my instance. The mobile interface has this already, but on desktop the only place to compose a new post is at the top of the Home, Federated, Local, Bubble, Bookmarks, and DM feeds. (Note that composing from the Catch-up feed is not currently possible on desktop or mobile, and I'd like for that to be updated as well.)
• Media Pagination: It would be nice to be able to click/scroll through multiple images from a post containing more than one media file. Currently, a littleFedi user can only see one image at a time (i.e., expand an image, collapse the image, expand the next image—multiple taps/clicks for something that should really be swipeable/scrollable).
• Drafts: A way to save drafts for editing and posting later.
• Edit Scheduled Posts: I'd like to have the option to edit my scheduled posts in addition to rescheduling them. Currently, scheduled posts can only be rescheduled. To "edit" a scheduled post, a littleFedi user must delete, re-draft, and reschedule the post.

This next one is a long-shot, so I'm separating it from the more reasonable (IMO) wish list items above:

• Schedule Boosts: Hashtags and boosting are the primary means of increasing a post's visibility in the Fediverse. I follow accounts that post things I think more people might want to see, so I boost many posts, often. I boost so often, in fact, that I imagine my public feed is a bit overwhelming for followers at times. It would be awesome if I could schedule boosts in order to provide followers with some breathing room between reshares while still boosting my favorite people in the Fediverse.

Figured I'd put these wish list items in a public, centralized location until the #littleFedi development team creates an official location for feature requests. If any #littleFedinauts have their own wish list items that aren't on this list, please feel free to add requested features in the comments.

@stefano

Do you want to see a #littleFedi instance's directory?

Here it is. It's all here.

littleone@littleone:~/littleone $ ls -l
total 2534224
drwx------    5 littleone littleone          5 Oct 12 21:23 backups
drwxr-xr-x   30 littleone littleone         30 Oct 13 16:22 blogs
-rwxr-xr-x    1 root      wheel       28676230 Oct 12 11:19 littlefedi-freebsd-amd64
-rw-------    1 littleone littleone 4367925248 Oct 13 19:56 littlefedi.db
-rw-------    1 littleone littleone      98304 Oct 13 12:20 littlefedi.db-shm
-rw-------    1 littleone littleone  108442552 Oct 13 19:56 littlefedi.db-wal
-rw-------    1 littleone littleone       3645 Sep 30 19:48 littlefedi.toml
drwxr-x---  402 littleone littleone        402 Oct 13 16:43 media

#littleOne

A new build of littleFedi (2026.10.13) is out!

We've made several changes based on reports from our friends on this instance, feedback from those who have started self-hosting, and code reviews by the Little Computer People.

Here's a non-exhaustive changelog:

• Alt text changed while editing a post from a Mastodon client (Mastodon web,
  Phanpy, Elk, Ivory, Tusky and others) was silently dropped. It is now saved
  and sent to other servers with the edit.
• Alt text of images already attached to a post can now be edited from the web
  composer.
• When a remote author adds or changes alt text by editing a post, the change
  now shows up here too. Before, the post kept its old description, and stayed
  hidden for anyone filtering out media without alt text.
• PUT /api/v1/media/:id can now clear a description, and refuses media that
  is already attached to a post, as Mastodon does. Use the status edit instead.
• Alt text is limited to 1500 characters on the server too, not only in the
  browser. Longer remote descriptions are cut at the same length. The limit is
  reported as description_limit in /api/v2/instance.
• Media without alt text now report description as null in the API, so
  clients no longer show an empty ALT badge.
• New Favourites page in the web interface, in the main menu, listing the
  posts you liked, most recent first.
• Paging through /api/v1/favourites skipped or repeated posts after the
  first page. It now continues from the last post shown, like bookmarks.
• When the timeline tabs or the top menu do not fit on one line, they now
  show only their icons. Before, some themes cut the last items off or split
  them over two rows.
• Keep the canonical instance actor URL public in secure and allowlist modes,
  fixing a key-fetch deadlock with other authorized-fetch servers.
• With split domains, /api/v1/instance now reports the handle domain as uri,
  and actors carry a webfinger property with their canonical handle.
• Hashtags can now be followed from the search in Settings > Followed hashtags,
  even before any post uses them. Hashtag pages with non-ASCII names, such as
  #caffè, now open and follow correctly.
• New [web] redirect_guests_to_about sends signed-out visitors from / to
  /about, and [web] public_blog_directory = false puts /blogs and its
  sitemap index behind the login.
• public_local_timeline = false now also hides the links to the local
  timeline and asks for login on /public/local and when scrolling, not only
  on /.
• Signed-out visitors could load the federated and bubble timelines through
  the scrolling endpoint. They now get the login page.
• Moved profiles now show the destination and replace Follow with a link to
  the new account. Old posts remain accessible, and cached account data is
  refreshed as soon as the move is saved.
• Move notifications now show and link to the destination, while the account
  name still opens the original profile. Moves by different users stay in
  separate notification rows when grouping is enabled.
• Cached timelines now pick up new posts when blog publishing is enabled,
  without waiting for the page cache to expire. Incoming boosts also update
  open timelines through streaming.
• Profile bios can now contain up to 5,000 characters in the web editor,
  up from 500.
• The notifications page now has a Mark all as read button.
  Clear all still deletes them.
• Follows imported from CSV are now saved before the upload is confirmed and
  resume after a restart. Settings and the API show progress, existing follows
  and failed lookups. Follow requests and their outgoing deliveries are saved
  together, and only one import can run per account. This uses the existing
  database schema.
• CSV files over migration.max_follows_import are now rejected instead of
  being silently truncated. Set the limit to 0 to import the whole file.
• CSV imports now leave an internal notification when they finish or stop
  after a terminal error, with a summary and a link to that import. Retries
  do not duplicate the notice; no email or push is sent.
• Multiple Mastodon API Fixes
• Replies in the web interface now keep the original post's content warning,
  both in the timeline and on the thread page.
• Media can be added to a post by dragging files onto the composer or by
  pasting an image, as well as with the file picker. Files dropped elsewhere
  on the page go to the main composer instead of replacing the page.

Enjoy!

#littleFedi #Fediverse

Dear #littleOne friends,
A new build of littleFedi is now powering this instance!

We've made several changes based on reports from our friends on this instance, feedback from those who have started self-hosting, and code reviews by the Little Computer People.

There are still a few things to integrate, but this will probably be the next build we release (likely tomorrow or on the 14th, two weeks after the previous release).

I'm attaching a non-exhaustive changelog:

• Alt text changed while editing a post from a Mastodon client (Mastodon web,
  Phanpy, Elk, Ivory, Tusky and others) was silently dropped. It is now saved
  and sent to other servers with the edit.
• Alt text of images already attached to a post can now be edited from the web
  composer.
• When a remote author adds or changes alt text by editing a post, the change
  now shows up here too. Before, the post kept its old description, and stayed
  hidden for anyone filtering out media without alt text.
• PUT /api/v1/media/:id can now clear a description, and refuses media that
  is already attached to a post, as Mastodon does. Use the status edit instead.
• Alt text is limited to 1500 characters on the server too, not only in the
  browser. Longer remote descriptions are cut at the same length. The limit is
  reported as description_limit in /api/v2/instance.
• Media without alt text now report description as null in the API, so
  clients no longer show an empty ALT badge.
• New Favourites page in the web interface, in the main menu, listing the
  posts you liked, most recent first.
• Paging through /api/v1/favourites skipped or repeated posts after the
  first page. It now continues from the last post shown, like bookmarks.
• When the timeline tabs or the top menu do not fit on one line, they now
  show only their icons. Before, some themes cut the last items off or split
  them over two rows.
• Keep the canonical instance actor URL public in secure and allowlist modes,
  fixing a key-fetch deadlock with other authorized-fetch servers.
• With split domains, /api/v1/instance now reports the handle domain as uri,
  and actors carry a webfinger property with their canonical handle.
• Hashtags can now be followed from the search in Settings > Followed hashtags,
  even before any post uses them. Hashtag pages with non-ASCII names, such as
  #caffè, now open and follow correctly.
• New [web] redirect_guests_to_about sends signed-out visitors from / to
  /about, and [web] public_blog_directory = false puts /blogs and its
  sitemap index behind the login.
• public_local_timeline = false now also hides the links to the local
  timeline and asks for login on /public/local and when scrolling, not only
  on /.
• Signed-out visitors could load the federated and bubble timelines through
  the scrolling endpoint. They now get the login page.
• Moved profiles now show the destination and replace Follow with a link to
  the new account. Old posts remain accessible, and cached account data is
  refreshed as soon as the move is saved.
• Move notifications now show and link to the destination, while the account
  name still opens the original profile. Moves by different users stay in
  separate notification rows when grouping is enabled.
• Cached timelines now pick up new posts when blog publishing is enabled,
  without waiting for the page cache to expire. Incoming boosts also update
  open timelines through streaming.
• Profile bios can now contain up to 5,000 characters in the web editor,
  up from 500.
• The notifications page now has a Mark all as read button. Clear all still deletes
  them.
• Follows imported from CSV are now saved before the upload is confirmed and
  resume after a restart. Settings and the API show progress, existing follows
  and failed lookups. Follow requests and their outgoing deliveries are saved
  together, and only one import can run per account. This uses the existing
  database schema.
• CSV files over migration.max_follows_import are now rejected instead of
  being silently truncated. Set the limit to 0 to import the whole file.
• CSV imports now leave an internal notification when they finish or stop
  after a terminal error, with a summary and a link to that import. Retries
  do not duplicate the notice; no email or push is sent.
• Multiple Mastodon API Fixes
• Replies in the web interface now keep the original post's content warning,
  both in the timeline and on the thread page.
• Media can be added to a post by dragging files onto the composer or by
  pasting an image, as well as with the file picker. Files dropped elsewhere
  on the page go to the main composer instead of replacing the page.

#littleFedi

#littlefedi + Garage S3

1. Create a bucket, because I will using custom domain for this bucket (different with endpoint domain name) so the bucket name is my custom domain name eg. img.domain.com,
2. Enable "exposing website access" to img.domain.com bucket Garage: exposing websites,
3. Configure a reverse proxy with Caddy or nginx to point the img.domain.com to Garage web access Garage: Reverse Proxy
4. Edit the littlefedi.toml file

[media]
backend = "s3"
public_base_url = "https://img.domain.com" # custom domain

[media.s3]
bucket = "img.domain.com" # bucket name
endpoint = "s3.endpoint.com # real Garage S3 endpoint
region = "us-east-1"
access_key = "myraccesskey"
secret_key = "mysecretkey"

Save and start littlefedi

PS: I need to download binary or build littlefedi source with S3 support.