Local timeline
Großartig:
"Fungiert der Anwalt dagegen nur als Durchlauferhitzer für ungeprüfte KI-Texte, ..."
https://www.lawblog.de/archives/2026/10/20/gericht-weist-ki-schriftsatz-zurueck/
@hugovalters@mastodon.social for #proxmox #pve the installation-time default is 10 percent, capped at 16 GiB.
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_limit_memory_usage
This is a fresh #littleFedi instance. Currently I am importing a "follows"-list with 979 accounts, exported from a "real" Mastodon instance...
Watching it feels... "interesting" :-)
I've upgraded my (still experimental) #littleFedi -instance to "littlefedi-linux-amd64-2026-10-13" a moment ago. While I read the original announcement (https://littleone.littlefedi.social/@littlefedi_official/01a1342b-11e6-7952-8be2-ac959bc4cf7a) I missed an easy-to-find upgrade documentation.
But actually it seems not to need one! I just put the new binary "over" the old one, killed the running littleFedi process and started it again. Seems to work :-)
Thank you, @stefano@bsd.cafe
Hello #Fediverse,
I am going to start an experiment:
- run my own #Activitypub-Instance utilizing #Littlefedi
- use multiple accounts to enhance my own reading experience and to separate boosting from original content
It is important to note that this is a single-user instance, at least currently. This means all accounts belong to the very same human being.
- @42 = original content, rarely boosts, may quote to add information, only following a very few accounts
- @solidvoid = mainly reading other peoples toots; this one follows a lot of people; will boost only positive toots, which are really rare nowadays :-(
- @generalfailure = boosts mostly negative events and topics
Btw: this is not a "normal" toot but a blogpost with its own nice URL --> https://littlefedi.faq7.de/@42/blog/sitenote/ :-)
Well, #littleFedi works quite well - I think. My current problem (with my own instance) is to find my accounts "from the outside"...
And I need to follow my alter egos and some external accounts before I am convinced :-)
Installation was one thing. Producing *content* is much more difficult...
First connect from an external browser --> immediate success :-)