I just wanted to share a handy feature in Firefox that can be used to create shorthanded keywords. For instance, you could make it so that typing "t ~books" brings you to "https://tildes.net/~books". Or "ts banana" that brings you to Tildes search engine, searching for "banana".
I've been using a similar trick on another browser I use for years (Qutebrowser), but lately I've been using Firefox more and a post on the Ferdiverse reminded me that I could do this in Firefox as well.

Instructions

• In FIrefox, open the Bookmark Manager. (Keyboard shortcut: Ctrl+Shift+O , alt: Burger-menu in the upper right > Bookmarks > Manage Bookmarks)
• Select a folder where you want to save your bookmark
• Go to "Organise > Add Bookmark"
• Enter whatever name you like.
• In the URL textbox, enter the static part of the url you want to use. Replace the part that can change (like the page name or the search term with this: "%s"
  • Example for switching communities or go to the frontpage: "https://tildes.net/%s"
  • Example for searching: "https://tildes.net/search?q=%s"
• Optionally, add tags seperated by a comma in the tags textbox.
• At last, choose a keyword. This is the word that replaces the static part of the URL when you use the bookmark. For example, I use "t" for the community-switching and "ts" for searching.
• Save you bookmark and try it out. When you now type just the letter "t" in your URL-bar and press enter, it should bring you to the home page. When you type "t ~books" , it should bring you to the books community page.

You can use this feature with any website, so I encourage you to play around with it :)

Want to contribute a theme to Tildes but don't know where to start? Let's fix that.

Before we start, get yourself a development environment setup and do a quick read through of the general development info to get acquainted with how Tildes works (or at least the HTML and CSS section).

For this walkthrough I'll be using tildexample as the example name for the theme, but if you decide to contribute a theme for real, make sure it uses the proper name of your theme. :P

Step 1: Sassy _Sass

Open the Tildes codebase using your text editor of choice and navigate to the themes directory at tildes/scss/themes. Then create a copy of _default.scss at _tildexample.scss. The default White theme is the canonical source of all colors used, so it's the best place to start from.

Below is an annotated example of all the things you need to change in your new theme file.

// Add a small description of the theme here with maybe a link to its website.
// Check the other themes for examples. https://example.org/tildexample

// Change the theme variable to $theme-tildexample
// ↓ ↓ ↓ ↓ ↓ ↓ 
$default-theme: (
  // A whole bunch of color definitions, edit as your theme demands.
  // ...
);

// Append ".theme-tildexample" to the body selector.
// ↓ ↙
body {
  // Don't forget to update the theme variable here too.
  //                  ↓ ↓ ↓ ↓ ↓ ↓ ↓
  @include use-theme($default-theme);
}

@include theme-preview-block(
  // Change the text to tildexample.
  // ↓ ↓
  "white",
  // And again update the theme variable here.
  //       ↓ ↓ ↓ ↓ ↓ ↓ ↓
  map-get($default-theme, "foreground-primary"),
  map-get($default-theme, "background-primary")
  //       ↑ ↑ ↑ ↑ ↑ ↑ ↑
);

Once that's done, head to tildes/scss/styles.scss and at the bottom of the file add your theme import:

@import "themes/tildexample";

Step 2: Hardcoding a TheMe coLor

Boy that title is a stretch just to say, we need to add 2 lines to the HTML base template.

Inside the tildes/tildes/templates/base.jinja2 file is a section of if/elif/elif/elif/... statements to set the theme color meta element. Add yourself an elif block and add your theme color.

For this you probably want to use the background-primary color you used in your theme definition. I've used #ff00dd below because it spells food. I'm such a jokester.

{% elif request.current_theme == "tildexample" %}
<meta name="theme-color" content="#ff00dd">
{% endif %}

Step 3: Snakey Wakey

Finally the last step is to grab your trusty pungi and give it a blow.

Head to tildes/tildes/views/settings.py and find the THEME_OPTIONS constant. Here you want to add the theme class you used in body.theme-<this part> and a proper name that will be shown in the theme dropdown.

THEME_OPTIONS = {
    "white": "White",
    # Many other themes...
    "tildexample": "Tildes Theme Example",
}

Once that's all been done, check it out in your development site and see if it works.

Now git!

Commit. Push. Merge request. Have some water. Deimos reviews, merges and deploys your theme. Job's done.

Context: Last year I struggled for a long, long time to make my new Xbox Elite Series 2 gamepad work properly with Steam. After more than a day of frustration and following various trails of other discussions on the topic, I finally figured out the exact series of actions needed to solve the issue. I posted these steps on Reddit, and they ended up getting me dozens of comments and messages, even as recently as yesterday people still let me know that I saved them from the same frustration. With reddit in its current state of uncertainty, I'd hate for this guide to be lost, so I'm hoping new readers and controller fanatics will find it useful here.

The Problem: You have a Xbox Elite Series 2 Controller, which you are trying to use in Steam on Windows. When using the default (no profile lights) profile mode, the paddles are detected and can be mapped in Steam Controller config. However, they still register no input in-game when pressed. Here is how to fix your problem:

The Solution:

Step 1: You must first revert the firmware of the controller to version 4.8.1908.0. On a PC with your controller plugged in, open the Xbox Accessories app (from the Windows Store), then hit Windows + R to open the Run dialog. Run this command:

xboxaccessories:\firmwareupdate?legacyDowngrade=true

This should give you option to revert. Do it.

Step 2: In Steam Big Picture, go to Gear Icon -> Controller Settings and Enable Xbox Extended Feature Support if it isn't already checked. After enabling it you will have to Reboot. If it's already enabled, there is no need to reboot.

Step 3: Back to the desktop, make sure the Xbox Accessories app is CLOSED. If it is open, you must close it, then disconnect the controller entirely, then power it off, and then finally reconnect it to the computer.

Step 4: Press the central profile button on the controller a few times until it cycles through the profiles. You need to cycle it until the profile light turns off, indicating the controller is in its default layout.

Step 5: Open Steam's controller configuration for your game of choice, and you should now be able to re-map the paddles therein.

Every time I have done the above process, the paddles on the default profile (with no lights on) are now mappable in Steam and usable in-game. I have completed this successfully now with five total controllers, and all worked with Steam flawlessly afterward.

Notes & Clarifications:

• You do not have to uninstall the Xbox Accessories app. However, if ever you use it to modify the controller at all, you must repeat step 3. If you try to use the steam-remapped paddles in the game with the app open, they won't work. You have to turn off the app, disconnect and power cycle the controller, and then reconnect, and very specifically do not re-open the accessories app. I'm assuming this is because the Accessories app inserts some kind of override layer that only goes away after removing the controller and closing the app.
• This process will almost certainly make the Bluetooth connection wonky, if it even works at all. Instead, you'll want to use either a direct cable connection and/or the official wireless adapter. In fact, all of the above steps worked for me with the wireless adapter connection just as well as with the wired connection. As a bonus, you can seamlessly transition between wired and wireless mode this way by simply plugging or unplugging the cable.
• At least as of May 2023, I've received now multiple reports saying that newer purchases of the Elite 2 controller are being shipped with the controller now pre-flashed with a default firmware that is newer than the one that was available in the above post. As a result, this means that rolling back the firmware might not work, as it can't be rolled back to version 4.8.1908.0 anymore. However, I have since purchased two more new controllers of my own since then, and neither had this issue, and in fact both worked with Steam immediately out of the box (after telling Xbox app "no!" to firmware upgrades, that is).

I hope I have posted this correctly (it's my first post here!), and that others continue to find it useful.