If everything had worked perfectly, it still would have been a bum airplane." - Charles Wilson, Secretary of Defense

Back in the 1950s and 1960s, the United States attempted to design nuclear powered aircraft. This was part of a larger "nuclear craze" in the era where everything and anything was proposed to have nuclear technology applied to it. This led to all kinds of things like the Chrysler TV-8 and "peaceful" earthmoving construction projects. The only place where nuclear power or propulsion really took off was for large ocean going ships both for military navies as well as civilian tankers, cargo ships and icebreakers. Spacecraft technology was the only other "success story."

Nuclear powered aircraft, while more realistic than say nuclear cars, never quite caught on except for a few experimental engines and just one actual working aircraft. The most extensive efforts towards this during the Aircraft Nuclear Propulsion (ANP) program were the HTRE-2 and HTRE-3 experimental nuclear reactors with heat transfer assemblies designed for nuclear powered aircraft at the Idaho National Laboratory. Rather than burning fuel, the jet turbine would use the heat from the nuclear reaction to heat air sent through a compressor which would then be expelled as exhaust for thrust.

On of the more fascinating tests were the test flights of the NB-36H which while conventionally powered, flew while carrying a working nuclear reactor to test the protective shielding of the crew. It carried an air-cooled 1 megawatt reactor. The engineers and crew worked within a specially shielded nose cabin with 12-inch-thick lead-glass windows.

The project was canceled by the Kennedy administration a few months after taking office in 1961 citing high costs, poor management, and little progress towards a flight ready reactor saying:

At the time of termination, the Aircraft Nuclear Propulsion Program was still in the research and development stage, with primary emphasis on high performance reactors. Although a number of research and development achievements can be credited to this program, at the time of termination an airplane had never been flown on nuclear power nor had a prototype airplane been built. - Joseph Campbell, Comptroller General

and

Nearly 15 years and about $1 billion have been devoted to the attempted development of a nuclear-powered aircraft; but the possibility of achieving a militarily useful aircraft in the foreseeable future is still very remote. - John F. Kennedy, POTUS

Footnote: This post is a rework of a reddit post I made here a couple years back. It's not really meant to be a coherent or lengthy article but has some links and thoughts which I found interesting.

I have a little web app running on Deno Deploy and I want to see how it handles people connecting from multiple regions. There's a BroadcastChannel class that lets you send messages to any servers running in other regions, but to test it, I need to make connections in multiple regions, so there's more than one server running.

What are good ways to test this, either interactively or by writing tests? Maybe use a VPN? What's your favorite?

Recently Lockheed Martin put out a post on social media [1] where they showed a silhouette of a yet-to-be-revealed aircraft. Most people seem to believe it will be the reveal of their entry to the NGAD program [2] (Next Generation Air Dominance).

While not much is publically known one interesting tidbit is how much it looks like the silhouette of the Testor Corp [3] F-19 [4] model that was released back in the mid 80s. Testor said at the time that the model was based on intelligence (aka leaks) of what would eventually become the F-117.

Aviation forums in the past have said F-19 model is what they WANTED the F-117 and it does look quite a bit like the Have Blue [5] test craft they built, however, the legend is that they couldn't get the math to work for radar deflection properly at that time due to lack of computational power and ended up with the geometrically simpler F117 design we got.

[1] Lockheed Martin Teaser: https://theaviationist.com/wp-content/uploads/2023/07/LM-NGAD-story.jpg
[2] NGAD: https://en.wikipedia.org/wiki/Next_Generation_Air_Dominance
[3] Testor F19: https://en.wikipedia.org/wiki/Testor_Corporation#F-19
[4] Testor F19 Image: https://test803.files.wordpress.com/2018/10/img_6712-1.jpg
[5] Have Blue: https://en.wikipedia.org/wiki/Lockheed_Have_Blue

(I'm not looking for simple lists of YouTube channels that you like.) _{even though I'm about to dump a list of channels that I like}

There's a lot of YouTube cooking content. I was wondering what you look for in that content, and what you want to avoid?

I don't have a particularly coherent answer - I like a mix of content.

I do like plain and simple information, or informative content that gives details about technique or science or why a thing is done the way it is. Examples of this would be America's Test Kitchen, or J. Kenji López-Alt or Helen Rennie, or French Cooking Academy.

I also like recipes that I can actually make. I prefer recipes that don't have a massive array of ingredients that I don't have. Examples are Brian Lagerstrom (I like the way he tends to use a limited amount of equipment and he gives alternatives for ingredients if he thinks some thing is going to be hard to get) Not another cooking show has some nice recipes (his grilled cheese and tomato soup is fantastic).

Some channels I watch have Michelin Starred chefs discussing a recipe. I like watching this because I can't replicate most of it, but I can get ideas for improving taste or texture. Italia Squisita has a lot of content, and some of their videos are comparing a traditional Italian recipe (and these are excellent) with an elevated restaurant version. The staff canteen is a bit frustrating - it's almost exactly what I want, but it ends up missing the mark a bit. But they talk to chefs, mostly in the UK, about being a chef or about a dish. La pâte de Dom is self-taught, but they have a high level of skill in pastry.

And here's a list of videos that I can't categorise, and why I like them.

The Biryani Expert (sadly, channel appears not to be making content any more) taught me that biryani covers a quite wide range of different dishes.

Sheldo's Kitchen He seems like a nice bloke, and his food looks really nice and achievable to make. Again, sadly, he doesn't seem to have made any videos for a while, and he was saying that he has a lot on. But he has a calm style and I liked his content.

Cool Daddy, YummyBoy and Street Foods TV expose me to a lot of food that I'm not used to. I can't recreate a lot of it (I don't have a camel I can cut up and cook but it gives me ideas for new ways to combine ingredients or new flavour profiles to try.

So, what do you look for in content?

(In this thread I avoided dunking on creators, because there's a few that I really don't enjoy but I don't think me yelling about them is good discussion. _{But I'd totally join in if someone created another thread}.

YouTube limits ad blocker usage in new test
YouTube could be testing a three-strikes policy for ad blocking (Update)
So its clear now that YouTube is going to limit the usage of Ad blockers in the coming future
I use Ublock Orgin with Firefox which basically used to block all ads and on mobile device I use NewPipe

Hi all. On my Pixel phone I have the accessibility option for font size and display size turned up a notch or two but noticed that not all of the text in Tildes adheres to this. Some front page topic text is bigger, some of them remain small.

Is this something that can be quickly tested and fixed if it's a bug? It might drive poor sighted people away from the site.

I'm assuming it's not me, as my Pixel 7 is quite new .... but I am on the Android beta program.

Can anyone else try and see if it's a localised issue or more global?

I can post screen shots of needed but not sure what image sharing sites you prefer to use in here!

Edit:

Fixed with a chrome flag....

the text-scaling is being replaced by the "Accessibility Page Zoom" feature (currently hidden behind the feature flag in chrome://flags)

Do you love a good trail? Are you a hiker, backpacker, trail runner, or neighborhood saunterer? If so, this conversation is for you! Share your favorite routes, dream trips, the gear you love, where you find inspiration, or essential advice. Got any cool trips planned, in the near or distant future? Whether you’re a newbie or trail-tested veteran, share what you know!

The recent PKM thread had me thinking about what folks are using as journaling app/portal. I do use Obsidian for my second brain right now and genuinely love it. But I find the mobile app on Android to be a bit clunky, if I'm honest. Seems slow to open even with very few plugins. For jounaling I've used DayOne for years. I started back when it was iOS/MacOS only, but then switched phone to Android and haven't been back. But now they have an app and web app for that. What I don't like is the somewhat goofy format it saves in and it's on their servers. They used to allow you to at least leverage your own Dropbox, but no longer.

For the past several months I've tried several FOSS options. Main criteria is that I could host it myself, supports offline entries stored in an open file format (preferably MarkDown), and had either multi platform app or a decent web app. That lead me to try these:

Memos
Pros:

• Great persistent web app
• Slick UI that is light and snappy
• markdown support
  Cons:
• Stuffs the .md inside a database file so can be a bit cumbersome to export data
• No offline support. There is a 3rd party app that hopes to implement it

Flatnotes
Pros:

• Incredibly simple
• Another easily deployed app
• Flat Markdown files
  Cons:
• Web app on mobile is almost unusable as in it doesn't scale well to smaller screens
• Very early development, but very likely to stay as minimalistic as it is now.
• No offline and very unlikely to ever have it

Joplin
Pros:

• Multi platform apps that perform well
• End-to-end encryption supported
• Could replace both DayOne and my To-do solution (Google Keep)
• Offline support
  Cons:
• More database stuff instead of flat markdown files

One solution I've been testing lately is using IAWriter to write to a 'Journal' folder within my Obsidian vault on Google drive Obsidian Vault > Journal > 2023.... for example. This works surprisingly well. Of course IAWriter is a bit spendy at $29 for Android and then more $ for other platforms as they're sold separately.

So I'm curious what other people are using for just simple daily journaling, random thoughts, etc. If there's an approach I've missed I'd love to hear it. Joplin is so dang close but not having the structure of plaintext files is a no go for me as I don't want to be trapped by any one product should something happen to the development down the road. Doesn't have to be free, but I want control of the entries either on my own server or cloud storage.

Tags testing.

Updated: June 29th 2023

Hello folks,

Like many of the other people that have been around lately, I'm new to Tildes, I've been browsing it without an account since last Monday or so while waiting for an email response (thanks @Deimos), and in that time I've been working on a little tool to add some QOL features I thought would make my experiences with the site feel better.

I didn't plan on sharing it initially, because I didn't think I'd be able to get the javascript into a usable state, and I'm not fond of sharing my code in general, as I always get a big wave of impostor syndrome whenever I do, "What if they look at my messy code and see how silly I do some things", that sort of thing. But with Tildes I want to try to correct some of my internet behaviours, for years I've generally stayed as a lurker, never commenting or sharing content of my own, so, hello there, hopefully, I stick to my guns and you see more of me.

Onto the script itself, currently, I've built five main features into it all of them being rather minor on their own, I did do bug testing on everything and couldn't find anything else, but if you notice anything please feel free to report it to me or post an issue on the repo. It's easy to miss bugs when you've only got one set of eyes.

Tildezy Github

The GitHub contains installation instructions if you've never used a userscript before, and contains some images showing off each feature described below.

Hopefully, someone gets some use out of this with me, I look forward to chatting with you all.

EDIT
Refactored the code and added a new comment traveller feature based on some of the comments below.

EDIT 2
Up to 1.3.0, we've got markdown buttons now, see comment explaining the change or check out the github readme

Was a fun little project. I worked on the drinks myself first, then gave them to my roommate for a blind taste test, and asked her to describe the kind of character she thought the drink was about. If she wasn't at least mostly right, then I'd have to try again - but they somehow ended up a lot more accurate than I expected to be, despite the fact that she knows nothing about this D&D game, haha. I guess we're just really on the same wavelength?

Anyway, without further ado, here are the recipes! If there are any other mixologists on here, I'd love to hear what you think - and you want to try (something like) any of these drinks but are missing an ingredient or two, let me know and I'm happy to try to suggest a few possible substitutions.

Avery

• 0.75 oz chartreuse
• 0.5 oz montenegro
• 0.5 oz black walnut liqueur
• 0.5 oz distilled water

Liz

• 0.75 oz peated gin
• 0.75 oz crème de violette
• 10 drops lemon juice
• yuzu bitters

Matoya

• 1 oz mezcal
• 1.5 oz lemon tonic
• cardamom bitters

Morgana

• 1 oz plum gin
• 1 oz white rye
• 1 oz distilled water
• lavender lemon bitters

Sylvaire

• 0.75 oz cognac
• 0.25 oz pomegranate liqueur
• 0.25 oz grand marnier
• 0.75 oz peach juice
• peychaud’s bitters

V

• 0.75 oz peated gin
• 0.25 oz galliano vanilla
• 0.25 oz absinthe
• 1 oz peach juice
• hibiscus rosehip bitters
• cucumber twist (i.e. take a thin lengthwise slice of a baby cucumber and curl around the inside of the glass)

Are you comfortable following most bread baking recipes? Looking to start making your own recipes, and understand what ingredients do at what levels? If yes, this is what I'm going to try and explain the basics of, and point you in the right direction. If no, still feel free to read and ask me to explain anything I did a poor/insufficient job of.

Baker's Percentages

A baker's percentage is calculated by dividing the weight of the ingredient by the total weight of flour, times 100. You might hear it referred to as baker's math, or as a symbol with b%.

For example, if I had 100 grams of flour and 60 grams of water, that would be:

60/100*100 = 60% water, or in bread recipes that's referred to as the hydration. You might have seen on YouTube things like "90% high hydration sourdough!!".

It's important to note that if I had 90 grams of bread flour and 10 grams of whole wheat, that would be 100 total.

Why is this important? Whilst it's not an exact thing, for most breads you can tell a lot by seeing what the baker's percentage of the recipe is. It's also a great way to share those recipes, it's a ratio, so it's easy to scale up or down a batch. I share recipes like this, and it might look as simple as something like:

Flour - 100%
Hydration - 50%
Salt - 2.50%
Lard - 20%
(The flour tortilla recipe I use)

In my experience, I would say that most breads fall in:

50-70% hydration
1.5-3% salt
~3% oil/fats is the optimum for loaf volume without it being very enriched (added fats and sugars), although it's also common for rustic loaves to be lean (no added fats/sugars)

There's not much I can do in terms of the typical range for other ingredients, apart from recommending resources that help to explain what these ingredients do, and give examples using bakers percentages. Michael Suas' "Advanced bread and pastry" explains what all the commonly used ingredients for each section are used for, and gives lots of recipes for different items in both weights and baker's percentages.

Bakerpedia is a great resource for seeing the typical ranges used for various products, as well as offering example recipes in some cases. It's much more geared towards industrial/commercial baking, including the use of functional ingredients (additives), but I find that kind of stuff interesting too.

If you have a lot of money to spend, Modernist Bread by Francisco Migoya and Nathan Myhrvold is definitely interesting, informative, and the photography/graphics are as helpful as they are beautiful.

The main way I learnt is to convert recipes I liked/used into baker's percentages, and start to change them. You can find various ones online, but one thing that really helped me was creating a spreadsheet calculator.

I'm going to walk through how I first made my calculator, and hopefully that will show how all the maths actually works.

Recipe Template

This is the recipe for a lean dough, so I keep the name in the top left. The "weight per" is how much I want each loaf or roll to weigh. I can change the number of them, and it'll change the total weight in the recipe to match that. I input the bakers percentages under "percentage" and the formulae display the total percentage of the recipe, and the weights of each ingredient. I like to centre align calculated cells, and right align cells that I have to change.

Showing the Formulae

So how does this actually calculate the weights? You can see that the "Total" for percentages sum up all the percentages in the recipe, and for weight is multiplies the weight per by the number of. Why? Like I mentioned above, baker's percentages are like a ratio. If I know I want 100 grams of dough, and I want to figure out how much flour I need, I need to figure out how many grams each percentage is worth and multiply it by the percent of that ingredient.

100 / 168.40 = 0.5938 grams
0.5938 * 100 = 59.38 grams

You can see me doing this in one step for each weight, where I divide the total weight by the total percentage and multiply by the column to the left - the percentage for each ingredient.

You can make one of these for all of your recipes, and then you can change the weights or batch size very easily by just changing a number or two. As you start to experiment, you can keep a "main" template with lots of blank spaces to write what ingredients you want.

This is my own personal calculator, where I've added things like pre-ferment calculators, double hydration, offsets for water loss with evaporation, something that calculates the amount of vital wheat gluten depending on what protein I want, and checks/balances for seeing if all my flours add up to 100. I also have a vlookup table underneath that tells me the nutritional information for the ingredients I'm using. I also use cell colouring as a validation tool. You can see a screenshot of it here

I don't want to share this with the idea of you using mine, there are many things I'd change about it if I decided to start over, but hopefully it shows you the flexibility and customisability of making your own calculator.

One thing that this can't do is tell you how long to knead, how long to proof, how long to cook, what temps, et c. The only thing I can recommend for that is continuing to read and do other written recipes, until you get the intuition - although I still look up recipes similar to what I've written to double check things like cooking time!

In terms of how long to bulk/final proof, generally you'll get a feel for things like judging volume (if i'm not doing an open crumb bread, I like to proof in a large 2L jug to measure change in volume). For final proof I like to use the poke test, although you'd expect a poke test on baguette dough to spring back much more than you would on challah. You want more oven spring with baguette than challah, so understanding what the tests mean and reading through resources that explain those things are very useful.

I hope this has made sense, I'm not very experienced with long-form writing and trying to teach a topic like this, but I'm trying to lean into the tildes mindset.

Just a hack job, but I'd seen some comment about it being inconvenient to ignore posts so I made a quick userscript (tested with Tampermonkey on Firefox) that adds hotkeys for bookmarking/ignoring/voting on a post. It can also navigate to the link or comments or prev/next pages (←/→). Only implemented for posts 1-9 at the moment.

Ex:

i+2 ignores and hides the 2nd post (or restores, if ignored)

? shows a summary of hotkeys

// ==UserScript==
// @name         Tildes
// @namespace    http://tampermonkey.net/
// @version      0.1
// @description  Quickie convenience hotkeys for tildes.net
// @author       TT
// @match        *://tildes.net/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=tildes.net
// @grant        none
// @require      https://unpkg.com/hotkeys-js/dist/hotkeys.min.js
// ==/UserScript==
(function () {
    "use strict";
    let Action;
    (function (Action) {
        Action[Action["Invalid"] = 0] = "Invalid";
        Action[Action["Bookmark"] = 1] = "Bookmark";
        Action[Action["Comments"] = 2] = "Comments";
        Action[Action["Ignore"] = 3] = "Ignore";
        Action[Action["Open"] = 4] = "Open";
        Action[Action["Vote"] = 5] = "Vote";
    })(Action || (Action = {}));
    const regex = /tildes\.net(\/~(?<group>\w+))?/gi;
    let match = regex.exec(document.location);
    //In a group if I wanted to support hotkeys there?
    if (match.groups.group) {
        //alert(match.groups.group);
    }
    else {
        addArticleNumbers();
        addMainHotkeys();
    }
    //Route
    function routeAction(action, event, handler) {
        event.preventDefault();
        //Grab index.  Zero-index?
        let indexText = handler.key.substring(2);
        let index = parseInt(indexText) - 1;
        if (isNaN(index))
            return;
        actOnArticle(action, index);
    }
    function actOnArticle(action, index) {
        //Get article for index
        let article = document.querySelector(".topic-listing").children[index].children[0];
        //Do the thing
        switch (action) {
            case Action.Bookmark:
                if (article.style.borderStyle === 'solid')
                    article.style.borderStyle = 'none';
                else
                    article.style.borderStyle = 'solid';
                article.querySelector('button[data-ic-put-to$="bookmark"]').click();
                break;
            case Action.Comments:
                article.querySelector(".topic-info-comments a").click();
                break;
            case Action.Ignore:
                //Hide vs blank?
                if (article.style.visibility === "hidden")
                    article.style.visibility = "visible";
                else
                    article.style.visibility = "hidden";
                // article.style.display = 'none';
                article.querySelector('button[data-ic-put-to$="ignore"]').click();
                break;
            case Action.Open:
                article.querySelector(".topic-title a").click();
                break;
            case Action.Vote:
                article.querySelector(".topic-voting").click();
                break;
        }
    }
    function addArticleNumbers() {
        let titles = Array.from(document.querySelectorAll(".topic-title a"));
        for (let i = 1; i <= titles.length; i++) {
            let title = titles[i - 1];
            title.text = i + " - " + title.text;
        }
    }
    function addMainHotkeys() {
        //Set up handlers
        const handleBookmark = (event, handler) => routeAction(Action.Bookmark, event, handler);
        const handleComments = (event, handler) => routeAction(Action.Comments, event, handler);
        const handleIgnore = (event, handler) => routeAction(Action.Ignore, event, handler);
        const handleOpen = (event, handler) => routeAction(Action.Open, event, handler);
        const handleVote = (event, handler) => routeAction(Action.Vote, event, handler);
        hotkeys("shift+/", (e, h) => alert(getHelpText()));
        //Page nav
        hotkeys("left", (e, h) => Array.from(document.querySelectorAll(".pagination a")).find((e) => e.textContent == "Prev").click());
        hotkeys("right", (e, h) => Array.from(document.querySelectorAll(".pagination a")).find((e) => e.textContent == "Next").click());
        for (let i = 1; i <= 9; i++) {
            hotkeys("b+" + i, handleBookmark);
            hotkeys("c+" + i, handleComments);
            hotkeys("i+" + i, handleIgnore);
            hotkeys("o+" + i, handleOpen);
            hotkeys("v+" + i, handleVote);
        }
    }
    function getHelpText() {
        return `
    ←/→ = navigation
    b = Bookmark, i = Ignore, v = Vote,
    c = Open comments, o = Open link,

    Action+[1-9] calls that action on the corresponding article`;
    }
})();

1. Read Part 107 from the official government website of the Cod Of Federal Regulations This is a very easy to read list of the do's and don't under Part 107. Any study guide that does not tell you to read this is a bad study guide.

2. Read Remote Pilot -- Small Unmanned Aircraft Systems Study Guide - This is an official study guide put out by the FAA. Either save it to your computer/phone or print it off and mark it up as you read. But read this cover to cover and comprehend it. It is 88 pages, but this alone could pretty much get you to pass the Part 107 exam. There isn't a single YouTube video out there that covers all of this.

3. Read the official FAA ruling on "Operations Over People General Overview". This details new requirements for flying over other people. There are 4 categories and this can get a little bit confusing. There is a great dedicated Youtube Video from a small channel run by a gentleman named Tim McKay who explains it all crystal clear.

4. Read the official FAA requirements for Night Operations.  This has changed in the last year.

5. By this point you pretty much know everything you need to. But we want to have a thorough understanding of everything not just basic knowledge so we can "just pass" the test. Fog is a topic that will come up on your test. Make sure you understand the characteristics and causes of each of the 6 major types of fog. A great resource for this is Fly8MA.Com Flight Trainings video.

6. Sectional Charts. You've already read about them in the study guide, but practice these. Try to memorize which lines mean what. But if you forget always remember there is a legend in the front of your supplement book that you will have on test day. Some great tools I used for this were:

   1. Altitude Universities FAA Part 107 Study Guide [How To Read A Sectional Chart]. They teach you almost all of what you need to know, but he also teaches you a great "game" you can use to practice.
   2. Fly8MA.Com Flight Trainings - Video on Advanced Sectional Chart Knowledge. You see a lot of lazy videos out there on "5 Tricky questions about sectional charts on the part 107 test". Well this video will make it so there are no tricky questions!

7. Understand abbreviations for METAR and TAF reports. Weather.GOV has a chart of this. You certainly do not need to memorize every single one of them. But the major ones regarding precipitation, cloud, winds, max, min, began/begin, end, etc. A great way I learned to read these was to install the Avia Weather app on my Android phone and use that for my weather app for a few weeks. It presents weather in METAR format. It forced me to learn to read them. I would see new abbreviations pretty regularly and then look them up and know them. You can also spend some time using the Aviation Weather Center website. It provides METAR reports and you can decode them to verify your answers.

8. Understand air masses, fronts & clouds. This too comes directly from the FAA. It is comically old looking, but the information was incredibly helpful. It is 30 pages with tons of pictures. It helped supplement the knowledge from the official study guide on the 3 phases of every storm cloud. I probably have 4-5 questions on this during my test. If you understand weather you almost don't even need to study much on the effects it has on and aircraft because it all becomes incredibly easy to process.

9. Density Altitude & Pressure Altitude. This is one I see almost never talked about. Sure enough I had a question for this on my part 107 test.

10. Know how to talk on a radio. You will basically never have to do this, but I had two questions on radio procedure come up. One was how to contact ATC for authorization via radio (you never ever do this) the other was how something would be properly announced using phonetic alphabet. This video from Fly With the Guys does a great job of digging deeper into this.

11. Spend the time to understand Aeronautical Decision Making (ADM) The video series I watched was 4 parts. Here is part 1. When I initially read through the study guide this didn't quite click with me, but the videos helped a ton.

12. Understand Weight & Balance basics for aircraft. A guy named Jeffery Bannish has a pretty great video on this. Understand loads during banked flight. I had multiple questions on this on my test as well.

13. Lastly. This one is completely optional. It cost me $15. John Peltier of Peltier Photo Courses has a bank of $300 questions he put together into a test that you can take as many times as you like. It picks 60 random questions so you are not taking the same test over and over. When you buy it you can access the test for 2 months. I probably took his test 10 times over the course of the month I was studying. What I would do is take the test once each day. Then review any questions I got wrong and I would spend time to learn the correct answer. As I would learn the correct answer I would absorb additional information. The next day I would take the test again. Get some new questions and repeat the process. After about 4 days I started routinely getting 94-98% on the practice tests.

I have lost my r/finch community, and am feeling curious to see if there are any folks here who also find apps can be helpful for their mental health.

I struggle with anxiety and am processing a lot of grief, and may or may not have ADHD (I am in the process of getting tested, but it takes a while). My experiences with therapy are a bit mixed, so I am currently going down the route of trying to DIY my wellness a little. Starting simple with things like, sleep more, try to focus on drinking enough, go out in nature, switching off podcasts and phones and reading more. It's actually helped me, bit by bit.

One of my 'tools' is an app called finch, a virtual pet that encourages you to set goals, check in how you are feeling, journal, do mindful breathing and such. I tried many things and this app is the one that stuck and actually works.

Just wanted to ask, do any others here use wellness apps? And have they worked for you? Which do you recommend?

Just to be clear, I mean apps that work as a stand alone solution, rather than apps like 'better help' which ultimately just connect you to a therapist. Although Better Help has its uses too!

I joined Tildes a couple of days ago, and I'm absolutely loving the interface and community.

In the last few days of using Tildes, I noticed a particular problem that was mildly annoying; if you have the "Collapse old comments when I return to a topic" setting on, and you click on a link that is supposed to lead to a comment in a topic you have already visited, it won't jump to that comment.

Searching around, I found a post about it from a day ago, in which long-time users have mentioned that it's been a known problem for a while now. In those comments, someone mentioned permalinks as a solution, but it appears that's still in the works.

For now, I've made a quick userscript that will address this issue (and adds some slight related functionality). It hasn't been thoroughly tested yet, so if any issues occur, please let me know. This userscript is designed to be used with Tampermonkey (a privacy-friendly alternate that should work is ViolentMonkey), which is available in all popular desktop browsers. Installation instructions for Tampermonkey are available on their site (it's installed like any other extension).

To install the script, you can head to this GitHub Gist which contains the code (click "Raw" to open the TamperMonkey install prompt), or you can copy and paste the code from the following dropdown block into a "New script" on the TamperMonkey dashboard. The dropdown is not guaranteed to contain the latest version.

// ==UserScript==
// @name         Tildes Comment Link Fix
// @namespace    https://gist.github.com/blankdvth/6da89fff580e8cf6e50f88847ddb5729
// @version      1.2.0
// @description  Fixes comment links (anchors) not working as a result of Tildes' comment collapsing feature.
// @author       blank_dvth
// @match        https://tildes.net/*
// @icon         https://www.google.com/s2/favicons?sz=64&domain=tildes.net
// @grant        none
// ==/UserScript==

/* 
    USER SETTINGS
    This script is not big enough to warrant a visual settings menu, so adjust settings here.
    true = enable, false = disable
*/
const alwaysRun_S = false; // If enabled, will always run the script, even if the comment was not collapsed (site works fine in this case). This is useful if you want to make use of the other settings.
const smoothScroll_S = false; // If enabled, will smoothly (animated) scroll to the comment. If disabled, will jump to the comment.
const uncollapseIndividual_S = true; // If enabled will uncollapse parent comments into one line instead of fully uncollapsing them.
const uncollapseChildren_S = true; // If enabled, will uncollapse all children of the comment. If disabled, will leave them collapsed.
const collapseIrrelevant_S = true; // The script uncollapses all parents to ensure the comment is visible. This will collapse irrelevant (not direct parent) comments again.
// END OF USER SETTINGS

/**
 * Uncollapses the comment if it is collapsed.
 * @param {HTMLElement} element Article element of the actual comment
 * @param {boolean} individual If true, will "uncollapse" into one line instead of fully uncollapsing
 * @returns {boolean} True if the comment was collapsed, false if it was not
 */
function uncollapse(element, individual = false) {
    if (element.nodeName !== "ARTICLE") return false;
    var removed = false;
    if (
        !individual &&
        element.classList.contains("is-comment-collapsed-individual")
    ) {
        element.classList.remove("is-comment-collapsed-individual");
        removed = true;
    }
    if (element.classList.contains("is-comment-collapsed")) {
        if (individual)
            element.classList.add("is-comment-collapsed-individual");
        element.classList.remove("is-comment-collapsed");
        removed = true;
    }
    return removed;
}

/**
 * Uncollapses all direct parents of the comment.
 * @param {HTMLElement} element Article element of the actual comment
 * @param {boolean} collapseIrrelevant If true, will collapse irrelevant comments again
 * @param {boolean} individual If true, will "uncollapse" into one line instead of fully uncollapsing
 * @returns {boolean} True if any parent was collapsed, false if none were
 */
function uncollapseParents(element, collapseIrrelevant, individual) {
    const relevant = []; // List of relevant elements (direct parents)
    var wasCollapsed = false; // Whether any parent was collapsed
    while (
        element.parentElement &&
        element.parentElement.nodeName !== "SECTION"
    ) {
        element = element.parentElement;
        relevant.push(element); // Add parent to relevant list
        if (uncollapse(element, individual)) wasCollapsed = true;
        // Collapse all irrelevant sibling comments (if feature enabled)
        if (collapseIrrelevant && element.nodeName === "ARTICLE") {
            element
                .querySelectorAll(
                    `article#${element.id} > ol.comment-tree > li.comment-tree-item > article:not(.is-comment-collapsed)`
                )
                .forEach((child) => {
                    if (!relevant.includes(child))
                        child.classList.add("is-comment-collapsed");
                });
        }
    }
    return wasCollapsed;
}

/**
 * Uncollapses all direct children of the comment.
 * @param {HTMLElement} element Article element of the actual comment
 */
function uncollapseChildren(element) {
    element
        .querySelectorAll("article.is-comment-collapsed article.is-comment-collapsed-individual")
        .forEach(uncollapse);
}

(function () {
    if (!location.hash.startsWith("#comment-")) return; // Not a comment hash
    const comment = document.getElementById(location.hash.substring(1)); // Get comment element
    if (!comment) return; // Comment does not exist
    // Uncollapse the comment itself, and it's parents, then perform other actions if needed/enabled
    if (
        uncollapse(comment) |
            uncollapseParents(
                comment,
                collapseIrrelevant_S,
                uncollapseIndividual_S
            ) ||
        alwaysRun_S
    ) {
        // Uncollapse all children (if feature enabled)
        if (uncollapseChildren_S) uncollapseChildren(comment);
        // Scroll to the comment
        if (smoothScroll_S) comment.scrollIntoView({ behavior: "smooth" });
        else comment.scrollIntoView();
    }
})();

Hi Everyone!

First post on Tildes. I'm excited to have been invited to give it a shot!

I was wondering if anyone here is using Unreal Engine 5 for any project their working on? It could be game design, virtual production, architecture, automotive or you name it!

I'm currently testing out numerous areas of Unreal Engine 5 for virtual production.

Thanks!!

Someone mentioned elsewhere that they signed up for Tildes “years ago during the beta”. That reminded me: Tildes hasn’t reached beta-testing yet.

Officially, Tildes is still in alpha-testing phase.

The login page says “Tildes is currently in invite-only alpha...” And the Contact page says “To request an invite to the Tildes alpha...”

We’re still in alpha-testing. Alpha-testing of software usually happens on an incomplete product before it is released to the customer.

This is a very important point. Tildes is not feature-complete yet: there are literally hundreds of feature requests yet to work on before Tildes will be what people want it to be – and even that list is far from complete. In Agile software development terms, Tildes is a minimum viable product, or, in other words, “a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development”.

Tildes works as it is, but it’s a bare-bones forum: you can post, and comment… and that’s about it. It’s a proof of concept. There are a few minor tweaks here and there, which give the impression that Tildes is more complex than it is, but they’re misleading. There are plans to make Tildes a more complex website but, right now, most of that complexity of Tildes exists only in people’s imaginations (and there have been some very imaginative people contributing to that list of future features!).

Most questions about “Why doesn’t Tildes do X?” or “Can Tildes do X?” can be answered simply by saying “Tildes is incomplete and X hasn’t been built yet.” There are some questions about missing features which can be answered by saying “Tildes was never intended to do X”, but those are far and away in the minority. Most flaws, drawbacks, and problems with Tildes exist because Tildes is still a proof of concept, rather than a finished product.

It’s also worth noting that Tildes’ current feature set is absolutely not up to the task if the user base and site activity increase too quickly. There’s too much manual tinkering required at the moment to make things work properly: for one thing, there are no significant moderation tools on Tildes (that’s almost all done manually at the moment). There are still a lot of features yet to be built - and we don’t even know what some of those features are yet!

To pre-empt the people who will rightly point out that Tildes is 5 years old: Tildes’ feature set was intended to grow gradually over time, in line with a gradual growth in users, activity, and the need for those features to exist. However, Tildes has not undergone much growth over the past few years, so the existing features were sufficient to manage the existing activity. Basically, the site didn’t need a lot of fancy features to handle the low traffic here.

This sudden surge of new users might change that. But it will take time to build more features. That was always the intention, and it hasn’t changed now.

Until then: Tildes is still in alpha-testing. It’s an unfinished product. Set your expectations accordingly.

EDIT:

If you're one of the many people who seem to be replying to this topic, saying "it's okay, I like this simple bare-bones site as it is"... then you're probably not part of my original intended audience for this topic. This topic was aimed at all the people who are arriving here, being taken aback at how simple Tildes is, and wondering where the advanced features are.

However, we can still take the "set your expectations accordingly" message and apply it to you: "Tildes is an unfinished product, so you can expect it to change in the future. It won't be like this forever."

Either way, "set your expectations accordingly" is the message here, whether you're expecting more features and not finding them, or whether you're expecting simplicity and enjoying what you see. Either way, you should know that things will change around here. Maybe slowly. Maybe quickly. Maybe they'll get better from your point of view. Maybe they'll get worse from your point of view. But, change they will.

Happy Friday everyone! I'm making a post to see if anyone wants to beta test my Tildes.net iOS app Backtick.

Background

I've been wanting to create a Reddit app for quite a while, and just when I got started, the API change chaos happened. Thankfully, I remembered signing up for Tildes.net a few years ago and decided to pivot to make an app for this site instead! The app is still a work in progress, but I believe releasing early and getting as many eyes on it during development results in a better end product (and it's more fun for me 😊).

Features

Here are the current features of Backtick:

• Light mode/dark mode
• Login to Tildes.net (suports 2FA)
• Front page feed with sorting support
• View, vote, and comment on posts
• Reply and vote on comments
• Collapse comments
• View notifications
• Full markdown rendering
• Text-to-speech for posts and comments

Here is a video demo of the app in its current state (updated for v1.8.1): https://youtube.com/shorts/iukQJyJbtw8?feature=share

I know there missing features, but as I mentioned before, I would love to get as many people in as early as possible to help shape Backtick's future.

Testing

If you're interested in testing the app as I continue to work on it during my free time you will need:

• An iOS 16 device
• TestFlight (Apple's testing app)

You can access the beta here: https://testflight.apple.com/join/gNH18NE9. If you have any issues please DM me your Apple ID email and I will send you an invite manually.

Thanks, everyone! Have a great weekend.
- Ash

Edit:
Getting some great feedback! I'll be tracking bugs and potential features here if anyone is curious: https://chatter-brick-3d3.notion.site/Backtick-Tracker-888150b641ae4c0ab39dc0345783bc50?pvs=4

Edit2:
I created the Discord server to help facilitate better collaboration with those who wish to be more involved. It will be a place for discussion around potential features, bugs, and general chat. I will still be taking in feedback via TestFlight and Tildes.net, so it's perfectly fine if you don't want to join.
Join here: https://discord.gg/aah7nkfpBY

After reviewing all the beginner friendly tags on the GitLab and figuring out easy answers the hard way, I finally made my first merge request for issue #700 to an open-source project! It isn't much, and probably took me 10x the amount of time it would take for someone who knows what they are doing, and it probably has some issues that needs to be worked out (although I tried to test as thoroughly as possible), I still submitted it. Even if it doesn't get accepted, I'm sure if someone wants to pick up my pieces, they can do so and build out this functionality in a better way.

I just wanted to share and put it out there that you don't have to be a master programmer to make contributions to this site))

Welcome to the discussion thread for the BLAST Premier Spring Final 2023, the last Big Event before the summer break. The event will feature eight of the world’s best CS:GO teams competing for a $425,000 prize pool and a spot at the BLAST Premier World Final 2023. The event will take place at the Entertainment & Sports Arena in Washington, D.C., from June 7-11.

The teams attending the event are:

• Heroic (From Spring Groups)
• G2 Esports (From Spring Groups)
• FaZe Clan (From Spring Groups)
• Natus Vincere (From Spring Groups)
• Vitality (From Spring Groups)
• Astralis (From Spring Groups)
• Cloud9 (From Spring Showdown – EU)
• Imperial (From Spring Showdown – NA)

The event will start with two double-elimination GSL groups, followed by a single-elimination playoff bracket. All matches will be best-of-three.

The event will also mark the return of Vitality to LAN for the first time since their Major triumph in Paris, where they won without dropping a single map. They will face Imperial in their opening match, who might be playing their last event with Gabriel “FalleN” Toledo as rumors of his move to FURIA are rampant.

Other interesting matchups include G2 vs Cloud9, who both had disappointing runs at IEM Dallas and the Major cycle, and Heroic vs Astralis, who will clash for the Danish supremacy.

You can follow the event on BLAST.tv, YouTube, or Twitch. The schedule and results can be found on HLTV or Liquipedia.

This is a bit of a test thread. I will try to post a comment for each match, under which you can share your thoughts and comments about each individual game. As such, it may be preferable to sort the thread by new, in order to see the most recent match-ups. Also, in case I miss any match feel free to post the results yourself!

I figured it'll be easiest to consolidate discussion of all these in one place. As you find more good, thoughtful ones feel free to comment it and I'll edit them into this list.

Overall impressions seem very positive. LTT, in particular, tends to be pretty comfortable being critical of Apple and even he seems impressed (though I think his is the only review that doesn't have a hands-on component.

The Bloggers:

Daring Fireball: https://daringfireball.net/2023/06/first_impressions_of_vision_pro_and_visionos
Nilay Patel: https://www.theverge.com/2023/6/5/23750003/apple-vision-pro-hands-on-the-best-headset-demo-ever

The Vloggers:

iJustine: https://www.youtube.com/watch?v=AtCEGztr8cw
MKBHD: https://www.youtube.com/watch?v=OFvXuyITwBI&t=917s
Linus Tech Tips: https://www.youtube.com/watch?v=SqB0lUcqFbA
Snazzy Labs: https://www.youtube.com/watch?v=uUblFIaZKIk
Norman Chan (via Adam Savage Tested): https://www.youtube.com/watch?v=f0HBzePUmZ0

I've been trying to set up a dev enviornment for Tildes, mainly so that I can actually test my MR (!136), and I've been running into a few issues.

However, since we also have a new influx of people who might be interested in contributing to Tildes, it seems like a good time to collect resources on setting up the dev environment, as well as helping anyone running into issues.

So, if you have issues or advice, post them here! I'll be adding my questions in a comment shortly.

Relevant wiki pages:

• Development / Initial Setup
• Development / General Development Info

Edit: A more recent post on setting up the dev environment on Apple Silicon / M1 Macs

Just tested it myself. Here’s the process that worked for me, in case anyone else needs a guide. No guarantees, of course, but hopefully it works for others too:

From Desktop Mode

Download the Battle.net installer
Add the installer as a non-Steam game
Change the installer settings in Steam to run with Proton Experimental
Run the installer
(tip: to make it easy to find the launcher in the next step, you can change the install path to be in your downloads folder instead of deep in the Proton path)

Once installed, exit the installer
Add the installed Battle.net Launcher.exe as a non-Steam game
Change the launcher settings in Steam to run it with Proton Experimental
Run the launcher
Log in
Install Diablo IV
(tip: uncheck the high res textures option which is on by default to save yourself about 40 GB of space)
Close launcher
(tip: if D4 is the only Bnet game you’re planning on playing, you can rename the launcher in Steam to Diablo IV)

From Gaming Mode

Launch the launcher
Click the Play button on Diablo IV
Enjoy!

Other Tips

During installation or the game, whenever you need a keyboard, press STEAM + X to call it up.

Occasionally, during installation or in the Launcher in game mode, my trackpad input would get wonky or stop responding. When this happens, hold the STEAM button down while using the trackpads, and they should work again.

Beyond that, the game automatically worked from me. It loaded low graphics settings (which are perfect for the Deck) and recognized my controller. It even opens with some accessibility settings before you start playing that lets you scale the font size up too, which makes it easier to read on the small screen.

I can’t say much about how the game actually plays as I really just did this to test if it works. I’ll be putting in my first actual time with the game tomorrow.