candied_scarf

discussions gamify github like contribution graph. there are no counts for discussions like issues/prs so authors can hide issues by moving them.

see for example: https://github.com/isoron/uhabits

anything that isnt specific a crash is moved to discussions so it can be ignore. anyone see similar in other repos?

doing this keeps issues low by hiding them so stars etc can be high. then author says they have only a few issues open for the project, and users see the same so think its probably good

Saw the following on GitHub and Reddit and was curious.

https://github.com/rust-lang/rust/issues/40552

https://github.com/rust-lang/rust/issues/75263

None of the workarounds noted work for me, paths and usernames still make it into the binary when using release mode. Its only medium priority for them so likely to not be officially fixed anytime soon so trying to find a solution in the interim.

CI is fine for the user, but not everyone has access or uses CI. Even then if I compile the code my user is different so hashes will be different meaning it only solved part of the issue.

recently i came across a large project that is interesting and i want to use. the project name specifically likely doesnt matter and may change the discussion so keeping it vague. but i realized all the way up their chain they cannot follow their own policies documented on their site. though any one trying to contribute is criticized for every small detail including having the policies rubbed in their face.

the project is a bit too big and complex for me to just fork and do my own thing.

what do you all do in these cases? use the project or no? and if so do you try and somehow discuss or point out the policies to others when its appropriate and in a diplomatic way?