pepecyb@hub.hubzilla.hu@hub.hubzilla.hu
yani@smarteditor.io@Der Pepe (Hubzilla) ⁂ haven't processed the issues fully. There's a billing system for use of the various APIs. Code is under a most restrictive agreement... needs a following before we care a lot about that, but yes most of it will be open sauce and any code that it useful can be stripped out for Hubzilla. We didn't touch Hubzilla, it's all interface layers.
If the question is "can we use this in our own sites" then absolutely. If we are going to draw a line on that isn't decided or defined.
You can ask to see code in Laozi and make comments on it for review. There should not be a means exposed to edit code directly.
If the question is "can we use this in our own sites" then absolutely. If we are going to draw a line on that isn't decided or defined.
You can ask to see code in Laozi and make comments on it for review. There should not be a means exposed to edit code directly.
sh@fed.hayfidelity.de
It does by nature need to end in an Open Software license. That's part of the general ethical commitments. We are changing code too fast to engage on code ATM.
What I can say on code is that most atoms trigger code of about 30-40 lines that is fairly isolated. So hand tuning improvements doesn't require understanding the code base.
We have a concept of "spooning" code as opposed to "furking it".
It's in a design state with part of the code done waiting for an interface. You need to be into the story more before that will be your next.
I can’t and won’t criticise the fact that quite a few things don’t work (yet?)… I realise that this is a project still in development. Unfortunately, the interface isn’t particularly intuitive either (at least not until you know what it’s actually supposed to be).
Is it some sort of “feasibility study”?
So is the aim to determine whether Hubzilla can be run “headless”, so to speak, and to offer a completely standalone UI for it?
The Solidified theme is currently demonstrating convincingly that this is possible. And with Rust, it also seems to be possible… and why not? The main problem with such a UI, which operates completely independently of Hubzilla’s own interface, is that virtually all functions have to be completely rebuilt from scratch. And that also applies to the add-ons. These, too, would have to be recreated. External add-ons would, of course, no longer be usable, unless there were a suitable interface allowing developers to build their own version for the new UI.
Or is this a feasibility study to find out whether an interface can be ‘vibecoded’ from scratch? Well, that also seems possible (at least in terms of what Smarteditor can do now, and what it cannot yet do). The question of whether it’s desirable to create software that has been virtually entirely generated by AI (“It’s over a year’s work, and I haven’t touched a line of code. Not one.”) is one everyone must answer for themselves. For me, it isn’t. But that’s my personal view, and it applies both to creating the software and to using it (which is why I’ll only use this account and channel until my curiosity is satisfied, and then I’ll delete them).
In any case, I’m not quite making sense of the whole thing yet, especially as the site doesn’t really seem to offer any practical benefit at the moment.
BTW: I’ve now managed to log in… and I’m at a loss. I’ve no idea what I’m actually supposed to do with an account. What’s the point? What are you supposed to do with the interface? What’s it for?