Post AUIwG8a50pvcQR7GZE by polyna@toot.community
 (DIR) More posts by polyna@toot.community
 (DIR) Post #AUIwG7lk1zf7uJZ46a by kde@floss.social
       2023-04-04T09:12:40Z
       
       1 likes, 2 repeats
       
       Say hello to KDE Discuss!https://discuss.kde.org/A new discussion service from KDE for everybody who makes and uses KDE software.#KDEDiscuss is a place for questions, requests, suggestions, banter, and in general interacting closely with the people actively involved in KDE, as well as with fellow users.#KDEDiscuss is also a great way of getting up-to-date news about your favorite apps, new KDE products, environments and frameworks directly from those who create them.
       
 (DIR) Post #AUIwG8a50pvcQR7GZE by polyna@toot.community
       2023-04-04T09:21:17Z
       
       0 likes, 0 repeats
       
       @kde Ugh, what a downgrade. The previous forum worked well, meanwhile this Discourse garbage requires tons of JS to work and serves extremely crippled version of the webpage without it. Has anybody even wanted this?
       
 (DIR) Post #AUIwG9EqZGXQSsBp6u by justinz@social.opendesktop.org
       2023-04-04T09:43:21Z
       
       0 likes, 0 repeats
       
       @polyna @kde 🤦‍♂️
       
 (DIR) Post #AUIwG9piMC1qJDRGZk by kde@floss.social
       2023-04-04T09:13:50Z
       
       0 likes, 0 repeats
       
       (Note that the contents of the https://forum.kde.org/ is still available, but is now read-only.)
       
 (DIR) Post #AUIzM9Elmjco3phqgC by Tionisla@troet.cafe
       2023-04-04T10:18:04Z
       
       0 likes, 0 repeats
       
       @justinz @polyna @kde"Unfortunately, your browser is unsupported. Please switch to a supported browser to view rich content, log in and reply." *sigh* This is on Falkon... a kde browser project
       
 (DIR) Post #AUIzU1MQx9iTwv2rNQ by justinz@social.opendesktop.org
       2023-04-04T10:19:31Z
       
       0 likes, 0 repeats
       
       @Tionisla @polyna @kde indeed. Because QtWebEngine I believe is based on a very old Chromium. Angelfish does the same sadly. With the Qt6 upgrades I believe this will be fixed.
       
 (DIR) Post #AUIzflBculdXGDaVbU by Tionisla@troet.cafe
       2023-04-04T10:21:37Z
       
       0 likes, 0 repeats
       
       @justinz @polyna @kde just sayin' 🤷‍♀️
       
 (DIR) Post #AUIzwGmBEVizrpYe6i by justinz@social.opendesktop.org
       2023-04-04T10:24:38Z
       
       0 likes, 0 repeats
       
       @Tionisla @polyna @kde I'm in agreement with you. It's a big problem. However there are other browsers out there that work including Firefox which is open source as well.
       
 (DIR) Post #AUJ0BdlQ30N7VRWzjM by Tionisla@troet.cafe
       2023-04-04T10:27:23Z
       
       0 likes, 0 repeats
       
       @justinz @polyna @kde I know and I agree but this opens up the question about a native up to date QT Browser...
       
 (DIR) Post #AUJ0CZ373tOTApFQiu by justinz@social.opendesktop.org
       2023-04-04T10:27:35Z
       
       0 likes, 0 repeats
       
       @Tionisla @polyna @kde there is a workaround on the client side https://forum.manjaro.org/t/new-version-of-discourse-dropped-support-for-qtwebengine-5-15-lts/132543 and it does mention potentially patching the server side to remove the check. I may test it tonight or tomorrow to see if the server side change will work.
       
 (DIR) Post #AUJ52iLe8KMQtA2Ugi by Tionisla@troet.cafe
       2023-04-04T11:21:48Z
       
       0 likes, 0 repeats
       
       @justinz @polyna @kde I'll see to the client side, when I'm back from work
       
 (DIR) Post #AUJUZWz5tzQA3TEfaa by Tionisla@troet.cafe
       2023-04-04T15:59:27Z
       
       0 likes, 1 repeats
       
       @justinz @polyna @kde ok, just got back and got it working thanks to Justin🙂 As workaround for all who want to visit discuss.kde.org with KDE's Falkon Browser:Get into the Preferences for Falkon (ctrl+shift+,) -> Extensions. -> Choose "Adblock" then click on "Settings" button below the list of extensions.-> "Custom Rules" Tab-> Options -> Add Rules Enter: "||discuss-cdn.kde.org/brotli_asset/browser-detect-*.js"and next time you visit the discuss.kde page the message is gone. ymmv, tho