subtitle playback

This is still a little weird. I found that the web client (in a browser) handles this really well with default settings. However, if I try to use the desktop app or a mobile client, I have to force it to burn in the subtitles for them to show up reliably. Fortunately, there are per-client settings for this now:

The products I work on are mostly monoclonal antibodies (and the occasional gene therapy product mixed in). So, the types of diseases they are used to treat vary. To be honest, I work on the process/formulation side of the development pipleline and the actual clinical treatment part is pretty much inconsequential to what I do. Some of the past programs I have worked on include treatments for asthma, eczema, multiple myeloma, breast cancer, MS, hemophilia, and tons of others that I don’t remember. Often, when dealing with antibodies, the same medicine can be effective for multiple indications.

The finished vials, post-lyophilization, sealing, labeling, and packaging, are sent to infusion clinics. There, clinicians will add water to the vials to reconstitute the drugs and then administer them to patients via IV (usually).

Watching TC do a video about something I do professionally has been a bit of a trip. For context, I work with freeze dryers (we call them lyophilizers) in pharmaceuticals rather than foods. I help design the lyophilization cycles for biologics and gene therapy products that get preserved through freeze drying. Until this video, I had no idea that people used these instruments for at-home food preservation (which is kind of insane imo).

The instruments that I work with are typically a much larger version of the bench-scale machine that he is using (usually one of the LyoStar line). However, I have used smaller, bench-scale units as well for some quick and dirty work. I included some pictures at the end behind a spoiler tag. Happy to answer any questions people have.

Some differences in how I use lyophilizers in a scientific setting as opposed to a home-use food setting:

• Typically, we only lyo products that are already filled in vials as opposed to a full tray like he’s done.
• We don’t pre-freeze our products before they go into the lyophilizer. Instead we refrigerate the shelf that the vials are sitting on to freeze the contents before we proceed to the drying steps.
• Speaking of the shelves, in our instrument, the shelves can move up and down. This is used to compress the vials after the cycle is completely done, fully seating the vial stoppers and sealing them before we open up the main door.
• Also speaking about stoppering the vials, we typically allow some nitrogen into the chamber before sealing up the vials, at a pressure moderately less than atmospheric pressure. This helps keep the vial sealed until it is properly crimped with a seal.
• When it comes to drying, we do it in two stages. The primary drying step is when our product is kept cold, but put under vacuum. This removes most of the water, but not enough for our purposes. The secondary drying step is when the product is heated while the vacuum is maintained. This removes the rest of the water. We typically shoot for a residual moisture of <1% for a good cycle.
• He talks about how long the process takes. I have worked on processes that take from 1-5 days. Typically, the lyophilizer is limited with how much liquid can be removed per unit time. This limit is determined by the geometry of the vent that connects the main chamber with your vials, and the chamber containing the condenser. Also, if you try to dry too quickly, it can damage the product you are trying to preserve.
• He has some discussion at the end about the end of the cycle and the progress bar. What the instrument is doing is comparing the vapor pressure in the chamber using two different sensors. One of those is sensitive to the vapor pressure of water vapor, and the other is not. So, when things are fully dried out, those two are going to read the same pressure. While drying is still occurring, the sensor that detects water vapor will read a higher pressure. So, the instrument will continue to extend drying until those two pressures are the same.

I have hosted a wordpress site on my unraid box before, but ended up moving it to a VPS instead. I ended up moving it primarily because a VPS is just going to have more uptime since I end up tinkering around with my homelab too often. So, any service that I expect other people to use, I often end up moving it to a VPS (mostly wikis for different things). The one exception to that is anything related to media delivery (plex, jellyfin, *arr stack), because I don’t want to make that as publicly accessible and it needs close integration with the storage array in unraid.

[email protected] for light novels from Japan

[email protected] for Ascendance of a Bookworm specifically (which just recently published its final volume).

Two that are local to me:

• [email protected]
• [email protected]

@[email protected] does an admirable job with these two. I try to chime in when I can, but am mostly busy with the communities I am running elsewhere.

This is what I do. I have a VPS that handles all the 443 traffic and then proxies it back to my home server on the correct port. I also just serve some things directly from the VPS since I have it already. It also works well to have a second box for things like uptime monitoring.

Sorry for not being clear. I was referring to the discussion threads created by @[email protected] in the anime community. So far, she has been creating discussion threads for the episodes in the general community (episode 4 link for reference). In the past, I have disabled these posts for certain shows if there is a dedicated community to the show that wants to run their own discussion posts ([email protected] did this for instance).

Note if it wasn’t clear: I am a mod of the anime community and the maintainer of the rikka bot.

Feel free to make a promo post over in [email protected] as well. Good luck with things! I don’t want to switch it up partway through the season, but if there is ever a season 2 and you want to run your own episode threads instead of the bot-created ones, let me know.

Some good answers in here already. It boils down to a couple points for me:

• Back when I started selfhosting, it was either nginx or apache, and I found nginx better and easier to set up
• All the nginx knowledge I learned years ago still works just the same as it did back then, so why potentially mess things up by switching if it all still works
• Basically every project has an example nginx config for reference, that can’t be said about other proxies
• It is easier to find support online for edge cases that might pop up with nginx due to the ubiquity of its use and years of history

I didn’t have a VPS with them, but long ago I had a couple domains through them. One of them had an issue with the auto-renewal and I never got a notification of any kind, only finding out when they had taken ownership of the domain, advertising it for sale. Then they wanted some way, way higher amount of money for me to buy it back. So, I don’t have any domains with them any more.

This was years and years ago though, so they might be better now.

I use Sonarr, but it does mess up sometimes for shows even when you mark it as an anime to use absolute numbering. It most often happens with older shows that have lots of OVAs that are sometimes listed as episodes and sometimes listed as specials, depending on the database. So, if you are having Sonarr manage your downloads, then it can grab the wrong episode if its database (I think TVDB) and the release (usually using MAL numbering) disagree.

I don’t have a solution for you, but I will be watching this thread. Currently, I use Sonarr for library organization, but it doesn’t always work well with anime due to title differences and differences between how seasons/specials are numbered in different databases. So, Shoko was on my radar to try out at some point since it uses anidb.

I used to have my docker updates done automatically. However, as the services I used to run just for myself have started to be used by other people (family, friends), I am less tolerant of having things break. So, instead of something like watchtower, I run diun these days. I have it set up to ping me in a discord channel when a docker update is available. Then, I can actually perform the update when I have time and attention to troubleshoot any issues that may come up.

This lines up with my experience. I have nextcloud and wordpress on two different vps’s and just checked their ram usage.

• nextcloud: 468 MB
• wordpress: 120 MB

Caveat to the above is that nextcloud is installed bare metal rather than docker and I have both nextcloud and wordpress set up to use object storage as the media back end.

edit: To add to this OP, the reason we are only talking about ram numbers is that the cpu usage for these applications (with primarily only a single user) is pretty much zero most of the time, so you aren’t going to be limited by the single core machine.

Also, depending on your use case (large amount of data on nextcloud or large media files in wordpress), you might run out of disk space pretty quickly. In those cases, you should consider using object storage as your nextcloud or wordpress media backends as it is cheaper than block storage (there are plugins/tutorials to configure object storage and Linode offers it).

My isp doesn’t support ipv6 in my area (Verizon). They claim to be in the process of rolling it out, but it’s been years that they have been saying that, so idk. At least they don’t use CGNAT, so it isn’t a huge deal for me after I set up dynamic DNS.