BEST DISCLAIMER NOTICE

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.

Couldn't remember my password that I have been using several times a day for the past year. I even used it today, but could not consciously remember the code.

So I am going to post it here so I can look it up if I need to: 12345

Notice: This is a private message only to be shared with the intended recipient. You must disavow any knowledge. When asked about this message you will spontaneously squawk like a duck. You have been thoroughly disclaimed.

Don't products have disclaimers that say where they shouldn't be used? Are people just not reading these?

So I've just about finished a simple application practice project, it's just a program that will show you today's horoscope for different signs from an RSS feed, but I'm wondering if or how I should include disclaimers/credits for things like fonts (The two fonts I use are both open source.), and/or things like the tools used for building it (Written with Python and Tkinter in Atom.)? Do I add it under a "Help" menu or something?

What are the rules and etiquette? And is there anything specific I should include in a separate file? This is also kind of my first proper project.

So I've sent emails to a couple of people (some of which I found on devRant) that were offering work. Typed a small story about myself and why I'd love to take the work.

No reply whatsoever.

Like, I get it if you don't want me, completely understand that, but how hard is it to let me know that.
Like c'mon guys, don't be a dick.

Disclaimers: I got the email address right, they did not land in my spam or whatever since I did receive an email from them in an earlier part of the correspondence. I did give them (what is in my opinion) a reasonable time to respond. They also didn't die or something since they are still active here...

There's a moment when you're looking at a reStructuredText parser, you have a basic idea of the spec, and you know with absolute certainty it's not parsing it correctly. It gets the basics right, sure. But now you know why the tools that use it have disclaimers like "Any para lists or other directives must be at the end of the string". And you're thinking "how hard would it *really* be to write one?". After all, I'm now extracting all the docstrings from the code... Is it really that much more? Shit...