upvote

points

by database641286 hours ago |
comments
upvoteby Barbing6 hours ago|
next
[-]
>enough friction that none of us did so far.

Emailed per https://news.ycombinator.com/item?id=50450200

Definitely still a bug right? Linked them to your parent comment.

Edit: oops sorry team, think you're on it (4d ago): https://github.com/whyredfire/wireguard-apple/commit/0bac142...

Guess it can serve as feedback on the friction when issues can't simply be opened though!

reply
upvoteby database641286 hours ago|
parent|
[-]
> Definitely still a bug right? Linked them to your parent comment.

Thanks! Yes, it is still a bug.

> Edit: oops sorry team, think you're on it (4d ago)

I don't think @zx2c4 has seen this PR, and the author of the PR has not sent a bug report yet, so it's probably fine :P

reply
upvoteby traceroute664 hours ago|
parent|
next
[-]
> Thanks! Yes, it is still a bug.

Its unfortunate no updates for Wireguard macOS have been pushed out for 3 years, App Store is still showing 1.0.16 as the latest version – as also confirmed on the Wireguard website at the latest version.

No doubt macOS APIs have moved on a lot in 3 years and so perhaps bugs that are being seen are simply a reflection of the lack of updates to keep up with API changes ? Just thinking aloud here, I don't know if the concept of OS API changes are applicable to this particular PR / bug.

reply
upvoteby Barbing5 hours ago|
parent|
prev|
[-]
All right! :)
reply
upvoteby encom5 hours ago|
prev|
[-]
>friction

I appreciate when both options exist, because I've passed on reporting so many bugs, because I refuse to create a Microsoft account to do it.

In fact, I don't understand how sending an email is high friction.

reply
upvoteby database641284 hours ago|
parent|
[-]
> I've passed on reporting so many bugs, because I refuse to create a Microsoft account to do it.

99% of the time it's perfectly fine to just email the maintainer with a bug report and maybe a patch.

> In fact, I don't understand how sending an email is high friction.

Judging from the fact that after so many years, such a widespread (as seen in the Reddit post and here) issue still hasn't resulted in a single bug report in the mailing list, I'd say most people (including myself) do indeed consider using a mailing list to be higher friction.

If I'm not mistaken, unless you're already CC'ed by a participant, you'd have to subscribe to the whole mailing list just to receive notifications for a single thread. For an "issue" on a Git forge, participation is usually as easy as upvoting and then clicking the "Subscribe" button.

reply
upvoteby encom4 hours ago|
parent|
[-]
Assuming you're already using MS Github. Anyway, even if I was, a lot of Github project require filling out an absurd Simon Says form. Or that scene from Indiana Jones where he takes a wrong step and falls through the floor. That's nothing to do with email or Microsoft specifically, it's just another reason I almost never bother reporting bugs. Talk about friction.
reply
upvoteby database641283 hours ago|
parent|
[-]
Yeah, I hate these forms (issue templates) too. Every time I have to fill such a form, I always feel that they are discouraging me from writing the bug description in a natural, coherent way. I'd spend more effort to make sure the description is clear and contains all necessary information, if there's no issue template requirements.
reply
upvoteby jeremyjh1 hours ago|
parent|
[-]
Yes, but most people won't. Most people will submit a bug report with important information missing that means we have to go back and forth. Also, there is often specific debugging information that people would not even know would be useful.

In the current age, its useful because AI will submit tickets using the CLI that don't use the form, so I can immediately close and lock them and go on living my life.

reply