vault backup: 2023-08-26 11:35:12

This commit is contained in:
zleyyij
2023-08-26 11:35:12 -06:00
parent 94f099185a
commit 9111c24baf
5 changed files with 0 additions and 15 deletions

View File

@ -1,15 +0,0 @@
TS is currently written in Python, depending on a technically EOL version of the discord.py library. It has grown to a massive scale, and provides all of the functionality that is critical for the server, but has some downsides.
- The codebase is not documented very well, which makes changes to the core system difficult.
- Python suffers from performance issues that have proven be meaningful at the scale of the server (they have been addressed)
- The migration to a new discord.py version is proving to be extremely troublesome
However, sticking with the system we currently definitely offers some pros:
- It functions and is largely bug free, proving stable enough for our use case, with the reliability proving to be mostly dependent on the host.
- Eff is contributing, however the level at which he will end up contributing to the project is uncertain
- Once totally 'cleaned up', sticking with TS may be perfectly acceptable
Rewriting TS offers some pros:
- We can document it as we go and decide on design patterns and practices to stick to before implementation begins
- We evaluate the scale that TS needs to fit, and design according to that
- We can switch to a language that may prove to be more performant/versatile, should we decide discord.py and python are not the best tool for our needs

View File

@ -0,0 +1,29 @@
This post mostly serves as a collection of extremely useful resources that I find convenient to group together
# Homelabbing
For most of these, you'll need a dedicated server. A used optiplex, or Raspberry Pi or alternative is fine.
Ideally, you'd find something from this list that's actually useful to you.
<https://github.com/awesome-selfhosted/awesome-selfhosted>
# Software Development
I specifically enjoyed reading through [this](https://os.phil-opp.com/) series explaining how to write an operating system. You don't need to understand Rust for the theory section of it.
<https://github.com/codecrafters-io/build-your-own-x>
# Learning
These are all various blogs/series that I enjoyed (not fully inclusive) and found very informative:
- ($TAG, $OTHERTAG) - $NAME: $LINK
- (Operating System development, optimizing, reverse engineering, programming) - Asahi Linux Blog: <https://asahilinux.org/blog/>
- (computer design, low level, back to basics) - Ben Eater's 6502 computer series: <https://eater.net/6502>
- (misc, programming) - FasterThanLime's blog series: <https://fasterthanli.me/>
- (reverse engineering, usb protocol, drivers) - LLBP Reverse Engineering a USB Keyboard: <https://www.youtube.com/watch?v=is9wVOKeIjQ>
- (linux, history) - LWN, Birth of Linux: <https://lwn.net/Articles/928581/>
- (misc, programming) - Corecursive podcast (transcripts available): <https://corecursive.com/>
- (graphics APIs) - I want to talk about webGPU (andi): <https://cohost.org/mcc/post/1406157-i-want-to-talk-about-webgpu>
- (programming, design, thinking, code quality) - The Programmer's Stone: <https://www.datapacrat.com/Opinion/Reciprocality/r0/index.html>
- (optimization) - Massively cutting GTA load times: <https://nee.lv/2021/02/28/How-I-cut-GTA-Online-loading-times-by-70/>
- (hacking, security, reverse engineering) - Hacking my car's firmware: <https://programmingwithstyle.com/posts/howihackedmycar/>
- (optimizing, programming, low level) - doom on a raspi pico: <https://kilograham.github.io/rp2040-doom/>
- (optimizing, operating at scale, programming) Discord Engineering Blog (specifically performance, storing messages): <https://discord.com/category/engineering>

View File

@ -0,0 +1,83 @@
# Latest
# New/release features
## Complaints/requested features to address
### Specified
| Assigned to | Task |
|-------------|------|
| Seals | un-jquery it all |
| Drei | finish cleaning up doomscroll |
| Drei | Feedback form |
| arc | Json standardization |
| seals | retain profiles related to feedback |
| drei | add url to the dumps and make them accessible |
| Drei | Sort devices like device manager |
| drei | clarify parts of the ui that are interactive |
| drei | make temps icon actually useful |
| drei | find somewhere to put the debug log |
| Everyone | clean up code |
### Specify
| Assigned to | Task |
|-------------|------|
| nobody in particular | move specify logo during runtime or something |
| bionic | average temps for runtime (5 secs I think?) |
| Seals | figure out the command run for a task (also specified) |
## Not addressed in this release
Viewport
## Docket
- [x] Specify - Decide the next release version
- [x] Specify - Status Text and other possible headaches of switching to another GUI framework
- [x] Specify - Minor GUI redesign
- [x] Specify - Possible optimizations
- [x] Specified - jQuery and the lengths for performance
- [x] Specified - CTRL + F (Gesp mode) - doomscroll
- [x] Specified - Feedback form
- [x] Entire thing - Json standardization
- [x] Specified - Viewport
- [x] Specified - Group device types (from last meeting)
- [x] Specified - Are we deleting dumps?
- [x] Specified - where do we want to put the debug log?
## General notes
- Stop fixing issues/flaws with the json on the specified side
- Document the json format
- Start homogenizing and standardizing/documenting/commenting our codebase to make it more manageable and scaleable. Write code in a vaguely standardized style and flow, and re-evaluate our codebase.
- Don't need a concrete release date right now
- Find an alternative for datatables/jquery - jquery slim?
- gesp is mostly done, by k71 with drei finishing cleaning.
- Basically, open up Device manager. See how it's seperated by device type? Yeah, I would love that - tito on device sorting
- Make it a carbon copy - Use localstorage to remember view?
- Worry about viewport later - Doomscroll might help
- Moving to a new gui framework is a pain
- Updating to dotnet 5 would massively increase filesize, it's not included in any windows version
- Use EOL framework?
- It's probably best to move away from WPF in the long run
- drei found a bug! he's excited. When you toggle a selection in the ui, the hover doesn't work
- figure out a way to show the actual command ran for tasks
- Handle async better
# 1.1
# New/released features
- Specify: Automatic minidump zipping
- Specify: GUI (fairly close to being done, managed by K7i)
### Handled complaints/requested features
- Specified: Doomscroll (k7i) *Wanted by don among others*
- Specified: Improved table view (drei) *wanted by tito*
- Specify: Child process handling convert to total instances and memory usage on c# side ()
- Figure out SVChost parsing
- Specified: label process tables with units
- Specified: clean up routes table (drei)
- Specified: make partitions view contain some useful info
- Specified: make sure extensions work (drei) *see jim for broken test case*
- Specified: convert time as from unix time (drei)
- Specify: Clean up and add to puplist (everyone)
- Specif(ied|y): Figure out A/V view list, list all of them if we can't find the default
## Not addressed in 1.1
- Specified: Download raw json button
- Specified: Group device managers by type
- Specified: *light mode*
- Specify: Add feedback form