Local timeline
@renata@cosocial.ca Hoje havia um movimento intenso quando passei pelos prédios de humanas a caminho do trabalho (~11 a.m.) e na hora que saí (~7 p.m.) havia uma turba animada na região do Básico chamando à luta. Espero que cresça
@nuke@openb.app Hello from Canada.
Grateful to learn about #Openbook and how it can run on shared hosting.
It 'feels' like Friendica, but looks more accessible for non-technical people to get up and running.
Not unlike spinning up a wordpress, or in my case, a classicpress, website via cpanel.
Hopefully these few questions I have are not too much of a bother, as I understand from reading your roadmap, it is still a work in progress.
Similar to how the /community page of a friendica site, for example :
https://poliverso.org/community
...can also become the default public page, meaning non-logged in users, can see the public activity of the instance, can Openbook allow for this?
Can you clarify to how RSS feeds can be added and act like users of an Openbook instance; are they treated like how Friendica allows for RSS feeds to appear in the "community" page?
When RSS Feeds are being added, do they end up in "Local" Community(ies) ?
Lastly, how many active users might be too many for Openbook?
50 ? 200?
How big of an instance is okay to run on regular shared hosting?
I intend to install and try it out this weekend as I can devote proper time to it.
Thank you so much.
@renata@cosocial.ca There was a time—in the 1960s and 70s—when they took to the streets; now, they no longer do.
@sturai@kqiscygp6gq4xxhoehvd7v3epze6jetqdxcsvovl6khlq2kjnlra.mesh.lighthouse.alimara.de this is extremely cool. Let me know how it does!
@Canadian_Eh@mas.to Ohhhh... Thank you for sharing this!
Immediately reminded me of the last time I was there!
Wonderful feeling, even after all this time, simply by remembering it.
Yay!
Find's ja doof, dass Signal noch immer nicht mehrere Benutzenden-Konten verwalten kann.
So könnte eins z.B. unterscheiden zwischen "Privat" und "Geschäftlich", ohne ein zweites Smartphone verwenden zu müssen.
Oder eins verwendet Delta.Chat, damit geht das.
Müssten sich Kund:innen halt ggf. nur auch installieren wollen.
(Und dann gab es noch die gute, alte E-Mail, ja, ja ;)
#Signal #DeltaChat #Messenger #Selbstständigkeit
@lilpoes I'll send you some information - I still have to create the "hints" user so, while the full documentation hasn't been published, I can post some guides like that.
It is a matter of lack of time, not of energy or motivation 😉
@stefano @fd0 This software architecture principle of "no nonsense is primary" immediately brings Marie Kondo to mind :
https://en.wikipedia.org/wiki/The_Life-Changing_Magic_of_Tidying_Up
I did not grasp what the acronym LCP means, so of course wikipedia'd it :
https://en.wikipedia.org/wiki/Link_Control_Protocol
And again, Marie Kondo stays in mind.
@fd0 I have a small script that produces some stats, so I can tell you something about this:
As of 8 October 2026, littleOne has 53 registered users and stores about 1.71 million posts and boosts, including 4.983 local ones.
The application’s data totals approximately 6.25 GiB, but around 2 GiB is remote media cache (set in lazy mode): images, videos and other media from federated instances, cached on demand with a configured 72-hour lifetime and a 2 GiB limit.
Excluding that shared cache, the remaining application data occupies about 4.30 GiB, averaging 83 MiB per registered user. With ZFS compression, those files occupy approximately 2.56 GiB of allocated disk blocks, or 50 MiB per user.
Users’ own uploads, thumbnails, avatars, headers and blogs average just 4.36 MiB per account, with a median of 1.18 MiB. That figure excludes the database, which also stores shared federated posts, profiles and interactions.
These measurements exclude backups, filesystem snapshots and the operating system.