Wedge

Yeah, I know it's long.. ;)
I'll pretend to ignore the blaaatant name dropping at the end. :niark:

Technically, it's only the default 'test' homepage, my plan is to offer a dedicated admin settings page where you'll be able to choose what portions you'd like to show in the homepage. (It's already largely implemented in the Home.php file, I just need to add the proper settings, really..! And do something about that translatable intro... :lol:)

It's been implemented in various ways in other systems. Basically, really, it's a nested tweet system. Some seem to prefer shoutboxes, though. It's a different philosophy.

The thought system was originally spawned from 'user texts', you know, the customizable text below your avatar in topic pages. I implemented an input box on the noisen.com header to quickly set it. Then I figured, why not allow people to comment on them..? So I did just that. Made it into its own table, added a hierarchy, etc... In the end, it's grown to something more; a mini-forum, if you will, where the character limit is set at an arbitrary 255 char limit. (Could be more, really...)

That one's SMF, really!

It's quite different from the SMF admin layout, but there are many things I'd still like to move around. I don't have the same opinions as Arantor in this area, and he was in charge of redoing the admin area (his personal hobby?), so when he left, I felt that I owed him nothing in this respect, and that I could go back to something I liked better. The first thing I did was to move several items to the generic settings area. Then I rewrote an obscure and complicated double save function for settings into a unique save function, suddenly allowing me (and anyone) to do anything they want, anywhere, rather than "depending on whether this or that is in this file..." Anyway!

One could say I could go further and add proper Facebook Connect out of the box. Years ago, Pete and I removed OpenID support because we (well, mostly Pete) felt it was only half-baked, and was to be replaced with a better system. He never got around to implementing it, though, and it's really not my priority. But if I had to do a bridge with another IDing system, it'd be Google I think, and then Facebook. Google Credentials is doable, although I've rarely seen in use on other websites. Also, I'd like to change the way external-based signups are considered 'lower citizens' on a forum. There's no reason for this to happen, IMHO. But I take security seriously, so... "Postponed until I have more take to look into it."
In the meantime, if you want OpenID support, you'll have to use ElkArte. (Certainly not bad software; I'd recommend that you try it out.)

Yeah, and that only took, like, a couple of days to implement. And competitors will probably end up adding it, too, and in five minutes only. See, browsers are now catching up and offering a CSS property that does the same. If you look into my code history, you'll see that I actually added that CSS property, and am falling back to my original code (the one that took a couple of days to perfect) if it's not supported (i.e. pretty much everything at the current time.)

Another thing I'm proud of, is infinite scrolling. Only the most recent competitors have it, such as Discourse. As far as I know, no PHP-based competitor has it. This is because it's horribly hard to implement. It's okay if you have static elements to show, but we're talking about user posts that can contain JavaScript (e.g. embeds, etc.), and it forces one to rewrite a LOT of things to make them behave. A nightmare, I'll tell you...

Okay, I'm really, really concerned about that.

On Wedge.org, I currently see a slowdown about every two minutes, because that's when my Github plugin takes action, and I have yet to implement an Ajax version of it that will not slow down my pages. However, that plugin is ONLY active on admin logons, that is to say only I will see these slowdowns.

Now, for the last couple of weeks my server has been a bit inefficient, but I have a feeling that it's improving to normal levels, at least for the last couple of days, so I'm not seeing much of a performance problem.
On my local Windows install, I'm seeing zero slowdowns.

However:
- You pointed out you're having slowdowns,
- Xarcell pointed out (on Github) that he's having slowdowns compared to ElkArte.

Considering that ElkArte does a reasonable job at being faster than SMF (they're also concatenating and minifying CSS, and JS IIRC, although not gzipping it in advance), it's fair to say that they're competing against Wedge rather than SMF when it comes to performance. However, I've been extremely anal about performance in Wedge. Really. It's one of my obsessions. I'm very happy with it, I've managed to save a lot of time on backend page generation (about 30% time improvements overall compared to a few months ago), and frontend pages are extremely fast to load (as little HTML as possible, inline images, scripts all loaded at the end of the page on session starts, etc.), so to me it's a bit baffling that both Xarcell and you are seeing slowdowns, either comparing to ElkArte or MyBB.

To me, the only software that feels really faster than Wedge is FluxBB. They'll always keep the speed crown because they have so few features built-in. It's easier to load quickly, when you're not executing anything... :^^;:

I'd like more feedback on speed, really. Positive or negative. Or maybe unit tests. Some way to find out what's slowing it down for you. Where the bottlenecks are.

Never seen that happen...

Quote

| Happens a lot with the random home icon that does nothing that I can see, only the text is clickable

Random home icon..? (??)

Some will mostly talk in quick one-liners that may not be very welcoming, but nothing bad AFAIK...

Quote from Bunstonious on February 3rd, 2014, 12:43 AM

The importer works well, has a few quirks tho.

8/10 would recommend.

Thanks, which version was your MyBB @Bunstonious ? I haven't used MyBB for a while, maybe they changed their database layout meanwhile..

I was thinking that YouTube worked regardless of whether you were in HTTP or HTTPS.