Danitos

OP asked for opinions, commenter stated their opinion in a respectful way. Why are you trying to shut them up?

I'm very aware of how toxic gaming communities can be, but I don't see how that refutes my point that Pepe is used with non-hate purposes in the gaming community. Furthermore, I wouldn't be surprised at all if 90% of the people aren't aware of Pepe's relationship with far right, neo-nazis and 4-chan. I still wouldn't call them any of these words for liking and sharing the frog with the expressive face.

On the other hand, not wanting to deal with people that post/use Pepe in any sort of way is respectable, albeit seems like a giant social bubble to me.

TW: slurs ahead.

This whole thing remins me of "marica" and "maricón", Spanish words that are used in a few contexts and meanings, the main one bieng "faggot". Recently, tho, they have increased their popularity in the LGBTQ+ community as a self-describing word, in a "fuck you, homophobics" tone. My point is that dismissing these groups as being too far right over using "maricón" would be devoid of context and interest in others. Note as well I'm not claiming all use of "maricón" is respectable and friendly.

Like the swastika, is not the only use it has. In the gaming/Twitch community, it's definitely not massively used as a hate symbol.

Unrelated, but the other day I read that the main computer for core calculation in Fukushima's nuclear plant used to run a very old CPU with 4 cores. All calculations are done in each core, and the result must be exactly the same. If one of them was different, they knew there was a bit flip, and can discard that one calculation for that one core.

The reference adds stuff like the author, journal or year, so it can be a showcase for the relevance, importance, how new is it, etc. I still find it useful in cases like the presentation not being followed by a paper, or you add visual aids that are not present in the paper yet are not your own work.

Disagree on 7 and 8

For 7: References and sources are a must, unless everything is your own work. They should not be put at the end of the slides because the public does not have access to your file, so they cannot go back and forth to properly read the source like they can in a paper. The way I do this is simply putting "Source: blablablabla" in a smaller font, so the reader can easily recognize it as a source and ignore it if they want to.

For 8: This greatly improves the public's ability to ask you questions, as they can just say you "Please go back to slide #X", instead of having to explain the content of the slide.

Keep in mind these are used in my scientific academic background, perhaps outside of it they are not as important.

A report usually contains somewhat useless information, requires more background in the topic and does not allow for easy to ask questions to the author. Slides, written reports, papers, speech, etc. all serve different purporses.

I would like to add a few more tips, based in my experience in an academic background:

5. Don't go back in the presentation to refer to something. If you want to refer to a slide/graphic you already explained, you put the slide/graphic once again, but do not go back several slides.

6. Use big fonts. Text should be clearly readable in any part of the room you are presenting.

7. References and sources should be put as a footnote in each slide, not as a big ass slide at the end of the presentation.

8. Enumerate your slides.

9. Time and flow quality is just as important -or maybe more- than the visual quality. It is a must to stay behind a 10% error margin of the alocated time. So in a 10 minutes presentation, always stay between 9 and 11 minutes (ideally between 9:30 and 10).

Even then, AMD, Intel and now Apple CPU chips are suspected to be backdored. NIST has been slow to adapt a standard post-quantun E2EE algorithm, with some rumours of self-sabotage mandated by NSA (like they have already done in the past). The Tor network is extremely vulnerable to traffic correlation by big parties.

Encryption theoretically gives you what you describe, but in reality you still need to put a lot of thrust in things like your own hardware.

I find this comment funny, given the link I provided was copied from NewPiped.

It is. Check 3:44

There's ways in which a program can detect if it is running in a VM. If Riot made a kernel-level anti-cheat program, they'll surelly also implement this.