UEFI-Editor
citation-file-format
| UEFI-Editor | citation-file-format | |
|---|---|---|
| 4 | 8 | |
| 397 | 426 | |
| - | 1.4% | |
| 7.0 | 6.7 | |
| 26 days ago | about 1 month ago | |
| TypeScript | Python | |
| - | Creative Commons Attribution 4.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
UEFI-Editor
- Fix for High Power Consumption when Intel Arc GPU is Idle
-
Guide about how to check PCI-E Bifurcation support of any mainboard
For all other use cases, here are the couple of steps missing for unlocking a BIOS: https://github.com/BoringBoredom/UEFI-Editor
- Findings Erying i5-12500H ITX B660i. VT-d(iommu) do work
-
RX 580 BIOS mod
I’m not sure exactly what you mean, like do you want to change hidden bios settings? Bios modding can be risky unless you can roll back bios or have multiple bioses or some sort of feature that can help you “unbrick” if your goal is to change hidden settinfs use this method which is known as “grub” it’s much less risky and iirc if you brick with grub the only thing you need to do is clear cmos(Yes i’ve used this method and yes it works) https://github.com/BoringBoredom/IFR-Formatter
citation-file-format
-
Qsv: Efficient CSV CLI Toolkit
I am somewhat tickled at the thought of citing everything in a malicious compliance kind of way. Given a Nix environment, it should be possible to pull down a list of every bit of code that was used to construct the OS. Would we have to differentiate between installed vs executed code? My Latex environment probably has thousands of packages, though I might directly only include a handful of them. Even if I include a Latex package, it might not get executed.
The CITATION.cff format[0] is a newish format to solve the machine identification of citable works, but I suspect it is too new to see widespread adoption. It is going to take some backbreaking regexes to extract "How to Cite" sections embedded in READMEs and buried in the source.
[0] https://citation-file-format.github.io/
-
Beautify your GitHub repo
The standard CITATION format is the Citation File Format, proposed by GitHub:
-
Citation File Format
Ah, I missed the fields that would help you define that info on “definition.reference”. https://github.com/citation-file-format/citation-file-format...
Clearly I’m not the person who built the connector if I missed that :)
-
Hacker News top posts: Aug 21, 2021
Citation File Format\ (28 comments)
What are some alternatives?
arch-linux-installation-guide - An easy to follow Arch Linux installation guide. This guide will show you how to properly install Arch Linux on UEFI/BIOS systems, ext4/btrfs file systems; using systemd-bootloader/GRUB and systemd-networkd/NetworkManager for networking. These are the given examples but I have provided links to sections with the information necessary to install any 86_64 system
ruby-cff - A Ruby library for manipulating CITATION.cff files.
unicode-formatter - Convert portions of text to fancy text using unicode fonts for use on Twitter and other sites that don't support rich text
fugashi - A Cython MeCab wrapper for fast, pythonic Japanese tokenization and morphological analysis.
scripts - A bunch of scripts and configs I use on every machine I set up.
aurora - Malware similarity platform with modularity in mind.
darkmatter-grub2-theme - Dark Matter GRUB Theme 👾💙
schema - Citation Style Language schema
Rufus - The Reliable USB Formatting Utility
pubs - Your bibliography on the command line
rollercoaster-tycoon-randomizer - RollerCoaster Tycoon Randomizer mod for RCT1 and RCT2 inside of OpenRCT2
janet - A dynamic language and bytecode vm