Hey, my SO and I really loved Severance and watch it in my Jellyfin server, which I set up so they can connect from anywhere. I'll add season 2 the moment it launches. I would be happy to give you acess to it if you want to, just let me know.
Danitos
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:
-
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.
-
Use big fonts. Text should be clearly readable in any part of the room you are presenting.
-
References and sources should be put as a footnote in each slide, not as a big ass slide at the end of the presentation.
-
Enumerate your slides.
-
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).
I find this comment funny, given the link I provided was copied from NewPiped.
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.
Dota 2 is similar to LoL, has a native Linux build and runs perfectly fine out of the box. Perhaps you can give it a shot.
You can use Flatseat to config the permissions (including files) that Flatpaks have. It has a nice GUI