Qt.io webservices

@jukka It works :) Thank you very much.

Haha, now I'm experiencing the lags too. @tekojo said: Yes, we seem to have issues with the infra. It is being worked on, and we really hope to get it solved soon. It all comes down to traffic increasing steadily all the time, and we need to keep up with that. It's a good problem to have, I guess :)

Hi, I might be wrong but it could be a markdown issue. The only workaround I found is to use spaces and tell people to remove them when they copy the code around.

Yes, the words are unfortunately not standard. The latest nodebb themes seem to hide the favourite tab to the topic menu, which makes sense. But we could still change the voting buttons to thumbs up and down or something more sensible. Also hints on mouse-over would definitely make sense. I'll ask when someone here can hack our theme to include those changes.

@koahnig Past tense. I've already been helped, but thanks for the offer. The reply was for anyone else in the same situation.

Hi, just did another Test on another PC with a fresh installed opera and everything works fine. So it looks like a problem of my opera installation, not a problem of the forum software. Thanks gerd

@TOMATO_QT You pretty much have the answer to your question there. SO does not help one bit in keeping a community together. Also fragmenting the services does not help in that (Q&A in SO, other things here), and people would probably still cross post to both (or shout for a Q&A area here). I don't see having multiple Q&A forums an issue (there's Qt centre, Qtforum, Qt apps, Qt developpez, Qtfr, and other local sites too). The thing we try to do here, is to be a place where the community can come together, talk and ask questions among other things.

@tekojo I guess most will not see the bug, because it is not obvious with a long list of posts. I had noticed only because there where only two and I incidently decided to check them out. BTW this is on Chrome on Win 10.

@SGaist I could be missing something, but if we can run some JavaScript on the top of the old forum pages, this is a solved problem. or at least temporarily until we come with something better.

It does open in a separate window for me. Anyway, most half decent browsers would preserve the form data if you hit back. At least Chrome does.

Strange… I've updated it for you

@xargs1 actually neither. We had a server malfunctioning on the weekend, it was crashing at regular intervals. And as we are running a clustered setup for the forum, every time the server went down traffic from that node went to the other nodes, and that looks like an update (taken offline, and brought back somewhere else) to the forum software. Sometimes the load balancer does the same trick and you get the message if you keep a window open long enough. But the message is completely harmless.

@JKSH As indicated above I have use other search engines to find what I am looking for. It escapes me why you would want to abandon something that is working, for something that is practically useless. I hope you resove this problem quickly.

Nice thank you !

Sounds strange. This site relies on websockets, so maybe something there interfering?

@tekojo Fix confirmed. All seems to work now :)

I'll take a look, but honestly I haven't even looked at individual thread view counts. If there is an option, I'll take a look and see what can be done. But I'm guessing that there is no good solution, as it is practically impossible to differentiate what is a new view or reload (logged in users should be identifiable, but visitors are pretty much anonymous)