Hacker News Reader

candied_scarfon Debian Running on Rust Coreutils

they end up here https://github.com/casey/janus/tree/master/fetch

candied_scarfon Debian Running on Rust Coreutils

i wont use this because the author sucks up all justfiles files with no way for a user to opt out and isnt fully clear on this. use it on some private or company thing that accidentally goes public, oops he has your file now in his repo.

if it was opt-in to him monitoring i might be more open. maybe i should fork and change the filename to keep this from happening

candied_scarfon Rust 1.50

except it needs someone very experienced with rust and compilers to fix which isnt me. even then if its ignored now whats to say a pr wont be too

candied_scarfon Flameshot – Superb Screenshot Tool

look at older releases. as mentioned the newest is missing for some reason.

candied_scarfon Flameshot – Superb Screenshot Tool

do they know windows bins are missing from the newest release?

candied_scarfon Rust 1.50

im still waiting for fixes for https://github.com/rust-lang/rust/issues/40552 and https://github.com/rust-lang/rust/issues/75263 in one of these releases

lots of upvotes for them too since its for privacy in the compiler

candied_scarfon GitHub discussions further gamify the platform

in my example they devalue them by hiding reported bugs

candied_scarfon An OpenBSD Email Server Using OpenSMTPD, Dovecot, Rspamd, and RainLoop

the issue is they are very arbitrary in what they accept. an example: a couple articles i updated to add commands for new os, not changing content other than command blocks (to be clear they allow this and have a submission form for updates or new os for exist articles), were rejected due to "grammar and spelling mistakes". i also had gotten "your commands do not work" despite in some cases them being slightly tweaked, if not the same, to already posted articles. in any case the original articles were still posted and not even getting updates. i took my edits or new articles and gave them to multiple others who found no issues from proofread or running the command. this made me stop even trying to contribute to them, so i image the same will be true of others. making the comp to DO a tough sell.

candied_scarfon Rust 1.49.0

i am disappoint there isnt mention of more private/reproducible release binary output from compilation

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

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

candied_scarfon OpenBSD devs imply they don't have to follow their own policies

I don't think the change really helped much.

What if the maintainer didn't submit them simply because they just don't want to, this is deliberate with no technical reason this shouldn't be shared, still contradicting the first sentence. At that point I don't think its impolite anymore that someone else does the work with or without their permission. It was the maintainer's choice to leave the work to another person or team to upstream, in turn increasing their own burden to deal with cleaning up or adding patches later.

If OpenBSD doesn't want to be a good FOSS citizen they should state as much and not try to hide behind word games. Nor should they throw stones calling questions or discussion rude when other statements by their own team are worse, yet they seem exempt from their own guidelines, etc.