Yeah, that’s a very common thing with Mlmym, and a lot of instances have that issue. It’s also hard to rate-limit because all client connections to the API come from Mlmym’s server rather than the users.

I think you would be better served by checking for the Link header

Can’t really do that, client-side, in a browser application. CORS is a perpetual cockblock (though I understand why it is), and I’d rather not make an internal API endpoint to do the lookup.

The application polls Lemmy’s getFederatedInstances API endpoint at startup, so it has a list of every activity pub server your instance knows about. That’s the first and primary check for the URL that’s being searched.

The second check is just to rule out non activity pub URLs that point to a federated instance (e…g. https://lemmy.world/modlog, https://lemm.world/pictrs/image/blah.webp, etc).

Goal isn’t to “catch 'em all” but to catch the most used ones. If there’s one I don’t account for, either by omission or because the federated platform didn’t exist when I made the patterns, then it will just fall back to a regular search which also includes trying to resolve it as a federated URL (which is the current behavior in all prior versions).

The goal is just to simply short-circuit the search behavior if the query is a known ap_id URL in order to avoid a lengthy search process and quickly redirect you to your instance’s local copy.

I did but was talked into at least maintaining it.

I’m making an “omnisearch” box.

Paste in an AP_ID into the search field, and it auto-resolves it and redirects you to your instance’s local copy (which is very fast) instead of going through the whole search process (which is slow). To prevent false positives, I’m matching the various ap_id formats and only doing the resolution on those; anything else gets passed to search.

Anything else that falls through the cracks just gets passed to search as usual (which also does a resolveObject lookup).

It’s to make life easier.

We’ve had this discussion :)

This application is written against the Lemmy API. It only speaks API. Eventually it’ll speak Piefed API as well, but right now, only Lemmy API.

Lemmy and Piefed only do server-to-server Activity Pub and not client-to-server AP. Clients have to use the API to interact with them. This is a Lemmy (and eventually Piefed) client.

Cool, thanks. I was close with /user guessing from memory.

I think the /users/.../post_id will be sufficient. It just needs to know that the given URL is an AP_ID before passing it off to the API call to resolveObject. Since it already knows instance.domain.tld is a federated instance, it just needs to see if the path is an AP_ID or the HTML (or something else). Thus, I don’t have to parse the whole thing, just check that enough of it matches.

Thanks!

Thanks. I’ve largely been active here for development/testing purposes lately, but agreed. That’s also why I’ve put so much effort into expanding and making a very powerful/granular filtering system in this release. Right now, I can filter entire instances, entire platforms (e.g. Mastodon), people/instances/platforms in specific communities, filter users/communities by regex pattern, etc. Makes it nice to filter people out of specific communities without blocking them entirely.

Eh, I know I made a big stink about it (which I stand by lol), but technically Dubvee’s still online since I need it for developing/testing the admin and mod capabilities. It’s mothballed but still able to be brought back if I ever choose to and get some more admins on board.

You’re welcome! I actually support that guy on Patreon. He’s got almost the exact same taste in music as I do and covers them all in Spanish. It’s like hearing the music I grew up with for the first time all over again.

Seems like it. I was planning only on maintenance, but with the huge amount of work I’ve put into the current dev branch, I can’t really call it maintenance anymore.

Yep, 100%. I’m waiting for the API to mature to the point where I can do everything the native interface can do. I really don’t want to waste my time making a second-class app.

Unfortunately, while I do have Python experience, I don’t have the spare time to contribute to the API code. At least not right now. Hopefully that changes soon.

If you ever wondered what that sounds like in Spanish…

https://www.youtube.com/watch?v=3U1zUqMjBl4&start=72

It starts at 1:12 if the cue in the URL doesn’t work.

Dude even subtitles the “da boom ta uuumm…” lol

It’s not abandoned (anymore) - just moved development to codeberg (https://codeberg.org/tesseract-ui/tesseract) since Github was like “Embrace AI or get out” so I got out. The Github repo is mostly just a mirror from Codeberg but I still need it since it’s the container registry for the releases. I haven’t had a chance to move those yet.

Next release (1.4.42) is probably 60% done. It’s got a lot of changes/overhauls, so this release cadence is taking longer than usual.

Lol, I feel honored. I made this meme as OC 6 months ago (https://dubvee.org/post/2992196). Funniest thing was I laughed at it, upvoted it, and was like, “wait a minute…” lol.

Usually most people don’t even wanna see my memes the first time 😆

No. It’s a PWA and can run offline from cache, but everything is fetched from the API in real time and not stored on-device. I’ve looked into offline support (probably using PouchDB) but haven’t made the first step toward that and have no idea if/when I ever will.

To be fair, it began with the misstep of his senate confirmation.

I’ve had better luck with webp as far as minimizing size while preserving acceptable quality.

Not sure what other apps do this (they really, really should!), but Tesseract can optionally pre-convert a pasted/uploaded image to webp with a user-selectable quality profile. When I ran an instance, I had a very low (250 KB) upload limit on images, and the pre-conversion made it a non-issue for all but the largest images.

That also works to strip out metadata, though I believe pict-rs (Lemmy’s image “subsystem”) will also strip out metadata (don’t quote me on this and do correct me if I’m wrong).

Edit: Also, whoever runs linkage.ds8.zone has Anubis setup wrong. The /api path should not be behind Anubis.

Got #1 and #3 completed.

The search feature is way more handy than I was expecting.

And you can now insert images as if they’re custom emojis:

There’s a few more things I want to add to the media browser if I have time:

1. [Work in Progress] Add “Search” button in the media item viewer action list. Will search for any posts or comments that use that image URL. This will help you both avoid deleting media for active content as well as finding a post/comment you made with that image (if you want to see the context).
2. Add image to favorites. Basically there will be a second tab you can show that’s just images you’ve favorited. These can be quick reference ones, such as reaction memes.
3. Add option to insert the image using the custom emoji syntax. This would basically let you create your own custom emojis.

Update: All 3 of these have been added.

If you did, I didn’t see it lol. Didn’t add this feature until late yesterday evening (was already planned), so I’m not sure why it didn’t show up.

And for those of you who, like me, don’t like being @'d, I got you: