4) According to the idea of @Mike Macgirvin (Mike Macgirvin), Hubzilla should be an extension of the Zap project, which has undergone (is undergoing) a modernization metamorphosis. In my opinion, this is the only way that can ensure real success. And I am very interested in the success of Hubzilla
...Polish translation, I first decided to translate...
...enthusiasm was gone...
As of today, there are 266 open issues in the framagit.org/hubzilla/core repository and 32 in the framagit.org/hubzilla/addons repository
I shouldn't even respond but in the interests of accuracy, no - I do not believe that (#4) at all. Otherwise I'll refer you the project LICENSE for warranty and refund information
Now we've come full circle and returned to our roots with the launch of Mistpark 2020 (aka 'Misty'). This incorporates newer protocols and a wealth of experience we've picked up along this fascinating journey, while remaining true to our original principles.
As far as which one to use, that's up to you. Zap is the root of this tree and development starts there. Redmatrix is Zot-only by default. All the others are fully integrated into the ActivityPub side of the fediverse and a bit like "Debian stable" in the sense that they usually don't get updated until we're comfortable with the latest changes in Zap or there's a security patch. Then these are pushed out. Roadhouse is the start of something new and different, but development will probably be a wee bit slower going forward. I'm retired now and fixing the planet and saving lives is a priority over fixing social media and listening to people whinge and attack me 24/7/365 for doing something I once enjoyed and sharing it with the world
For me, the answer is important because I have become involved in this work.
Another thing that is important to understand is that of those 200+ open issues, only a few represent actual "actionable" issues and for many of the others, we couldn't actually find a problem and need more information or they represent different expectations
Anyway I'm mostly suggesting that yes, we all know the code has to be updated.
I can't commit since registration on framagit is closed, but I can review.
Warning: Framagit currently suffers from a spam problem: many accounts are created to expose links to dubious sites: online games, escort sites, etc.Gitlab does not currently allow us to fight effectively against this abuse once the damage has been done, which is why we have decided to set up a moderation of new accounts until further notice.Newly created accounts will only be active once they have been authorised by our moderation team (which will take between 1 and 5 days).
since the service will be discontinued
Hi Scott, do you have any hints to give me ? I'd like to start playing around with Hubzilla code too. If you have any links, tips or advice I'd be happy to hear it. Thanks.
Kind of a pity that #Streams is such a grass-roots and word-of-mouth project that seems to fear publicity.
they just need some UI/UX developers to polish it up, and need extensive documentation. It is a diamond in the rough.The lack of a diverse set of developers is a real issue
So why are developers not finding their way to the project an join?
Nowadays, everyone uses #i3wm, nobody even touches a pointing device anymore, and the only graphical application they still use is a Web browser, if anything. For everything else they use the command line. They don't know GUIs anymore because they don't get to look at GUIs anymore, so they can't develop GUIs anymore, and they don't see any sense in GUIs because they themselves don't use them anyway.
Regarding the mobile app, there's more to say about it: It has to be named the same as the network, it ideally has to be made "by the same people" who also run the network, and it has to be readily available where people get their apps from.
Mike commenting about Streams: "The current name of this repository implies fluidity. As a brand or product it technically does not exist. This is also intentional. The software provides general web communications infrastructure. It's your website. Your site is your brand. Not ours."
Let's face it, under the current conditions, we remain the underdogs with our charming software.
I think privacy should be important for all users. But there should be an option to choose. Here you have that option too, but it is hard to find often and the defaults are build with closed information in mind.
But yes: UI could be better, although I personally love many things in that UI surprisingly.. And I don't think it is not sexy (if you choose all black ^^). But I am a nerd so that does not count that much..
I have to have a closer look at @Scott M. Stolz M. Stolz's Neuhub theme.
My goal with these themes is to streamline and modernize the interface.
let's start with Documentation!What can be done for a better Documentation? @mike @Mario Vavti
If I understood Scott M. Stolz correctly he is already starting on some kind of wiki or something?When I decide to start developing stuff for Hubzilla I would do topic 1 automatically more or less, as I am used to do something like that in all of my projects (for pure egoism, I don't like to answer the same question again and again, so it is nice to have something to point at. )
As part of a Hubzilla channel or on a separate website?I mean, it'd be cool if a wider audience could behold a Hubzilla-based wiki in the wild and see that it's possible.
. So I would use Hubzilla as engine for what ever I want to implement but would "fork" my own branding...