no built-in translator needed. Try e.g. https://www.deepl.com/translator
a very good + fast site to translate content. is perfectly sufficient.

new version 68.0.3618.129:
https://get.geo.opera.com/pub/opera_gx/68.0.3618.129/
__
apart from that,
Why are the GX-version info and changelogs not up to date - always?! The last ones are from April! What, Opera, is so incredibly difficult about it, huh?
or differently: you even have difficulties with something like that (comparatively simple)? Is that your way of expressing it? well then...

@amatczak said in New commenting mechanism on Opera blogs:

@aphaltgrau I definitely would not call it "dodging it".

It is an effort to add such feature and we must know if and how this could be useful for anyone, so that we can prioritize this accordingly, since every change takes time. (...)

it was not the question of whether the Opera resources fit - or not.
First of all it is only a question of pure logic. sure you've heard of it?!
And only in one direction it's unlogical and remains nonsense! And even if it's repeated by 3 other mods, that supposedly nobody would need it, it is and remains nonsense - (a bit)!
Whether this is really feasible is another issue. But to implement a function only halfway is, once again: nonsense. What is that supposed to mean?
And why are you wasting so much energy squirming and hiding?!

In the present form, commenting is unnecessarily difficult, impractical, difficult to read, illogically pieced together, etc., pp.
One has the impression that something was knitted with a hot needle. Or with (a bit much) cluelessness - sorry, no offense.
But considering e.g. artexjay's note (5-10, 19:44), if you don't want to stay light years behind, you have to do something. And urgently! Without ifs and buts. And also without distracting and avoiding again and again. Your smoke candles are quite obviously recognizable ...

@amatczak said in New commenting mechanism on Opera blogs:

@aphaltgrau What would be the reason (...)

not to dodge it. What is already stated in last post applies: a "jump-function" only makes sense if it is functional in both directions. Reasons don't matter at all!

_
ps: thanks for the editing period, wasn't known.

since editing option has expired, another post:
Just logged in via account, then the option appears that you can participate in forum. If you click on it, you are in the forum - not (!) logged in. And you have to log in again or rather confirm your login with 4-5 clicks. Not very user-friendly and very impractical.

@artexjay said in New commenting mechanism on Opera blogs:

This comment system is horrendous. (...)

Yes! at least in the currently available form.

@amatczak,
a jump blog-forum works. Back (here, used: firefox 60.9esr) not.
If, then it would make sense in both directions.

actual gx is "GX_63.0.3368.56078", a 64.x doesn't exist:
https://get.geo.opera.com/pub/opera_gx/

mit dem chrome-befehl
opera://settings/content/popups
bzw. chrome://settings/content/popups
dort blockieren/zulassen.

@amatczak, ok. no dates - how awful...
(& andrew84 lists what is missing)

@amatczak, no problem with the disqus-account, d. is a chatterbox anyway, so it doesn't matter. pure info question.

Blog seems a bit more accessible than the forum, at least so far.
Disadvantage now: the comment function (layout options) in the blog is now somewhat badly solved. Therefore less readable than before.
here, too, a "vivaldi-orientation" could be worthwhile:
The link blog-forum exists, the comment function in the blog is still well solved (colors, text highlighting, tree view, screenshot, etc.). This would make it a bit easier to read.