Dears,
A teammate (@raphaeld) posted multiple times about features (but also limitations) of the Openstack setup underlying the OVH offer (some of these limitations affecting our organization).
- ... about instance downgrading
- ... about CORS, object storage and private container
- ... about boot volume detaching
All posts were being technically sound, professionally written (and actually insightful).
Nonetheless this user's profile was disabled without prior notice, all posts hidden and provided no way to contacts forum administrators (which mostly sound inactive by the way)
Given the time it takes to write good post/bug-reports and their use of other OVH customer (aka _community members_), this looks totally unacceptable.
We would like to request the reactivation of the account and the restoration of the posts.
On the contrary we'd appreciate a public answer from OVH about community management practices.
Thank you
General Chat - Constructive community members censoring
Related questions
- API keys WebGUI
22060
10.11.2023 11:25
- OVH Manager exceptionally slow
20467
19.04.2018 11:11
- How to completely close your OVH Account
20313
05.07.2019 14:26
- I cannot complete registration
19089
10.01.2022 13:34
- Hubic issues downloading files and backup archives
16047
17.04.2018 11:12
- Remove / Change API Token
15545
27.10.2022 14:36
- DMARC record, available or not?
15019
18.07.2018 09:10
- [Beta] Experience the New OVHcloud Control Panel!
14611
05.02.2026 13:18
- Plesk server update error - Help
14108
20.07.2020 08:11
- Oops! An error has occurred creating the account
12695
01.04.2020 17:59