Timeline for Preventing unauthorized automated access to the network
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2024 at 22:28 | comment | added | Slate StaffMod | @dan1st I hope so, too! | |
| Sep 26, 2024 at 21:33 | comment | added | dan1st | Thank you for being transparent. I hope that your logging doesn't miss significant cases of user scripts/similar applications and that you are able to minimize false positives as much as possible (even though I still think it would be preferable to not restrict pages that don'tneed to be restricted). | |
| Sep 26, 2024 at 20:36 | comment | added | Slate StaffMod | Small update here. Based on the data we're seeing from the logging mode we're currently running, we actually suspect there should be very few (if any) new false positive detections of community tools / scripts. So for now I'll say that this approach is definitely still an option, but it's likely to be something we consider as a fallback, rather than something we implement at the start. | |
| Sep 23, 2024 at 21:44 | history | edited | Ryan M | CC BY-SA 4.0 | Fix a typo (correctly -> correct) |
| Sep 23, 2024 at 14:56 | comment | added | Slate StaffMod | I raised this as a possibility internally. We're optimistic that this idea could work, and agree that would alleviate a number of community pain points around this change. We do need to do some technical/trade exploration before we can commit to it, so don't take this as a firm "yes" - yet. | |
| Sep 23, 2024 at 10:30 | history | edited | dan1st | CC BY-SA 4.0 | added 20 characters in body |
| Sep 23, 2024 at 10:25 | history | edited | dan1st | CC BY-SA 4.0 | added 20 characters in body |
| Sep 23, 2024 at 8:54 | history | answered | dan1st | CC BY-SA 4.0 |