I haven't been able to connect via telnet for a couple of days. It might be me, but I figure I should say something...
So how do we make it easy for the common woman/man in the street to
hit F*c*b**k over the head and bury it once and for all?
Two of my son's friends have volunteered to accompany me on a trip to California to assault Mark *uckerberg with a baseball bat until F*c*book ceases to exist.
Sun May 13 2018 11:35:41 PM EDT from IGnatius T Foobar @ UncensoredTwo of my son's friends have volunteered to accompany me on a trip to California to assault Mark *uckerberg with a baseball bat until F*c*book ceases to exist.
That is where I begin to worry, should we call the police now or wait until you get half way across the country?
https://en.wikipedia.org/wiki/Movim
I am on: https://nl.movim.eu username mikeao
https://nl.movim.eu/?contact/mikeao%40movim.eu
Please have a look, and say hi. (after evaluating, lots of FOSS social networking systems, and just finding - and falling in love with movim (as much as i found and fell in love with citadel-- and still am <3 <3 !! ) i would highly recommend you guys sign up here, even just for a brief look, and to say hi to mo/mikeao :) .
One feeling i have after using movim for a little while now, is: What a lovely User Interface! :P
It is so simple, well laid out/intuitive and there is no difference using it on a wide laptop screen or a small smartphone.
This is one thing that would 'make' citadel, and especially having the side menu similar to movim, simplified and useable on a mobile/smartphone.
I know the new webcit will be mobile friendly, so will fix the current problems hopefully, is there any news anyone can share about the new citadel UI?
I would love to see a simplified set of icons, as well as a mobile friendly/mobile client UI and especially side menu (if you will keep this layout?
I am *not* a fan of throwing away a working code base and starting over, but WebCit is such a horrible mess of spaghetti that it can barely be maintained anymore.
Ah...
Yeah, I'd thought one might want to rethink webcit in the way you've described.
Sounds pretty good, just... I guess... needs a UI.
It's a pretty obvious change when you think about how web software is done now. It still bugs me to have to "start over" in a sense, but when the WebCit project was started in 1996 I really didn't know what I was doing. It was a couple of CGI scripts clumsily lashed to a server process that talked to Citadel, and presenting a UI using any weird hack I could manage. The design pattern was wrong, the code was badly laid out, and the built-in web server was bolted on four years later, adding more spaghetti to the code. The templating language seemed like a good idea at the time, and the implementation was pretty powerful, but it made code maintenance almost impossible.
webcit-ng is written very cleanly, with good separation between layers, and avoiding some of the design mistakes made in other parts of the system. For example, we pass all of the state of both the HTTP transaction and the Citadel session up and down the stack instead of constantly querying for thread-specific data. And to be honest, there are places where big chunks of code are being brought over from legacy webcit to webcit-ng, but they're being cleaned up and fitted into the new program instead of trying to fix what was in the old program.
It's a great little project and I'm really happy with what we've built so far. But that's part of what's making it take so long. And of course it doesn't have a UI yet. :)