Properly support listening on Unix socket + using a non-`/` router path about authelia

[james-d-elliott]

https://github.com/authelia/authelia/discussions/categories/pre-release-feedback

[fghzxm]

Hey, you could've at least pointed me to #6460 and told me it's already in master :)

…

________________________________ From: James Elliott ***@***.***> Sent: Friday, February 16, 2024 2:30:04 AM To: authelia/authelia ***@***.***> Cc: fghzxm ***@***.***>; Author ***@***.***> Subject: Re: [authelia/authelia] Properly support listening on Unix socket + using a non-`/` router path (Issue #6689) https://github.com/authelia/authelia/discussions/categories/pre-release-feedback — Reply to this email directly, view it on GitHub<#6689 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH3NPEWGMJCNT5FKXE45M4DYTZH2ZAVCNFSM6AAAAABDKCSB2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWHA4DGMRUG4>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[james-d-elliott]

We have an official feedback process for the beta which has been clearly communicated in every location we've invited users to join in the beta. It's quite disappointing that some users can't follow these instructions when we put all this effort into involving the community in this process.

It's especially disappointing and discouraging when a user then is able to find what they think they're looking for with a simple search and make a snide comment about it, or when they quite clearly know they're reporting a bug but avoid doing so open a FR instead to avoid providing minimal helpful information.

We want users to report issues but in a way that's actually constructive, helpful, and time efficient. You may want to consider all of this carefully in future interactions with the community, I hope you do at least.

[fghzxm]

Hi James, I'm very sorry for upsetting you. I've been using beta versions of Authelia for a while, but I didn't join the Matrix channel or the Discord server, so I was quite out of touch with the wider community. Previously whenever I had a difficulty configuring Authelia, I was able to find the answer by searching GitHub issues, and I didn't know that beta feedback is reported using a different GitHub feature (discussion) from that used by release and master feedback. I'll remember to first get in touch on Matrix the next time I provide feedback. As for my previous comment, I'm terribly sorry if it came off as rude to you. English is not my first language, and I'm not the best communicator even in my native language. I've had incidents where I spoke something in English in what I presumed to be an informal tone and ended up being perceived as offensive. I'll remember to err on the side of being formal the next time I talk to the community. I hope I can repair my relationship with the community and clean up any misunderstandings. Fred

…

________________________________ From: James Elliott ***@***.***> Sent: Friday, February 16, 2024 8:56:06 AM To: authelia/authelia ***@***.***> Cc: fghzxm ***@***.***>; Author ***@***.***> Subject: Re: [authelia/authelia] Properly support listening on Unix socket + using a non-`/` router path (Issue #6689) We have an official feedback process for the beta which has been clearly communicated in every location we've invited users to join in the beta. It's quite disappointing that some users can't follow these instructions when we put all this effort into involving the community in this process. It's especially disappointing and discouraging when a user then is able to find what they think they're looking for with a simple search and make a snide comment about it, or when they quite clearly know they're reporting a bug but avoid doing so open a FR instead to avoid providing minimal helpful information. We want users to report issues but in a way that's actually constructive, helpful, and time efficient. You may want to consider all of this carefully in future interactions with the community, I hope you do at least. — Reply to this email directly, view it on GitHub<#6689 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH3NPESG2YNZXBGT5FKF7QLYT2VCNAVCNFSM6AAAAABDKCSB2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBXGU3TOMZRGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[james-d-elliott]

There are additional avenues for feedback. I linked one of them (which also includes all of the important information including warnings about the storage database, breaking changes, etc), and all advertisements of the beta include a link to the feedback discussion forum and alternative ways to provide feedback.

[james-d-elliott]

Regarding tone that makes sense the way you explain it. No worries about repairing with the community, I was just a bit irritated and I don't hold grudges. My issue was mainly that a few people seem to have not read or not following the feedback instructions even though each avenue of advertisement lists it. It also appeared like you were avoiding giving bug report information using a feature request but that could just be a misunderstanding. No hard feelings and hope I didn't come over rude either.

The feedback forum I linked is also appropriate. for discussing the beta