New commenting mechanism on Opera blogs
-
andrew84 last edited by andrew84
@frenzie said in New commenting mechanism on Opera blogs:
Where else?
On forum.
I meant it in overall, why the blog (that has bad/unsecure Disqus system) was used by Opera previously to track/announce versions (with detailed changelogs), not forum. In the blog there could be just major version releases related posts with key features descriptions in this case.
@frenzie said in New commenting mechanism on Opera blogs:that Vivaldi's threaded blog comments are also based on NodeBB
I don't use Vivaldi (yet) so I don't use their forums/blog too. If there is the same system (there is a tree at least) then this is not great too. But why should I compare other browsers's blogs. I can say that Vivaldi is more stable in general (less crashes) and has less limitations (search engines for example) and much more customizable. But Vivaldi lacks some default features that I use daily in Opera.
My main complain about the Disqus is that sometimes it automatically marks common messages like a spam (it's really frustrating) -
frenzie last edited by frenzie
@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.
-
A Former User last edited by
@frenzie said in New commenting mechanism on Opera blogs:
Disqus marks a lot of innocent stuff as spam
That's exactly what I don't like about Disqus. I've encountered this several times.
-
A Former User last edited by
@leocg And that makes even more sense to implement the blogs into the forums as opposed to having them separate especially since the current implementation is very lacking.
So there is one destination for forums as well as seeing what's new with Opera. Right now it's a mess. -
A Former User last edited by A Former User
@andrew84 I can confirm that Vivaldi's blog uses the exact same system that Opera uses. Only difference is that they have implemented their blogs within the forums for seamless and one destination experience.
As for Disqus it's quite secure, there is so far little to no evidence to show that it is less secure than the system that Opera uses for their forums. Not to mention that Disqus is far more convenient on every level at least for me. Never had the spam false positive. Might mean you used a type of wording that is used often by spammers .
-
A Former User last edited by A Former User
@frenzie Vivaldi Forums comparison to Opera forums is extremely relevant. They use the exact same system! Only difference Vivaldi's implementation is actually good and thought out. While Opera's is more half-done or rushed in my view... Which isn't surprising actually.
And it seems that some Opera people can't seem to handle the comparison to Vivaldi or other browsers for that matter which is interesting, especially those that are well-founded.
-
amatczak Opera last edited by amatczak
@artexjay said in New commenting mechanism on Opera blogs:
Only difference is that they have implemented their blogs within the forums for seamless and one destination experience.
Well... no, they didn't. Their blog is using Wordpress (https://vivaldi.com/blog/) and their forums uses NodeBB (https://forum.vivaldi.net/), just like Opera does. They are even on separate domains, as you can see.
-
andrew84 last edited by
@artexjay said in New commenting mechanism on Opera blogs:
Never had the spam false positive. Might mean you used a type of wording that is used often by spammers .
Nope, all my posts were only Opera bugs/suggestions related. Sometimes there were really similar comments that describe the same issue in different build's threads but those weren't simple copy-paste posts.
-
frenzie last edited by
@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?
-
A Former User last edited by A Former User
@amatczak They use different domains but the blog has the forum part as the comment section and it's organized in a tree view similar how Opera's forums does but unlike the Opera blog which is a mess. That is what i meant. For the Vivaldi blog you do not need to go to the forums to edit,delete, see the thread in full tree fashion. While with Opera's implementation you are force to go to the forums.
How come Opera can't do that? Or do they need user input for them to actually say "yea that makes sense" in order to put it in.
-
amatczak Opera last edited by amatczak
@artexjay said in New commenting mechanism on Opera blogs:
For the Vivaldi blog you do not need to go to the forums to edit,delete, see the thread in full tree fashion.
Not true, again. On Vivaldi blogs you still need to go to the forum to edit or delete your comments.
The only thing that is correct in your statement is that they render comments in tree-like view. It has been said multiple times in this thread already, that it is on our roadmap and will be implemented soon.
At the same time, we want to make it work better than how it is implemented on Vivaldi, where all comments are rendered oldest to newest. Their approach, while simple and easy to implement, forces users to scroll all the way to the bottom of the page to read new comments, and then all the way up again to write a comment.
Contrary to some claims in this thread, we do think about the user experience. The way Vivaldi does it right now is not a good UX from our perspective, so we are working on figuring out a better solution. Much like we have put a lot of effort into streamlining logging into comments section when on blogs (compare it yourself between our version and Vivaldi's).
So, once again, tree-like view WILL be added here, along with at least some other requested minor enhancements.
Have a nice day!
-
andrew84 last edited by leocg
I'd suggest to add links in the blog that will show 'Popular Forum Discussions', like in Vivaldi blog.
-
jojo0587 last edited by
OKAY. May the answers appear under the post they concern and have indentation on the left? This will improve readability.
My proposals for changes in Opera (Google Document).
- There are not enough signs to put all the links here. -
leocg Moderator Volunteer last edited by
@jojo0587 See https://forums.opera.com/post/183976
It's the tree like view mentioned on the post.
-
jojo0587 last edited by
@leocg ok, sorry. I don't read all posts in this topic. True... I read only first post.
My proposals for changes in Opera (Google Document).
- There are not enough signs to put all the links here. -
andrew84 last edited by
What's the different between the new 'Link' icon and the timestamp links (both lead to forum)? I thought the 'Link' icon was made for sharing the blog's post links (like it worked in Disqus when I clicked 'share' and comment's link was auto-saved to clipboard, or like it works in Vivaldi's blog but there I need to use right click on 'permalink' and select 'copy link address')