There's no menubar in Chropera.

Here we go, yesterday was an anomaly. These new forum-based comments here aren't as good as My Opera used to be (e.g., they require JS) but at least they work.

Oh, I see. If I enable "show close buttons on each tab", the O/Opera button follows the tab bar around. But close buttons on each tab are just a recipe for disaster if you click in the wrong area. I guess I'd be okay with not showing the MDI buttons as a workaround, which I think was separate option in 11.64. In any case, this turns out to be specifically an Opera 12 regression, although the button itself has been quite annoying since 10.50. They simply managed to make it even worse.

PS If you disable the tab bar, the O/Opera button creates an empty "tab bar" either way.

@andrew84 said in New commenting mechanism on Opera blogs:

notifications (red circle next to username)

Disqus logs you out constantly and always displays a deceptive red circle as soon as it does. It's probably the most noticeable intentional misfeature. By contrast, there's a magical place with an actually functional notification icon. One guess...

@andrew84 said in New commenting mechanism on Opera blogs:

And the fact that Disqus was more popular than forum among users till know (including Opera team) tells me that Disqus was more informative and easier.

It tells you people follow the blog and feel the impulse to comment on the blog. Nothing more and nothing less. That might tell you something about Opera's browser and blog posts, but preciously little about Disqus.

Fyi, the widely disliked Disqus system fails to load again this morning:

Disqus is utterly unusable on mobile. Or it would be if it actually loaded. Most of the time it gets stuck using all your CPU like a malicious bitcoin miner until it craps out.

These days Disqus loads even less than back on its introduction in 2014. Make no mistake, some of us still posted a few comments occasionally in spite of Disqus. It used to be that Disqus was noticeably less dependable than anything else, where anything else basically loaded 99.99 % of the time and Disqus only some 90-95 %, usually fixed by a refresh. In 2019 it's literally down to loading on some days and not loading on others, refresh or not.

In short, the fact that Disqus is terrible is pretty much irrelevant. If Disqus worked I'd dislike it, as I detailed in a rare Disqus comment on the Opera blog back in 2014. On good old My Opera that'd have been quite easy to find; on Disqus it might be borderline impossible.

Either way, Disqus quite simply doesn't work at all anymore, so it needs to be replaced by something that does. Even if that something were somehow worse than Disqus, like the impressively, even caricaturishly awful Facebook comments. As luck would have it, this forum is a lot better than Disqus.

@andrew84 said in New commenting mechanism on Opera blogs:

And the whole versions history with changelogs and other stuff can be moved to the forum.

Not in its current form. There's no relevant newsfeed available afaict, just new comments per category.

@burnout426 said in New commenting mechanism on Opera blogs:

I'd like to have the "view forums thread" link at the top of the user comments section on the blog page too. Currently it's only on the bottom.

+1 Also it should read View forum thread instead.

Originally posted by blackbird71:

Hmm. That may be true in some sense, but in both my Opera 11.52 and 12.14u setups (which I'm looking at even as I type this), the tab bar appears at the bottom of the Opera screen (which is where I want it to be), and the red Opera button is indeed at its far left... as it has for a very long time. However, in 11.52, the button simply contains the half-"O"-logo and lacks the "Opera" text that appears in the 12.14 version.

Well, this is what it looks like for me. It's true in each and every sense.

Put the tabs on bottom and it creates its own empty "tab bar". Disable the tab bar and it does the exact same thing. This button is almost as annoying as the broken addressbar, but keeping the tabs both enabled and on top isn't nearly as annoying as hard-coded text colors that become unreadable if you want to use the "wrong" background color. The addressbar is the worst bug in Opera 11+. The Opera button is the second-worst.

Originally posted by blackbird71:

However, in 11.52, the button simply contains the half-"O"-logo and lacks the "Opera" text that appears in the 12.14 version.

It's a half-O button for me in regular use. I don't know when, how, or why it decides to flip around between one display mode and another.

Opera/Presto has an optional menubar; Opera/Blink unfortunately does not.

Tbh I'd expected the button to be ported as an option to regular Opera if the concept proved successful, not the other way around.

@artexjay said in New commenting mechanism on Opera blogs:

@frenzie Vivaldi Forums comparison to Opera forums is extremely relevant. They use the exact same system!

That comes across as if you're somehow disagreeing with me even though that's my very point?

@andrew84
Is that some kind of rhetorical question? The current blogs + Disqus were purposefully introduced in 2013/2014 in favor of My Opera, presumably mainly for financial reasons. You could call not having to maintain Disqus a technical reason, but that just reduces down to that it costs, e.g., half as much.

I don't understand the argument about splitting things up. That would just make it harder to follow. Please don't ever do that guys.

Regarding the Vivaldi blogs, Vivaldi isn't relevant to the point. You wrote the forum will "never" have a threaded view. Maybe it will, maybe it won't (and you can count this as a vote against), but given a clear NodeBB-based example of threading, chances are it involves little more than some theming.

Regardless if you like or dislike a feature, comparing the comments to other NodeBB implementations is quite relevant to understand what's a choice and what's a technical limitation.

That Disqus marks a lot of innocent stuff as spam was just as true in 2013. It's one of the many reasons I dislike Disqus. Comment a bit too long for its taste? Spam. Which makes it actively hostile as opposed to just annoying. Edited a couple of words/typos? Spam. Included a link? Spam.

I've never seen a web-based threaded format I like, except possibly for (old) Reddit.

@andrew84 No, I don't think it's strange to comment underneath the relevant blog post. Where else?

I don't know what changed from Opera's perspective. However, it should be self-evident that if it's part of your job to reply to user questions, you're not going to refrain from reading or commenting just because it's not your favorite system. Without more information on the matter the reverse hypothesis is no less valid (i.e., that the change was made precisely because those very Opera employees internally clamored for it).

Given a few basic requirements which are likely met by most commenting systems, I'd peg cost and reliability as the most important factors. Possibly also something like privacy as a USP, given that Opera VPN is advertised that way. A system like Disqus doesn't support that principle.

@andrew84 said in New commenting mechanism on Opera blogs:

I knew about it then, but it's something different because all the replied comments in tree are also duplicated beneath in a regular way.

Note that Vivaldi's threaded blog comments are also based on NodeBB.

@andrew84 said in New commenting mechanism on Opera blogs:

notifications (red circle next to username)

Disqus logs you out constantly and always displays a deceptive red circle as soon as it does. It's probably the most noticeable intentional misfeature. By contrast, there's a magical place with an actually functional notification icon. One guess...

@andrew84 said in New commenting mechanism on Opera blogs:

And the fact that Disqus was more popular than forum among users till know (including Opera team) tells me that Disqus was more informative and easier.

It tells you people follow the blog and feel the impulse to comment on the blog. Nothing more and nothing less. That might tell you something about Opera's browser and blog posts, but preciously little about Disqus.

Fyi, the widely disliked Disqus system fails to load again this morning:

Disqus is utterly unusable on mobile. Or it would be if it actually loaded. Most of the time it gets stuck using all your CPU like a malicious bitcoin miner until it craps out.

These days Disqus loads even less than back on its introduction in 2014. Make no mistake, some of us still posted a few comments occasionally in spite of Disqus. It used to be that Disqus was noticeably less dependable than anything else, where anything else basically loaded 99.99 % of the time and Disqus only some 90-95 %, usually fixed by a refresh. In 2019 it's literally down to loading on some days and not loading on others, refresh or not.

In short, the fact that Disqus is terrible is pretty much irrelevant. If Disqus worked I'd dislike it, as I detailed in a rare Disqus comment on the Opera blog back in 2014. On good old My Opera that'd have been quite easy to find; on Disqus it might be borderline impossible.

Either way, Disqus quite simply doesn't work at all anymore, so it needs to be replaced by something that does. Even if that something were somehow worse than Disqus, like the impressively, even caricaturishly awful Facebook comments. As luck would have it, this forum is a lot better than Disqus.

@andrew84 said in New commenting mechanism on Opera blogs:

And the whole versions history with changelogs and other stuff can be moved to the forum.

Not in its current form. There's no relevant newsfeed available afaict, just new comments per category.

@burnout426 said in New commenting mechanism on Opera blogs:

I'd like to have the "view forums thread" link at the top of the user comments section on the blog page too. Currently it's only on the bottom.

+1 Also it should read View forum thread instead.

Here we go, yesterday was an anomaly. These new forum-based comments here aren't as good as My Opera used to be (e.g., they require JS) but at least they work.

@andrew84 said in New commenting mechanism on Opera blogs:

If now all the attention will be focused on forum, what previously prevented Opera to be more active in their own forum instead of Disqus?

That'd have been a duplicate effort.

@andrew84 said in New commenting mechanism on Opera blogs:

Now I see the following situation when I'm forced to choose commenting system between bad (forum) and very bad (new system) for comments in the blog.

This is the first time in years that I've posted a comment on a blog post. I'll leave the rest implied.

Okay, just one teeny tiny thing, unrelated to my thoughts on how Disqus is designed. Half the time Disqus doesn't even load. But of course just when I'm trying to get a screenshot of Disqus saying that "Disqus seems to be taking longer than usual" it's consistently loading in a split second… weird.

Excellent!

I'm not sure if that torrent really graduated past experimental yet. In any case, note that I wrote down a few suggestions on what to do here. For finding all of your own posts, taking the sample Python script as a guide:

#!/usr/bin/env python3

import os

backup_directory = 'backup-data'

check = ['username\n']

for root, dirs, files in os.walk(backup_directory):
    for file in files:
        if file.endswith(".txt"):
            file_path = os.path.join(root, file)

            with open(file_path, 'r') as f:
                content = f.readlines()

            if content[3] in check:
                print(file_path)

Note that even on an SSD that'll take a while.

The DnD Sanctuary is down!

Confirmed. Since yesterday. I'm waiting for news.

Well, technically it's the primary DNS server that's down. I'm not sure if this is really the proper place, but a mod can always delete this post if not. This is a cross-post:

Okay, here's the story of what happened:

The primary DNS server is apparently down:

$ host -a thedndsanctuary.eu ns01.weservit.nl
Trying "thedndsanctuary.eu"
;; connection timed out; no servers could be reached

The secondary DNS server is fine:

$ host -a thedndsanctuary.eu ns02.weservit.eu
Trying "thedndsanctuary.eu"
Using domain server:
Name: ns02.weservit.eu
[snip]

But! Unfortunately there a typo snuck into the DNS record back when we set it up:

$ host -t ns thedndsanctuary.eu
thedndsanctuary.eu name server ns01.weservit.eu.
thedndsanctuary.eu name server ns01.weservit.nl.

It's fixed now:

$ host -t ns thedndsanctuary.eu
thedndsanctuary.eu name server ns01.weservit.nl.
thedndsanctuary.eu name server ns02.weservit.eu.

I apologize for any inconvenience.