You are not logged in.
Pages: 1
in reference to https://bbs.archlinux.org/viewtopic.php?id=315167
tried to open linked bug from my phone via mobile, android, chrome, no extensions: 403
tried via wget from my home pc: works
asked google: seems the kde bug tracker is quite restrictive - but also blocking regular mobile internet? anyone knows anything?
Offline
Worked with firefox mobile, but not from lightning (an android webview based browser), 403.
Faced that since long time.
Last edited by kokoko3k (2026-10-13 17:04:32)
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Yeah, same on LOS 22 w/ Brave Nightly; I get a 403.
in termux I normally get a 200:
~ $ curl -sS -o /dev/null -w 'HTTP %{http_code}\n'
https://bugs.kde.org/
HTTP 200But setting a browser User-Agent makes it return 403. Even a desktop Firefox UA gets a 403 through curl. IG it's evaluating more than just UAs, lol.
I feel sad for Keith. What happens if he gets chased by a Python? Poor guy, he is just an obese, diseased rat with a missing hind leg that was blown off... I hope those zero-cost abstractions help him run faster and escape in such scenarios. :cry:
Offline
Maybe an extreme antispam measure...
Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !
Offline
Same here, vivialdi w/ chromium UA
Works w/ wget.
Should be a new development, I'm pretty sure I saw a KDE bug last month.
I guess that's another way to be bug free - they could also just make the account creation more cumbersome…
Online
Worked for Arch. ![]()
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1