honestly feels like a joke but it's the reality aha.

\> It's not like it would be super complex to build one of all sad words, of tongue and pen, the saddest are these: we're gonna build a chat forum again

lol

FluxBB isn't even that bad, aside from Arch Forums, I run my own instance at but its just soooo dated at this point and does not get security or PHP updates so I cannot recommend it anymore.

its basically on deaths door, even for the arch folks

Also my main concern about mattermost, as brought up in the other channel, is that it's just so thicc that once it's abandonware, you're gonna be screwed even faster than FluxBB. Both FluxBB and PHPBB's main saving grace is its so minimalist that it doesn't take so much effort to upgrade it.

Could be wrong but I've been around long enough to see most community systems/packages come alive then die.

so, given that, should we bring our own online and then let it die?

this actually brings up a topic I am interested in: very long lived software

the long now type software

i hope htmx falls into that category

if its engineered with the same mantra as htmx, using htmx, I could forsee that having an extended life

Yeah, totally

there's just so little to go wrong or go out of date with htmx.

imo its just all about engineering stuff directly on standards and minimalism, keep the surface area of things that can go out of date non-existant.

this might russle some butts, but its what concerns me about engineering anything expected to stay in place for a long period on react or typescript. They just aren't made to stick around, and they just take over the code of a project.

So the whole thing goes down with the ship

unless you have a very active maintainer on it for the rest of their lives, ready to rework the entire thing.

I'm going to be offline for most of the day, but I couldn't let this thread go by without jumping in to say "hi." I agree with all of what you've said here. It seems like we're always re-building the wheel because someone else did it "not quite right." This goes double for chat and project management software. We saw a mini-version of this in the #929014829212123156 forum, where different people have slightly different requirements, and wildly different solutions. I think the "long lived" answer to this fundamental problem is to make a solid (but flexible) foundation of reusable components, along with sensible defaults, then let designers customize their own versions in a low-code environment. That's what I'm working on with whisperverse. Features (like form controls, db interactions, content relationships, etc) are all bundled into workflow steps, then those steps can be recombined in many ways via hot-reloadable JSON config files. I'm very close to having a working demo (even got a couple pull requests from the community here) but the startup experience is still really rough. I would love to work on this kind of a project with you all. I'll work to make a functional startup wizard, and will let you know when it won't be too painful to jump in and kick the tires. 🙂

am monitoring your progress with eagerness. Would actually be a gamechanger for community software to just have the deployment simplicity of Go - would be mindblowing to get a forum by just running a single binary.

Right now the bare minimum is like... nginx, mysql, php-fpm aha.

not super sold on the "Inline everything, including CSS and JavaScript", given HTTP/2 pipelining

https://www.youtube.com/c/PaulDavids Why do you have this guy's picture? 🙂

question on SSE-events - when using this code:

html
<div hx-ext="sse" sse-connect="/events/">
    <h1 sse-swap="msg1" 
        hx-get="cancel" 
        hx-swap="innerHTML" 
        class="text-success"></h1>
    <h1 see-swap="msg2" 
        hx-get="cancel" 
        hx-swap="innerHTML" 
        class="text-danger"></h1>
</div>

when sending events in the channel

msg1

this works as expected. But it does not work if I use

msg2

. I thought I could just use this as a selector for messages and warnings/errors.

when using it this way:

html
<div hx-ext="sse" sse-connect="/events/">
    <h1 sse-swap="msg2" 
        hx-get="cancel" 
        hx-swap="innerHTML" 
        class="text-danger"></h1>
    <h1 see-swap="msg1" 
        hx-get="cancel" 
        hx-swap="innerHTML" 
        class="text-success"></h1>
</div>

only the error messages (=msg2) work as expected. Can there only be one element ever be addressed in a sse-connect?

Is that a direct copy & paste? Because:

<h1 see-swap="msg1"

see-swap != sse-swap 🙂

We've all been there 🙂

is there already a syntax highlighting plugin for htmx / visual stutio code

seems so 🙂