Here are some file kinds / types that I like, and ones I have some dirt on.

Was always intrigued by these files. Used for describing contents of archives and folders.

• FILE_ID.DIZ FILE_ID.DIZ
• .NFO .nfo (See also Kodi's weird version, which contains XML)
• README, READ.ME, README.* README

Google Chrome extensions. The 'shop' doesn't let you just download them, so the only working solution I found was using the Chrome Extension Downloader website to grab them.

• https://developer.chrome.com/extensions/crx
• https://www.cnet.com/how-to/how-to-install-chrome-extensions-manually/
• https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Porting_a_Google_Chrome_extension
  • https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Temporary_Installation_in_Firefox

Desktop files are used to organise programs in the window manager's applications menu and/or launcher (in my case Rofi). They're basically the Linux equivalent of Windows' shortcuts.

Software should provide one, but if you need t ocreate your own, or customise one you can put them in ~/.local/share/applications.

I have an example one in my /Templates directory that looks like this:

[Desktop Entry]
Type=Application
Version=1.0
Name=Template
GenericName=Desktop template
Comment=
Path=/path/to/software/
Exec=executable.x86
Icon=/path/to/icon.ico
Terminal=false
MimeType=
Categories=Game;Utility;

There some notes on making ones for stuff you run through Wine on its page.

• Categories from the Freedesktop spec:
  • Main Categories
  • Additional Categories
  • Reserved Categories

File for standardising preferences across text editors, things such as tab length, character format. Also handy for formatting on Github ;)

• editorconfig.org
• Why you should be using an EditorConfig file in your project
• Why I use EditorConfig

see §.gitignore in the page for Git.

Firefox still lets you add your own style rules, though I kinda suspect they'll ditch it one day :(

It lives at ~/.mozilla/[profile name]/chrome/userContent.css, though you might have to manually create the chrome directory, and the .css file yourself.

Mostly I use it to hide results from shit websites in DuckDuckGo searches, for example:

@-moz-document domain(duckduckgo.com) {

	/*	Hide reults from particular domains	*/
	.result[data-domain="gamesradar.com"], /* anti-adblocker */
	.result[data-domain="www.w3schools.com"], /* shifty, low quality */
	.result[data-domain="slant.co"], /* low quality */
	.result[data-domain="www.gamesradar.com"] /* anti-adblocker */
	{
		display:none;
	}

}

Otherwise I'm just blocking a few pesky ads., and making basic, Web1.0-like pages a bit easier t oread with different colours and line heights.

see §Styling in the Firefox page.