Nostr notes by Admiral Patrick

Can't tell if this bugs me or is genius. A lot of names get ...

2026-07-14T21:07:24Z

Can't tell if this bugs me or is genius. A lot of names get pronounced very differently depending on the character. I'm used to shows having consistent pronunciation of character names, places, etc like in Star Trek, Game of Thrones, etc. In the show, though, it's all over the place sometimes.

e.g.

- **Admiral Souther**: Sowther / Suther (The character himself pronounced it "Suther" so I assume that is the correct pronunciation)
- **Klaes Ashford**: Kalus / Klace
- **Marco Inaros:** In-are-ohs / Inner-ohs

Does anyone know if that variation was intentional or just accidental? I could see it either way. If intentional, it does lend some realism since this is common IRL and may also help highlight the differences in dialects between the Earthers, Martians, and Belters.

The only instance that actually, flat-out bugged me was the same lieutenant on the Agatha King pronounced the admiral's name as "Suther" in one episode and Sowther in another despite working closely with the man himself and should, thus, know how to pronounce his name correctly.

Delicious grilled corn is here. Political memes are ---> That ...

2026-07-09T20:52:44Z

Delicious grilled corn is here. Political memes are ---> That Way --->

[YouTube](https://www.youtube.com/watch?v=Io7wofnFB_w)

2026-05-03T01:09:08Z

[YouTube](https://www.youtube.com/watch?v=Io7wofnFB_w)

- [YouTube](https://www.youtube.com/watch?v=EK_LN3XEcnw) ...

2026-03-01T02:27:39Z

- [YouTube](https://www.youtube.com/watch?v=EK_LN3XEcnw)
-[song.link](https://song.link/y/EK_LN3XEcnw)

Maybe I should flesh it out into an actual guide. The Nepenthes ...

2026-02-13T19:24:52Z

In reply to nevent1q…4r2e
_________________________

Maybe I should flesh it out into an actual guide. The Nepenthes docs are "meh" at best and completely gloss over integrating it into your stack.

You'll also need to give it corpus text to generate slop from. I used transcripts from 4 or 5 weird episodes of Voyager (let's be honest: shit got *weird* on Voyager lol), mixed with some Jack Handy quotes and a few transcripts of Married...with Children episodes.

https://content.dubvee.org/ is where that bot traffic lands up if you want to see what I'm feeding them.

Thanks! Mostly there's three steps involved: 1) Setup ...

2026-02-13T17:25:46Z

In reply to nevent1q…53mn
_________________________

Thanks!

Mostly there's three steps involved:
1) Setup Nepenthes to receive the traffic
2) Perform bot detection on inbound requests (I use a regex list and one is provided below)
3) Configure traffic rules in your load balancer / reverse proxy to send the detected bot traffic to Nepenthes instead of the actual backend for the service(s) you run.

Here's a rough guide I commented a while back: https://dubvee.org/comment/5198738

Here's the post link at lemmy.world which should have that comment visible: https://lemmy.world/post/40374746

You'll have to resolve my comment link on your instance since my instance is set to private now, but in case that doesn't work, here's the text of it:

So, I set this up recently and agree with all of your points about the actual integration being glossed over.

I already had bot detection setup in my Nginx config, so adding Nepenthes was just changing the behavior of that. Previously, I had just returned either 404 or 444 to those requests but now it redirects them to Nepenthes.

Rather than trying to do rewrites and pretend the Nepenthes content is under my app's URL namespace, I just do a redirect which the bot crawlers tend to follow just fine.

There's several parts to this to keep my config sane. Each of those are in include files.

- An include file that looks at the user agent, compares it to a list of bot UA regexes, and sets a variable to either 0 or 1. By itself, that include file doesn't do anything more than set that variable. This allows me to have it as a global config without having it apply to every virtual host.

- An include file that performs the action if a variable is set to true. This has to be included in the `server` portion of each virtual host where I want the bot traffic to go to Nepenthes. If this isn't included in a virtual host's `server` block, then bot traffic is allowed.

- A virtual host where the Nepenthes content is presented. I run a subdomain (`content.mydomain.xyz`). You could also do this as a path off of your protected domain, but this works for me and keeps my already complex config from getting any worse. Plus, it was easier to integrate into my existing bot config. Had I not already had that, I would have run it off of a path (and may go back and do that when I have time to mess with it again).

The `map-bot-user-agents.conf` is included in the `http` section of Nginx and applies to all virtual hosts. You can either include this in the main `nginx.conf` or at the top (above the `server` section) in your individual virtual host config file(s).

The `deny-disallowed.conf` is included individually in each virtual hosts's `server` section. Even though the bot detection is global, if the virtual host's `server` section does not include the action file, then nothing is done.

#### Files
:::spoiler map-bot-user-agents.conf

Note that I'm treating Google's crawler the same as an AI bot because....well, it is. They're abusing their search position by double-dipping on the crawler so you can't opt out of being crawled for AI training without also preventing it from crawling you for search engine indexing. Depending on your needs, you may need to comment that out. I've also commented out the Python requests user agent. And forgive the mess at the bottom of the file. I inherited the seed list of user agents and haven't cleaned up that massive regex one-liner.

```nginx
# Map bot user agents
## Sets the $ua_disallowed variable to 0 or 1 depending on the user agent. Non-bot UAs are 0, bots are 1

map $http_user_agent $ua_disallowed {
default 0;
"~PerplexityBot" 1;
"~PetalBot" 1;
"~applebot" 1;
"~compatible; zot" 1;
"~Meta" 1;
"~SurdotlyBot" 1;
"~zgrab" 1;
"~OAI-SearchBot" 1;
"~Protopage" 1;
"~Google-Test" 1;
"~BacklinksExtendedBot" 1;
"~microsoft-for-startups" 1;
"~CCBot" 1;
"~ClaudeBot" 1;
"~VelenPublicWebCrawler" 1;
"~WellKnownBot" 1;
#"~python-requests" 1;
"~bitdiscovery" 1;
"~bingbot" 1;
"~SemrushBot" 1;
"~Bytespider" 1;
"~AhrefsBot" 1;
"~AwarioBot" 1;
# "~Poduptime" 1;
"~GPTBot" 1;
"~DotBot" 1;
"~ImagesiftBot" 1;
"~Amazonbot" 1;
"~GuzzleHttp" 1;
"~DataForSeoBot" 1;
"~StractBot" 1;
"~Googlebot" 1;
"~Barkrowler" 1;
"~SeznamBot" 1;
"~FriendlyCrawler" 1;
"~facebookexternalhit" 1;
"~*(?i)(80legs|360Spider|Aboundex|Abonti|Acunetix|^AIBOT|^Alexibot|Alligator|AllSubmitter|Apexoo|^asterias|^attach|^BackDoorBot|^BackStreet|^BackWeb|Badass|Bandit|Baid|Baiduspider|^BatchFTP|^Bigfoot|^Black.Hole|^BlackWidow|BlackWidow|^BlowFish|Blow|^BotALot|Buddy|^BuiltBotTough|
^Bullseye|^BunnySlippers|BBBike|^Cegbfeieh|^CheeseBot|^CherryPicker|^ChinaClaw|^Cogentbot|CPython|Collector|cognitiveseo|Copier|^CopyRightCheck|^cosmos|^Crescent|CSHttp|^Custo|^Demon|^Devil|^DISCo|^DIIbot|discobot|^DittoSpyder|Download.Demon|Download.Devil|Download.Wonder|^dragonfl
y|^Drip|^eCatch|^EasyDL|^ebingbong|^EirGrabber|^EmailCollector|^EmailSiphon|^EmailWolf|^EroCrawler|^Exabot|^Express|Extractor|^EyeNetIE|FHscan|^FHscan|^flunky|^Foobot|^FrontPage|GalaxyBot|^gotit|Grabber|^GrabNet|^Grafula|^Harvest|^HEADMasterSEO|^hloader|^HMView|^HTTrack|httrack|HTT
rack|htmlparser|^humanlinks|^IlseBot|Image.Stripper|Image.Sucker|imagefetch|^InfoNaviRobot|^InfoTekies|^Intelliseek|^InterGET|^Iria|^Jakarta|^JennyBot|^JetCar|JikeSpider|^JOC|^JustView|^Jyxobot|^Kenjin.Spider|^Keyword.Density|libwww|^larbin|LeechFTP|LeechGet|^LexiBot|^lftp|^libWeb|
^likse|^LinkextractorPro|^LinkScan|^LNSpiderguy|^LinkWalker|msnbot|MSIECrawler|MJ12bot|MegaIndex|^Magnet|^Mag-Net|^MarkWatch|Mass.Downloader|masscan|^Mata.Hari|^Memo|^MIIxpc|^NAMEPROTECT|^Navroad|^NearSite|^NetAnts|^Netcraft|^NetMechanic|^NetSpider|^NetZIP|^NextGenSearchBot|^NICErs
PRO|^niki-bot|^NimbleCrawler|^Nimbostratus-Bot|^Ninja|^Nmap|nmap|^NPbot|Offline.Explorer|Offline.Navigator|OpenLinkProfiler|^Octopus|^Openfind|^OutfoxBot|Pixray|probethenet|proximic|^PageGrabber|^pavuk|^pcBrowser|^Pockey|^ProPowerBot|^ProWebWalker|^psbot|^Pump|python-requests\/|^Qu
eryN.Metasearch|^RealDownload|Reaper|^Reaper|^Ripper|Ripper|Recorder|^ReGet|^RepoMonkey|^RMA|scanbot|SEOkicks-Robot|seoscanners|^Stripper|^Sucker|Siphon|Siteimprove|^SiteSnagger|SiteSucker|^SlySearch|^SmartDownload|^Snake|^Snapbot|^Snoopy|Sosospider|^sogou|spbot|^SpaceBison|^spanne
r|^SpankBot|Spinn4r|^Sqworm|Sqworm|Stripper|Sucker|^SuperBot|SuperHTTP|^SuperHTTP|^Surfbot|^suzuran|^Szukacz|^tAkeOut|^Teleport|^Telesoft|^TurnitinBot|^The.Intraformant|^TheNomad|^TightTwatBot|^Titan|^True_Robot|^turingos|^TurnitinBot|^URLy.Warning|^Vacuum|^VCI|VidibleScraper|^Void
EYE|^WebAuto|^WebBandit|^WebCopier|^WebEnhancer|^WebFetch|^Web.Image.Collector|^WebLeacher|^WebmasterWorldForumBot|WebPix|^WebReaper|^WebSauger|Website.eXtractor|^Webster|WebShag|^WebStripper|WebSucker|^WebWhacker|^WebZIP|Whack|Whacker|^Widow|Widow|WinHTTrack|^WISENutbot|WWWOFFLE|^
WWWOFFLE|^WWW-Collector-E|^Xaldon|^Xenu|^Zade|^Zeus|ZmEu|^Zyborg|SemrushBot|^WebFuck|^MJ12bot|^majestic12|^WallpapersHD)" 1;

}

```
:::

:::spoiler deny-disallowed.conf
```nginx
# Deny disallowed user agents
if ($ua_disallowed) {
# This redirects them to the Nepenthes domain. So far, pretty much all the bot crawlers have been happy to accept the redirect and crawl the tarpit continuously
return 301 https://content.mydomain.xyz/;
}
```
:::

I was blocking them but decided to shunt their traffic to ...

2026-02-13T16:35:01Z

In reply to nevent1q…dwf4
_________________________

I was blocking them but decided to shunt their traffic to Nepenthes instead. There's usually 3-4 different bots thrashing around in there at any given time.

If you have the resources, I highly recommend it.

**California residents who lit illegal fireworks over the July 4 ...

2025-07-07T02:08:24Z

**California residents who lit illegal fireworks over the July 4 holiday may be in for a nasty surprise in the mail thanks to covert fire department operations.**

A number of California cities, including Sacramento, have begun using drones to locate people shooting off illegal fireworks. From Wednesday to Saturday night, the Sacramento Fire Department’s special fireworks task force patrolled the streets with unmarked cars and drones, focusing on neighborhoods where they’ve had prior complaints. Task force officers and the drones took photos of the illegal activity, and within 30 days the property owner where the fireworks were used could receive a fine in the mail.

Waited weeks for this and was so excited it finally arrived ...

2025-07-06T02:08:40Z

Waited *weeks* for this and was so excited it finally arrived today. Unboxed it, put it on charge, and....nothing. Won't boot up, no signs of life. He's dead, Jim.

Now I have to send it back and wait who knows how long if I want a replacement. Probably just going to ask for a refund; I can't wait another 4-6 weeks or wait for one to ship from the September batch. Ugh!

Mildly infuriating, highly disappointing.

TNG 6x24: Second Chances Ok, she said "Night Bird" but ...

2025-07-05T19:36:21Z

TNG 6x24: Second Chances

Ok, she said "Night Bird" but same energy.

It also helps to imagine that scene, but with this voice:

![]( )

Dog-piling is when someone expresses an opinion and people swarm ...

2025-06-25T17:30:32Z

Dog-piling is when someone expresses an opinion and people swarm in the comments telling the OC how wrong they are and how right *they* are. Typically the person getting dogpiled is downvoted into oblivion in the process. Note that I'm not talking about anything controversial in their opinion or the comment being trolling in any way; just any general disagreement with the groupthink.

**Brief example**:
```
User 1: There are lots of factors at play here, not just money. There's X, Y, Z, and those are all independent from money.
|____> User 2: No, it's money. It's always money
|______> User 4: Right? How can anyone think it's anything *but* money? Some people!
|____> User 3: Yes, well, X, Y, and Z wouldn't be a problem if not for capitalism, so it's definitely money, and you're wrong.
|____> User 5: It all boils down to money; always does.
|____> User 6: Of course it's money. Only a capitalist bootlicker would think otherwise.
|____> User 7: Go back to Reddit, troll.
|____> User 8: You're so close, but it's money.
...
|____> User 999: (Same as the last 998 comments; contributes nothing except attacking the opinion for being different)
```

None of that adds anything to the discussion; they're not engaging on the subject, just attacking the opinion because it differs.

That behavior does not seem healthy to me and seems like it's almost designed to discourage anyone from expressing any opinion that's not part of the established group think. Again, I am not talking about trolls here, just any kind of differing opinions.

Should that kind of behavior be discouraged? If so, as a mod, what would be the best way to address it? After the 2nd or 3rd dogpile comment, start removing subsequent ones that are just piling on?

It's definitely a people problem, so I'm curious what would be a gentle but firm way to deal with it.

Fake bans aren't a thing, but banning from an instance ...

2025-04-07T20:47:14Z

In reply to nevent1q…76hf
_________________________

Fake bans aren't a thing, but banning from an instance doesn't necessarily ban them from all communities (just the ones they've interact with up to the time of the ban).

This means someone on instance B, who is banned from instance A, can still interact with communities on instance A via instance B if instance B was not informed the person was banned from the community.

However, a user from instance B, banned from instance A, interacting with a community on instance A via instance B will not have their content federated via instance A (the home instance of the community). Thus, only other users on instance B should be able to see that user's submissions.

Clear as mud?

Ugh. I've already decided I'm not going to 1.0, so if ...

2025-03-16T18:27:54Z

In reply to nevent1q…rgkw
_________________________

Ugh. I've already decided I'm not going to 1.0, so if it's not in 0.19.10 maybe I'll patch it in myself until I figure out a way to move my instance to Piefed.

Upgraded my instance from 0.19.3 to 0.19.9 today, and fetching ...

2025-03-16T18:07:49Z

Upgraded my instance from 0.19.3 to 0.19.9 today, and fetching metadata for Youtube videos no longer works. Worked perfectly on 0.19.3 as of 3 hours ago (pre-upgrade).

This is how it's supposed to look:

![]( )

Good job, lemmy devs! 👍

Developers: I will never ever do that, no one should ever ...

2025-02-19T00:04:41Z

Developers: I will never *ever* do that, *no one* should *ever* do that, and you should be ashamed for guiding people to. I get that you want to make things easy for end users, but at least exercise some bare minimum common sense.

The worst part is that `bun` is just a single binary, so the install script is bloody pointless.

Bonus mildly infuriating is the mere existence of the `.sh` TLD.

**Edit b/c I'm not going to answer the same goddamned questions 100 times from people who blindly copy/paste the *question* from StackOverflow into their code/terminal:**

> WhY iS ThaT woRSe thAn jUst DoWnlOADing a BinAary???

1) Downloading the compiled binary from the release page (if you don't want to build yourself) has been a way to acquire software since shortly after the dawn of time. You already know what you're getting yourself into
1) There are SHA256 checksums of each binary file available in each release on Github. You can confirm the binary was not tampered with by comparing a locally computed checksum to the value in the release's checksums file.
1) Binaries can also be signed (not that signing keys have never leaked, but it's still one step in the chain of trust)
1) The install script they're telling you to pipe is not hosted on Github. A misconfigured / compromised server can allow a bad actor to tamper with the install script that gets piped directly into your shell. The domain could also lapse and be re-registered by a bad actor to point to a malicious script. Really, there's lots of things that can go wrong with that.

The point is that it is bad practice to just pipe a script to be directly executed in your shell. Developers should not normalize that bad practice.

I'm....speechless and all out of snark on this one. This is ...

2025-02-09T01:52:22Z

In reply to nevent1q…9kfu
_________________________

I'm....speechless and all out of snark on this one. This is fucking horrifying.

Single-issue voters who threw their vote away or sat out and did not help stop this, well, hope you're happy with your choices.

I'm unfamiliar with Clubsall. Is it pulling them via ...

2024-12-12T23:20:05Z

In reply to nevent1q…32p6
_________________________

I'm unfamiliar with Clubsall. Is it pulling them via federation or fetching via API? Would defederating work? I appear to have already defederated, likely in response to your earlier post, but not sure if that does anything. And that only stops them from pulling content from my instance, not what I posted to any other.

Context: [30 Rock: ...

2024-12-05T02:59:03Z

**Context**: [30 Rock: Homonym](https://www.youtube.com/watch?v=WZLkcFns8Ks) - A fake game show where the host says a homonym (stare/stair, meet/meat, etc), and the contestant has to guess the right word. It's *always* the other one.

Inspired from [this post](https://feddit.org/post/5379286)

> People in a quiet neighborhood in Carthage, a town in Moore ...

2024-08-27T18:12:51Z

> People in a quiet neighborhood in Carthage, a town in Moore County, North Carolina, heard a series of six loud pops a few minutes before 8:00 p.m. on Dec. 3, 2022. A resident named Michael Campbell said he ducked at the sound. Another witness told police they thought they were hearing fireworks. **The noise turned out to be someone shooting a rifle at a power substation next door to Campbell's home.** The substation, operated by the utility Duke Energy Corp., consists of equipment that converts electricity into different voltages as it's transported to the area and then steered into individual houses. The shots hit the radiator of an electrical transformer, a sensitive piece of technology whose importance would likely be understood only by utility company employees. It began dumping a "vast amount" of oil, according to police reports. A subsequent investigation has pointed to a local right-wing group, one of a wave of attacks or planned attacks on power infrastructure.

> By 8:10 the lights in Carthage went out. Minutes later, a security alarm went off at a Duke Energy substation 10 miles away, this one protected from view by large pine trees. When company personnel responded, they found that someone had shot its transformer radiator, too. Police found shell casings on the ground at the site and noticed someone had slashed the tires on nearby service trucks. The substations were designed to support each other, with one capable of maintaining service if the other went down. Knocking out both facilities prevented the company from rerouting power. Police described the two incidents as a coordinated attack. About 45,000 families and businesses remained dark for four days. This was a burden for area grocery stores and local emergency services. One woman, 87-year-old Karin Zoanelli, died in the hours after the shooting when the blackout caused her oxygen machine to stop operating. The North Carolina Medical Examiner's office classified the death as a homicide.

> The attack on Duke's facilities in Moore County remains unsolved, but **law enforcement officials and other experts suspect it's part of a rising trend of far-right extremists targeting power infrastructure in an attempt to sow chaos. The most ambitious of these saboteurs hope to usher in societal collapse, paving the way for the violent overthrow of the US government, according to researchers who monitor far-right communities.**

> Damaging the power grid has long been a fixation of right-wing extremists, who have plotted such attacks for many years. They've been getting a boost recently from online venues such as "Terrorgram," a loose network of channels on the social media platform Telegram where users across the globe advocate violent white supremacism. In part, people use Terrorgram to egg one another on -- a viral meme shows a stick figure throwing a Molotov cocktail at electrical equipment. People on the forum have also seized on recent anti-immigration riots in the UK, inciting people there to clash with police. In June 2022, months before the Moore County shootings, users on the forum began offering more practical support in the form of a 261-page document titled "Hard Reset," which includes specific directions on how to use automatic weapons, explosives and mylar balloons to disrupt electricity. One of the document's suggestions is to shoot high-powered firearms at substation transformers.

- [MBFC](https://mediabiasfactcheck.com/bloomberg/)
- [Archive](https://archive.ph/YGmmf)

cross-posted from: ...

2024-06-21T21:11:04Z

cross-posted from: [dubvee.org/post/1381314](https://dubvee.org/post/1381314 )

#

Changelog for 1.4.x Series (Intrepid)
##

1.4.0
This is the first release which completely drops “legacy” support for 0.18.x and below. The minimum required API level is now 0.19.3 (though it will work with any 0.19.x series, there will be broken features that require 0.19.3).

None of the 0.19.4 features are implemented yet. Updating my instance to 0.19.4 is not on my priority list at the moment, though I *really* wished the media listing was present when I added the new media handling stuff. :sigh:

I’ll probably be working on the 0.19.4 features sometime soon as I would like to finish what I had in mind for the media handling, and 0.19.4 provides the missing piece.

Anyway, here’s what’s new and improved:

###

New Features
<summary>Zoomable Images</summary>Most images are now zoomable: post images, user/site/community avatars, images posted in comments, etc. 
All the pan/zoom libraries I tried suuuuuuucked, so I ended up rolling my own from scratch. The pinch zoom isn’t quite where I want it, but it’s a start. If anyone wants to contribute some code for improving that, please let me know. 
- Support zoom, pan, and rotate
- Mouse scroll to zoom
- Click/grab to pan
- Rotate via on-screen buttons
- Double-click to quick zoom in/out by 2x
- Gesture support
- Pinch zoom in/out
- Swipe up to zoom in
- Swipe down to zoom out
- Swipe left or right to close the zoom modal
- Other gestures may be added once I figure out a clean way to differentiate them from conflicting mouse events

<summary>Basic Gesture Support</summary>First, I should point out that I am not a fan of gesture navigation; absolutely hate it as a primary method of interaction. I’m old and hate having to guess whether my fingers need to do the Macarena or the Hokey-Pokey to perform what should be an intuitive action.
That said, I do like waving things (and people) away.
To that end, I’ve added some gesture recognition in a few places, mostly modals. Any modal can now be dismissed with a left or right swipe in an area not bound by other event handlers.
- e.g. You can’t swipe in the text field to dismiss an edit/report/ban/remove modal; you have to swipe outside of that.
- Left/right swipe was chosen as to not interfere with scrolling so it could be used consistently across all modal types.
The only other place, currently, with gesture support is the image zoom modal (described above).
I may add some additional swipe actions where it’s intuitive to do so. For now, I’m content with modals being easier to dismiss on mobile without having to reach up to the close button in the top corner.

<summary>User Profile Modals</summary>Clicking on usernames throughout the application will now load a modal with their user card and relevant action buttons. Old behavior was taking you to their profile directly. 
Actions include:
- Go to profile
- Message in Lemmy / Matrix
- Block User
- Search for alts / simiarly-named accounts
- Ban user from instance (admins only)
- View user on their home instance
- Copy Lemmyverse link for user

<summary>Image Management on Posts/Comments (Paste Images into Post URL and Markdown Editor)</summary>- Images can be pasted in the post’s URL field as well as in the markdown editor. 
- Images can optionally be pre-processed to webP along with a user-selectable quality level. Especially useful if your instance limits the size of uploads
- Can delete post images (only before you save the post; unfortunately there’s no way to retrieve the delete token after that even though it is stored in the DB. Yet another API limitation :sigh:)
- This is addressed in 0.19.4, but I don’t have support for that yet.
- Images pasted/uploaded into the markdown editor are tracked in a bar along the bottom of the editor. Individual images can be deleted as needed along with the corresponding markdown code for them.

<summary>Hide Posts/Comments From New Users</summary>In App Settings -> Filters, you can now opt to hide posts/comments made by new users. You can also set the number of days an account is considered new: 1 to 30 days. That setting also is applied to the new user badges (if you set the minimum age to 15 days, any account 15 days or younger will show the new user badge).
This setting behaves differently for mods and admins:
- Mods: Filter will be applied to all posts/comments except in communities of which you are a moderator.
- Admins: Filter will be applied to all posts/coments except those made to communities local to your instance or those made to remote communities of which you are a moderator.
Comments made by new users will be hidden, and that includes any replies (essentially behaves the same way as blocked users)

<summary>Federation State Viewer</summary>From the instances menu on a post, there’s a new option called “Federation Stats” which will show you the stats from your instance to the target and from the target to your instance. Also included in that is an estimated cacluation of the number of activities each instance is behind (useful for troubleshooting federation delays).
This information has also been added to the instance items at <code>/instances</code>
Please note that the “Activities behind” counter is only an estimate. The value for <code>newest_activity_id</code> is not provided by the API (because that would be useful, so why would the Lemmy devs include it?), so it has to be estimated. The estimation is done by looking at the <code>last_successful_id</code> of all the linked instances and grabbing the highest number and subtracting the <code>last_successful_id</code> for the selected instance. Not all of those activities would necessarily be coming to your instance (votes/posts/comments to communities yours isn’t subscribed to, etc), so it is merely an estimation. Just because it shows you are behind by X number doesn’t necessarily mean it’s behind by that many.

<summary>Instances Page</summary>Re-wrote this to do manual pagination, searching, and filtering. Much more responsive now that it is not rendering several thousand components each with actions items.

<summary>"Click to Play" Media Embeds</summary>If media is disabled in the feed, the thumbnail will now have an overlay button that will convert it to an embed on-the-fly. 
When loading a video via click-to-play, I’m conditionally setting the “autoplay” flag where the embed API supports it, but it doesn’t always seem to be honored. This is an attempt to not have to press “play” twice for a video. So far, the only video frontend that seems to honor it is YouTube. Invidious/Piped, so far, do not, and neither does PeerTube. 
Ok, so autoplay works if muted (no idea how YouTube’s player gets around this; probably some chicanery). I think that’s worse because you still have to click twice on the videos, and the “unmute” button is harder to reach than “play”. So I think I’m going to just settle on having to click play twice.
This seems to be be a Chrome/Chromium thing (and explains why YT gets to bypass this). In Firefox, the autoplay flag is respected without having to mute the video.

<summary>Re-Integrated Piped Support as an Embeddable Youtube Frontend</summary>Now that click to play has been added, Piped support has been added back. It was removed due to poor performance and rate limiting when used with feed embeds. 
If media embeds are enabed in the feed, only YouTube frontend will show direct embeds. Piped/Invidious will always be click to play regardless of embed setting due to above mentioned rate limiting / performance.

<summary>Alternate Source Dropdown / Archive Links</summary>Removed the <code>[Archive Link]</code> next to the post URL and replacd it with a fancy menu to the left of it.
- On posts with links, it currently has buttons to search for the article at Archive Today, Ghost Archive, and 12ft.io
- On Youtube-like posts, can select alternalte links for YouTube, Invidious, or Piped
- Invidious/Piped will open with your preferred instance (defined in settings)
- Useful if someone posts a video to an Invidious instance that performs poorly for you and you would prefer to view it on your preferred Invidious/Piped instance or canonically on YouTube.

<summary>Quick Action Menus</summary>On mobile, the navbar was getting cluttered, so most of the discrete dropdowns there have been moved into Quick Actions menus.
- Main, Community, and User feed pages: Quick Actions has replaced all discrete menus
- Search Page, Modlog, instances page, and Community Browser: All of the filtering options are in a quick action menu

<summary>Users Can Now Add Their Own Preferred Invidious/Piped Instances</summary>Prior to this release, any Piped or Invidious instances needed to be added by the administrator via environment variables. In addition to that, users can now add any number of custom Invidious and/or Piped instances in the app settings.
These will be combined with the built-in list and the admin-extended list and be available for use as your preferred YT frontend and for detection of Piped/Invidious links in posts.
Be aware that those custom instances will only render as embeds for you; they will be thumbnails for anyone else who hasn’t added them to Tesseract. If you feel that instance should be added to Tesseract’s built-in list, please submit a Github issue with the details.
Tesseract is pre-populated with the official list of public instances for each, but it can get out of date easily.
Note: As of 6/20/2024, I’ve noticed a lot of Invidious/Piped instances are now requiring login, and embeds through them no longer work. I believe if you have an account with one, log in, and enable 3rd party cookies for that domain, the embeds should work. I have not tried that, but it does work with Spotify. This isn’t a Tesseract bug, unfortunately, or I’d fix it. 

<summary>Can Disable Infinite Scroll if you Want</summary>If you’re not a fan of the infinite scroll, you can go to App Settings -> Feed and disable infinite scroll. 

<summary>TOTP 2FA Setup</summary>Can now enable and enroll in 2FA as well as disable it.

<summary>Account Icons Now Use Your Profile Avatar</summary>Icons in the account switcher and account screens now sync to your profile avatar, if defined.

<summary>New Placeholder User Avatars</summary>Instead of the initials as used previously on accounts without avatars, now uses Dicebear Adventurer pseudorandom avatars. Initials are still used for placeholder community icons when the community mods haven’t set one.

<summary>Passwords Can Now Be Revealed</summary>All password elements will now allow you to toggle them to reveal. Should make a big improvement when logging-in on mobile.

<summary>Vote Viewer (Admins Only)</summary>Admins can now see votes like in Lemmy-UI. Uses infinite scroll and deduplication to compensate for the stupid API that returns multiple/duplicate votes on each page.


###

Bugfixes and Enhancements
<summary>Removed 0.18.x Backwards Compatibility</summary>- Or, more specifically, removed 0.18.x JS client and the extensions I wrote to make that compatible with 0.19.x. Now uses the 0.19.3 JS client.
- Removed the image upload proxy which was needed in 0.18x due to CORS restrictions.

<summary>Various Enhancements to Auth Module.</summary>- Added safety check so that the auth token is only ever sent to the profile’s associated instance and cannot accidentally send to non-home instance (e.g. when browsing communities on a remote instance).
- Fixed a few chicken/egg situations where the profile store needed to be accessed before it was initialized
- If your auth token is invalid, such as after changing your password on another device, you will get a toast message you can click to take you to the login screen.
- If a profile exists for a username/instance combo, logging in will update the auth token for that existing profile rather than creating a new one.
- User avatars are now fetched when logging in.

<summary>Grace Period Before Media Embeds are Destroyed When Scrolling out of Viewport</summary>- Embeds now have a short timeout when leaving the viewport before they’re removed from the DOM and turn back into thumbnails. Fixes annoyance when resizing the window while a video is playing and the video temporarily leaves the viewport and is destroyed. Timeout is 2 seconds and will reset/disarm if the post returns to the viewport before it expires.

<summary>Community Creation / Editing</summary>- Uses new upload handler for banner/icon
- Can pre-process the banner/icon to webP before uploading
- Shows a live preview of how the community card will look

<summary>General</summary>- Slightly darkened background color in light mode cards (bg-white->bg-slate-100) for better contrast. Did similarly for some button colors
- Added “OpenDyslexic” as a UI font option
- Can now close modals with Escape key, close button, or by swiping left/right
- Added button to reveal password fields
- Some modals can be closed by clicking out of them.
- I need to disable this or make it more consistent. Some workflows utilize nested modals, so I do need to be able to keep them open when interacting with a child modal.
- Added “share” link for searches.
- Will generate a URL with the current search params and copy to your clipboard.

###

Other Stuff
####

Peertube Follows
On my last release post, someone mentioned that following Peertube channels may be broken. At the time I was still on 0.18.5 and had followed a PT channel, and *seemed* to be getting updates from it. Then I wasn’t sure.

I can say that I *have* been getting at least some updates to the PT channel I follow (mostly as a test). While there have been videos posted there that did not come through to Lemmy, I don’t know enough about PeerTube to know if they were published differently or what. However, I have gotten at least 2-3 that someone posted to Lemmy that would absolutely had to have come in via Federation.

Also confirmed that commenting on a PT video (from the channel feed, not an embed to a Lemmy community) does federate out and show up on Peertube’s side along with any votes you give in Lemmy.

This isn’t really a Tesseract issue since the Lemmy backend handles that. Just figured since I do support Peertube, it would be worth mentioning that it seems to work.

###

What Didn’t Make the Cut This Release

<li>User profile import/export</li>
<li>Link previews</li>
<li>Custom feed rewrite</li>
<li>Custom emoji management</li>
<li>Fediseer Rewrite</li>

I keep kicking the can on the custom feed and infinite scroll re-writes, but for a good reason. I want to start using IndexedDB to get around storage constraints in the browser’s LocalStorage API. I need to write and integrate a library for this (or find one I don’t hate), and that’s going to take some dedicated development time. Switching to IndexDB is also a step in the direction I want to go towards providing offline support. So, at some point, there will be a release that only focuses on that. Not sure if it’ll be in the 1.4.x series or later, but ultimately, that is where I want to go.

###

Get Tesseract

<li><a href="https://tesseract.dubvee.org">Hosted Instance: Unlocked to allow login to any Lemmy instance</a></li>
<li><a href="https://github.com/asimons04/Tesseract/">Github</a></li>;
<li><a href="https://github.com/asimons04/tesseract/blob/main/ChangeLog.md">Changelog</a></li>;
<li><a href="https://github.com/asimons04/tesseract/tree/main/docs">Docs</a></li>;
<li><a href="https://matrix.to/#/#tesseract:ptznetwork.org">Matrix Support</a></li>
<li><a href="https://dubvee.org/c/tesseract">Lemmy Community</a></li>
<li>Docker: <code>ghcr.io/asimons04/tesseract:v1.4.0</code> (Should have images for amd64 and arm64 now that the Github actions are fixed)</li>

Nostr notes by Admiral Patrick

Can't tell if this bugs me or is genius. A lot of names get ...

Delicious grilled corn is here. Political memes are ---> That ...

[YouTube](https://www.youtube.com/watch?v=Io7wofnFB_w)

- [YouTube](https://www.youtube.com/watch?v=EK_LN3XEcnw) ...

Maybe I should flesh it out into an actual guide. The Nepenthes ...

Thanks! Mostly there's three steps involved: 1) Setup ...

I was blocking them but decided to shunt their traffic to ...

**California residents who lit illegal fireworks over the July 4 ...

Waited *weeks* for this and was so excited it finally arrived ...

TNG 6x24: Second Chances Ok, she said "Night Bird" but ...

Dog-piling is when someone expresses an opinion and people swarm ...

Fake bans aren't a thing, but banning from an instance ...

Ugh. I've already decided I'm not going to 1.0, so if ...

Upgraded my instance from 0.19.3 to 0.19.9 today, and fetching ...

Developers: I will never *ever* do that, *no one* should *ever* ...

I'm....speechless and all out of snark on this one. This is ...

I'm unfamiliar with Clubsall. Is it pulling them via ...

**Context**: [30 Rock: ...

> People in a quiet neighborhood in Carthage, a town in Moore ...

cross-posted from: ...

Waited weeks for this and was so excited it finally arrived ...

Developers: I will never ever do that, no one should ever ...

Context: [30 Rock: ...