SWW13
Are you sure this is not just a normal community with the instance name?
For me this post is coming from c/lemmyworld. I’m on another instance and there is no community with the same name, nor was I subscribed to any.
At least in Germany that’s the case.
Every contract is legally binding in Germany, even verbal contracts or in this case price tags (to some degree). Obviously other laws may invalidate them and verbally is hard to prove. For example if you advertise onetime off prices for a week to lure people in the store you have to have a reasonable amount of these items to be available through the week, otherwise people are eligible to get the offer or compensation.
Adding your own sticker would probably be fraud and easy to prove for the store (not matching sticker, no plans to reduce prices, …).
Notifications auf Android nutzen häufig einen Google Service. Damit sind alle Notifications von verschiedenen Apps gebündelt und das Smartphone braucht nur eine aktive Verbindung (spart Strom). Je nach implementierung kommt da nur ein “Es gibt was neues” an und die App fragt dann die eigentliche Notification an.
Das zwingend zu nutzen ist natürlich für eine privacy fokusierte Chat App fraglich, wobei der Signal CEO(?) einige fragliche Meinungen hat. Dafür hat er eine erstklassige Chat App gebaut und großflächig verbreitet.
That’s actually a good thought though. It would prevent (clear text) password leaks from shitty / malicious websites. Having a standard for browsers to salt and hash password would have prevented a lot password leaks. On the other hand it could never be updated and we would most likely be stuck on md4 or something similarly broken.
Some (larger) projects sometimes have a form of mentoring and “good first issue” to get started.
Another good way to get involved is to report any issues you face with open source projects you use (obviously search for similar reports first). This way you can help debug bugs or suggest improvements and get some feedback.
You can do most things by combining simple cmdline tools. E.g. filter out some specific lines from all files in a directory, get the value after the second :, write those to another file and then sort, deduplicate and count them.
This may sound complicated, but it’s pretty easy and fast if your are familiar with a shell. To be that efficient with your shell you want it to actually be powerful and not just a plain text input. Also writing cmdline tools is rather easy compared to a usable GUI tool.
As someone who had a mildly unpleasant interaction with kernel folks, I can totally understand the issue.
This is one of the very few open source projects I had the feeling they don’t appreciate new contributers. There is no on boarding material available and picking the wrong subproject mailing list results in being ignored. You have to spend days without any possibility of help and if your are lucky you get mentioned as a reporter. For the next issue you start from square one as there was no guidance, so you could only learn the bare minimum.
So yeah, his patch may be underwhelming. But the help and credit he got for days or weeks of unpaid work was basically nothing. You may be okay with spending days and only getting credits for the bug report, but I suspect many aren’t and will not contribute again after such an experience. And post like this try to point out the issue they have and why many people won’t contribute to the kernel ever again.
I didn’t meant to defend the patch and I see your point. But I personally think that it’s not unreasonable to expect to land a bugfix commit after spending multiple days debugging a complex issue, that’s why understand that he feels robbed of a kernel contribution.
I don’t know what could have been a good solution for this scenario. But taking potential future contributors feelings more serious would help to keep them around and make them feel appreciated.