#39
8 posts · Last used 13h
Boosted by @fedicat@pc.cafe
A new build of littleFedi (2026.11.16) is out!
The Little Computer People have been busy, and we're happy to share a new release of littleFedi!
Before reading the long changelog, there's something important we'd like you to know about upgrading.
⚠️ Important: Upgrading littleFedi
This release includes database migrations that run automatically on the first startup. Some of them may take a while, especially on larger databases or slower hardware.
Please read these instructions carefully before upgrading.
Stop littleFedi and make a backup.
Back up your database, configuration, and media files. Remember to save any encryption keys stored in the service environment, too.
See docs/backup-restore.md for backup and restore instructions.
Replace the binary.
Download the new binary for your operating system, CPU architecture, and database/media backend. Replace the old binary and start littleFedi using your existing configuration.
No separate migration command is needed.
Allow the database migrations to finish.
littleFedi will automatically perform the necessary migrations on its first startup. One of these rebuilds SQLite indexes and may take considerable time on large databases, particularly when running from an SD card.
Make sure your service manager allows enough time for startup.
Do not stop or restart littleFedi while migrations are running.
Check that everything is ready.
Wait for startup to complete, then check the logs and the /readyz endpoint before using your instance.
Subsequent startups will skip migrations that have already completed.
Need to roll back?
Stop littleFedi and restore your pre-upgrade backup before starting the previous binary.
Never run an older binary against a migrated database.
What's new?
As with previous releases, many of the changes come directly from the people who make this project worthwhile: our friends on this instance, those who have started self-hosting littleFedi, and everyone who has taken the time to test, report bugs, suggest improvements, or review our code.
We've continued working on the things that matter to us: keeping littleFedi lightweight, efficient, reliable, and enjoyable to use, without unnecessary complexity.
And yes, we're still very much committed to making the Fediverse accessible even to the smallest computers!
Here's what's changed in this release:
Changelog
Account blocks now hide posts in profiles, search, threads, quotes and
streaming, and stop new follows, mentions, replies, favourites, reactions,
poll votes, boosts and direct messages in both directions. Blocked profiles
keep only the account's identity and block/report actions. Existing direct
conversations stay readable, and email and push notifications check for
blocks before sending. Other accounts on the same server remain reachable,
even when they share an inbox. Public posts remain available to anonymous
readers and other instances.
Static blog pages now leave out unlisted replies. Only replies with public
visibility are included. Rebuild existing blogs after upgrading to remove
unlisted replies from pages generated by earlier versions.
Content warnings now display apostrophes and other HTML entities correctly
in posts and notifications, instead of showing codes such as '.
Source builds now require Go 1.27.4. Updated the Go dependencies, bundled
Alpine.js and htmx, and the security tools used in CI. Rebuild existing
binaries to pick up the Go security fixes.
With housekeeping.max_delete_per_run = 0, status pruning now keeps
going in batches of 500 until no eligible posts remain. Previously, remote
pruning stopped after 500 posts and local pruning after 500 per account.
Positive limits still apply across local and remote posts. Failed deletions
are left for the next run rather than retried in a loop.
The inbox no longer fetches a key for an unknown actor's self-delete.
Requests with a Signature header are acknowledged with 202 and dropped
when the actor and deleted object are the same URI and the account is absent
locally. Domain blocks still apply; deletes of known accounts and posts
still need authentication.
Incoming HTTP signatures now have their timestamps and body digests checked
before fetching a public key or verifying the signature. Stale requests and
damaged bodies can be rejected without a network request.
Public instance counts on /about and the v1/v2 instance APIs are cached
for 30 seconds, instead of counting the database on every request. The
admin dashboard still reads fresh counts.
SQLite reply and quote indexes now leave out NULL entries. This reduces
their size and avoids a slow query plan when loading RSS feeds. Migration
007 rebuilds all four indexes at startup and can be slow on large databases,
especially on SD cards. Allow extra time for the first startup after
upgrading; later starts skip the migration.
The interface is now available in Catalan, thanks to Jolupa, who
translated it. It can be picked in the settings like the other languages,
and Catalan is also in the list of languages a post can be tagged with.
Strings added after the translation was made were filled in afterwards and
are the ones most worth a second look.
Boosts can be scheduled, to spread them out instead of filling followers'
timelines all at once. Hold the boost button for half a second, or open the
post, and pick a time under "Boost later". A quick press still boosts right
away. Scheduled boosts show up on the Scheduled page next to scheduled
posts and can be moved or cancelled there. If the post is deleted or
becomes impossible to boost before then, the boost is dropped. Mastodon
apps have no notion of a scheduled boost, so the API leaves them out.
Scheduled posts can now be edited, not just moved to another time. The
Edit button on the Scheduled page opens the post in the composer with
everything it had, including the time, and saving puts it back on the
schedule. Before, the only way was to cancel it and write it again. A post
that is already being published can no longer be edited.
Posts can be saved as drafts. The composer has a "Save draft" button next
to Post, and the new Drafts page lists them, newest first. Opening one
brings back the text, content warning, audience, language, attachments,
poll and expiry, and the post it replies to or quotes. Posting or
scheduling a draft removes it. Everything is a plain form, so it works
without JavaScript and in text browsers. Drafts live on the server and are
not shared with Mastodon apps, which have no API for them.
The image viewer can now move between the pictures of a post. Use the
arrows on screen, the left and right keys, or swipe on a phone. Before, each
picture had to be closed and the next one opened by hand. Without
JavaScript nothing changes: each picture still opens on its own.
In French the image viewer had no name for screen readers. The apostrophe
in "Visionneuse d'images" broke the expression that sets it. Translated
labels are now read from data attributes, so quotes in a translation can no
longer break the script.
The Roost theme works better on phones. Post actions fit on one row, the
back link is a flat row instead of a pill against the screen edge, the
profile banner and avatar no longer fill the first screen, and the bottom
bar marks the current page without a filled block.
Unread mentions and direct messages now stand out from the other unread
notifications. In Roost the mention colour was the same blue as the unread
mark, and in every theme their rows took the same background as any unread
row. Herd and Ink also get mention colours further from their accent.
Filters set to warn now work on the catch-up page. The filtered posts were
shown in full, without the filter notice. Filters set to hide already
worked there.
Direct message notifications have a magenta edge, an envelope icon and their
own label, so they stand apart from public mentions.
Boosts from a followed account can now be hidden from the home timeline,
with the "Hide boosts" button on their profile or the matching switch in
Mastodon clients. Their own posts still show up. Boosts already in the
timeline go away too, and come back if boosts are shown again. The
reblogs parameter of the follow API was accepted but ignored until now.
Push delivery now follows up to three 307/308 redirects within the same
HTTPS origin. The Mastodon app relay redirects endpoints without a trailing
slash; those pushes previously failed after all retries.
Pushes for favourites, boosts and federated mentions now carry
notification_id. Those jobs were built before the notification was stored,
so the ID was missing, and the official iOS app showed only the relay's
placeholder trumpet instead of the notification.
The bookmark button on boosted posts now stays in sync after refreshing
the home timeline. Before, it could appear inactive while the post was still
bookmarked, and clicking it again removed the bookmark.
Replies no longer show the previous post as unavailable after it has been
downloaded. Refreshing or reopening the reply now keeps the correct reply
target in timelines, boosted posts and Mastodon clients. The open thread
page also updates its reply label as earlier posts arrive.
Redrew the quote icon. The old one, two squared-off hooks side by side,
could be read as "SS". It now looks like a pair of quotation marks.
Logging in with toot from the command line now works. toot opens
/oauth/authorize/ with a trailing slash, which returned 404. URLs with a
trailing slash are now routed like the ones without, as on Mastodon.
With require_approval on, new accounts were created already approved: they
could sign in at once and never showed up in the approval queue. They now
wait for an administrator. Accounts registered while the bug was present
stay approved; check recent signups if the setting is on.
Filter keywords created from a Mastodon client with whole_word turned off
were saved with it on. Leaving whole_word out still means on, as in
Mastodon.
Mastodon apps no longer show littleFedi's own notification types (follow
accepted, unfollows, blocks, emoji reactions, blog rebuilds and others) as
broken entries, and their unread badge no longer counts them. A client can
still ask for them with types[], which the notification endpoints now
honour. exclude_types[]=pleroma:emoji_reaction now works too.
The user:notification stream carries only notifications. Before, it also
sent home timeline posts, which some clients (Tuba) showed as empty
notifications.
The instance documents report image_matrix_limit as a pixel count, taken
from max_image_pixels and max_image_dimension. It was 4096, which clients
read as 4096 pixels in total and used to shrink uploads to a thumbnail. The
video limits Mastodon's iOS app requires are there too.
New client API endpoints: GET /api/v1/accounts?id[]=,
/api/v1/accounts/lookup, /api/v1/accounts/familiar_followers and
/api/v1/notifications/policy. Mastodon for iOS and Tuba call them.
Push notifications now reach the Mastodon apps (Mastodon for Android and
iOS, Tusky, Ice Cubes, Ivory, Mona). Apps that don't ask for
standard: true get the older aesgcm encoding, which is the only one
several of them can decrypt, and every push now carries the access token
and a numeric notification ID, without which the apps drop it. Form encoded
subscriptions are accepted, and the subscription ID is a number as the apps
expect. Subscriptions made before this release keep the old behaviour:
turn notifications off and on again in the app, or sign in again.
Polls no longer break Mastodon for iOS and Android. own_votes and emojis
are always lists, and expires_at uses Mastodon's date format.
Deleting a post from an app returns the deleted post with its source text,
so "delete and redraft" keeps the text. Deleting it twice returns 404.
Timeline paging: min_id returns the page right after the cursor instead of
jumping to the newest posts, which made apps skip everything in between when
filling a gap. A cursor pointing at a deleted post keeps working, and an
unknown max_id returns an empty page instead of the top of the timeline.
min_id and since_id work for notifications too.
Link headers are now absolute URLs and keep the other query parameters.
Followers, following, blocks, mutes, favourites, bookmarks, lists and list
members send them too, so apps can load more than the first page.
Media sizes are reported under meta.original as well, and remote media
keep their blurhash and size. Apps used them to lay out images before they
load.
Accounts without an avatar or header point to a placeholder image instead of
an address that returned 404. Accounts also report uri and
hide_collections, and relationships requested_by and languages.
The default post visibility and language set in the profile are reported to
apps and used when an app leaves them out.
/api/v2/instance reports the VAPID key under configuration.vapid and
translation.enabled. Mastodon for iOS reads both.
Loading images, avatars and emoji no longer counts against the rate limit.
Scrolling a busy timeline could hit it, and every API call after that failed.
An API request over the limit now gets a JSON error with Retry-After, and
unknown API routes return JSON 404 and 405 errors instead of HTML.
littleFedi now logs a warning when requests come from a local reverse proxy
that is not listed in http.trusted_proxies. In that case every visitor
shares the proxy's rate limit.
CORS preflight allows the headers the browser asks for (Idempotency-Key
among them) and exposes Link and Retry-After to web clients.
Idempotency-Key is honoured when posting: a retried request returns the
post created the first time instead of a duplicate.
Tokens from client_credentials (the app's own token, before a user signs
in) are treated as anonymous on public endpoints instead of being refused.
Filters: keywords_attributes works when creating and editing a filter, in
JSON and form encoding, and the /api/v2/filters/:id/keywords and
/api/v2/filters/keywords/:id endpoints are new.
New endpoints: GET /api/v1/accounts/search,
/api/v1/statuses/:id/history, /api/v1/timelines/direct and
/api/v2/notifications/unread_count.
The streaming API accepts the token in Sec-WebSocket-Protocol, as the
Mastodon web client sends it, and tokens limited to read:statuses and
read:notifications.
The "Clear all" button on the notifications page is now called "Delete
all", in every language, since that is what it does.
Profile fields: up to four label and value rows on your profile, edited in
Settings or from any Mastodon app, and shown under the bio on the profile
page. They are sent to other servers like Mastodon's, and the ones remote
accounts publish are now shown on their profiles. Remote accounts already
known get theirs the next time their profile is fetched again. Links work;
verified_at is always empty, as littleFedi does not check rel="me"
links.
Apps can mute a conversation (POST /api/v1/statuses/:id/mute and
/unmute). Mentions, likes, boosts, quotes, edits and reactions in that
thread stop notifying you.
Apps can keep a private note on an account
(POST /api/v1/accounts/:id/note). Only you see it.
Followers can be removed from an app
(POST /api/v1/accounts/:id/remove_from_followers). A remote follower's
server gets a Reject of the follow, as from Mastodon.
Conversations can be removed from the list from an app
(DELETE /api/v1/conversations/:id); a new message brings them back.
POST /api/v1/conversations/:id/read works too.
Saving the profile from an app with an empty bio or display name now clears
it. Before, empty values were ignored and the old text stayed. The default
post visibility and language set in an app are saved too.
MastoBlaster could not read its push subscription: the alerts object had
no update key. It is now there, and apps can turn on pushes for edited
posts. Renaming a list and changing push alerts from MastoBlaster failed
with 405, because it sends PATCH; both endpoints now take PATCH as well
as PUT, like Mastodon.
Three database migrations run at startup. One adds the standard and
access_token columns to push_subscriptions. One adds
accounts.fields_json and the thread_mutes, account_notes and
hidden_conversations tables. The last adds
push_subscriptions.notify_update. All of them only add, nothing existing
is changed, and all can be rolled back.
A big thank you to everyone who has been following this little adventure, testing new builds, sharing feedback, and helping us improve.
littleFedi is still a young project, and there's plenty more to do. But every release brings us a little closer to what we've wanted from the beginning: a federated social platform that's simple to run, easy to maintain, and doesn't require a powerful server just to participate in the Fediverse.
Small computers deserve a place in the Fediverse, too. ❤️
Happy upgrading, happy self-hosting, and stay tuned!
The Little Computer People
#littleFedi #Fediverse #SelfHosting #OpenSource OwnYourData
Late Night Ambient | Eurorack Performance #39 (MOMENTS)
https://www.matrixsynth.com/2026/09/late-night-ambient-eurorack-performance.html
#Synthesizers #Eurorack #AmbientMusic
Meta's VR Glasses、了解しましたです
Meta's $1,300 VR Glasses look like the Vision Pro sequel Apple should be making https://www.engadget.com/2267218/meta-vr-glasses-price-specs-apple-vision-pro-comparison/
#Apple #LLM #news #bot
Earth’s Crust Is ‘Unzipping’ Under Italy, Scientists Say https://www.byteseu.com/2355293/ #Apennines #Earth'sCrust #MountainRange #Science #TyrrhenianSea
🚨 [CISA-2026:0727] CISA Adds One Known Exploited Vulnerability to Catalog (https://secdb.nttzen.cloud/security-advisory/detail/CISA-2026:0727)
CISA has added one new vulnerability to its Known Exploited Vulnerabilities Catalog, based on evidence of active exploitation. These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose significant risk to the federal enterprise.
⚠️ CVE-2025-68686 (https://secdb.nttzen.cloud/cve/detail/CVE-2025-68686)
- Name: Fortinet FortiOS Exposure of Sensitive Information to an Unauthorized Actor Vulnerability
- Action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Known To Be Used in Ransomware Campaigns? Unknown
- Vendor: Fortinet
- Product: FortiOS
- Notes: https://fortiguard.fortinet.com/psirt/FG-IR-25-934 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2025-68686
#ZEN #SecDB #InfoSec #CVE #CISA_KEV #cisa_20260727 #cisa20260727 #cve_2025_68686 #cve202568686
Weak housing market could imperil Australia’s economy https://www.byteseu.com/2152366/ #Australia'sEconomy #CashRate #economy #HousingMarket #InterestRates #MarketSlowdown #OilPrices #TheReserveBank
AI bez lukru #39: AI wie, że się rozwiedziesz
Cześć! Z tej strony Tomek Turba. AI bez lukru to cykl moich felietonów o sztucznej inteligencji bez marketingowego lukru, bez korporacyjnych slajdów i bez bajek o “rewolucji, która wszystko zmieni”. Pokazuję AI taką, jaka jest naprawdę: z absurdami, wpadkami, halucynacjami i konsekwencjami, o których rzadko mówi się głośno. Bez zadęcia,...
#Aktualności #Teksty #Ai #BezLukru #Felieton #Przewidywanie #Psychologia #Rozwód #Schemat
Mia Moore (NET#39 Clemson Tigers) scores 🔥31 points.
That's Moore's 2nd game with 30+ points this season.
🚨 Sets a new season high in points (31).
[NET#88 Georgia Tech 65 @ NET#39 Clemson 67 2OT] @clemsonwbb #WCBB
You've seen all posts


