It's your project meant to scratch your itch and what you say goes; don't let other people shoe-horn out-of-scope features into your software that you'll have to maintain once they move on. Keep it lean and mean! :blobfoxdealwithitfingerguns:
If they don't like it, they can fork off :revblobfoxsipsmug:
Amolith (amolith@nixnet.social)'s status on Sunday, 23-Jan-2022 14:47:22 UTC
AmolithSomething to keep in mind when opening bug reports is that you are *usually* not helping the developer or providing any kind of service to them. In most cases, you're actually asking them to take time away from whatever else they're working on to specifically focus on your issue.
They do so out of the goodness of their hearts and for the love of their software.
They are not beholden to you nor do they owe you anything.
Demanding fixes/alterations or being rude to the maintainer(s) or TYPING IN CAPS TO CONVEY ANGER does nothing but make you a public ass.
I need some recommendations for incredibly high-quality and durable backpacks; the one I have now has been in almost continuous use for 15 years and I need to find a new one because it’s on its last legs :comfy:
Price isn’t too much of an issue but I’ll set a soft cap at $200 :comfythumbsup:
Amolith (amolith@nixnet.social)'s status on Saturday, 25-Dec-2021 20:19:29 UTC
AmolithI've always been told it's better to write comments describing the *why* rather than the *what*. This was for a couple of reasons but the primary one was that if you can't understand what the code does by reading it, you shouldn't be messing with it. That makes perfect sense to me.
However, Jon Calhoun from the Go Time podcast recently interviewed a (nearly) blind developer, Dominic St-Pierre, who had a very interesting take on this. He said that describing the *what* actually makes code more accessible; it saves those using screen readers from having to sit through a whole code block to figure out what could have been described in a comment in just a few words.
Those of us without any vision impairment can skim through and understand a whole page of code in just a few minutes while it might take half an hour with a screen reader.
Good comments can save a ton of time :flan_thumbs:
I would love to recommend a self-hosted mail setup that's Not Docker™, but at the moment, the best option I've found is taking a day to follow the ISPmail set of guides. https://workaround.org/ispmail
Unfortunately, most people don't want to invest that much time and effort in a self-hosted mail server so they just stick with Gmail or worse … Outlook :akko_sad:
I'm also going to set up a #Gemini counterpart later this evening or tomorrow, so geminauts — if that's the right term :flan_think: — are welcome to go ahead and open a ticket and I'll check them once it's ready :comfyaww: https://git.sr.ht/~sfr/cassini
This has become my public/announcement account for things related to NixNet, blog posts, streams, and so on. I'm moving pretty much everything else over to my Misskey account: @amolith@mk.nixnet.socialMisskey is *fantastic* software and I really encourage you to take a look at it :cyannyan_heart: https://github.com/misskey-dev/misskey