@phanisvara (streams) imo there is no point to use the app if you need to go to the browser anyway. Or you could upload with rcx (which will only upload the file to a folder) and compose the post later.
Best would be if someone could hack the app so you could also post some text with the uploaded file :thinking:
@Witcraft (Hubzilla) AFAIK Hubzilla PWA works with chrome on stock android (have tested it some time ago). It will however never work on phones which do not have google (play) on their phones since this seems to be a hard requirement.
I have just added the possibility to modify bootstrap via sass in redbasic. This finally allows channels to change the primary color. Sysadmins have more possibilities to customise bootstrap: https://getbootstrap.com/docs/5.3/customize/sass/
The Faces addon (requires python 3 and the python deepface library) will provide the Faces App which will detect faces in your photos and let you tag them. More info about this addon is available from its readme file.
The Logger Stats addon provides a tool for admins and developers to display various hub activities in a graphical way. It requires logging to be enabled to collect the data.
UI:
The content of the right aside area is now moved to the left aside on small screens.
Seen public stream items are now removed from the new public stream notifications area.
Under the hood:
We now use a new language detect library which supports 110 languages and should improve detection of rtl languages. Posts in rtl languages should now be displayed rtl. This library requires the PHP mbstring extension.
The gallery addon has been updated to use photoswipe version 5.
Performance improvements and bug fixes.
For a complete list of changes in Hubzilla 8.8 please refer to the changelog.
A big THANK YOU! to all contributors and everybody who supports Hubzilla and its development.
#Hubzilla is a powerful platform for creating interconnected websites featuring a decentralized identity, communications, and permissions framework built using common webserver technology.
@Dale Hitchenor looks like the date was set to the time the post arrived at your hub instead of its creation time. I have a vague idea why this happened an think it is already fixed in the development branch...