Nat

It is a good day to fry.

Good news: long-press on a community name pops up a menu with choices of actions already

Semi-proud to say that after an intro day showing him the scope of the software, my replacement quit. We tried to tell him in the interview but maybe he just didn’t believe us.

Anyone know of an iOS version?

Looks neat! Anyone know of an iOS version?

This link seems right: https://gitlab.com/veilid/veilid

(I think the other link requires login just so GitLab can check if it’s a private repo. It’s not, they just got the link wrong somehow, and it’s not because the repo was renamed.)

Yea, wow, I think this predates the SpongeBob meme!

deleted by creator

You might try https://lemmy.ml/c/lemmy_support

I’ve noticed this too and I’m not on lemmy.world, though I haven’t noticed whether the posts themselves were.

edit: happens in a lemmy.ml thread I checked too

I think the bang only works for communities: !obviousplant@lemmy.world. Voyager can also handle http links to communities (if the link is in a comment or post body, not a post link): https://lemmy.world/c/obviousplant.

Posts and comments are known feature requests that are non-trivial to implement.

I’ve been surprised not to see this with any of the fediverse platforms I’ve browsed. Instead, they’re all using Docker Compose. Any idea why that is?

Appropriate username. I’d say both. Both is good.

I meant a link post whose link is a community. I added a comment to the issue that’s hopefully clearer.

It doesn’t seem to happen for link posts though. This commonly happens in the new communities community: https://lemm.ee/post/2081675

Probably worth a GitHub issue for the profile page to just always show your posts. (If the issue doesn’t already exist.)

vger.app works now

Now that I’m on desktop, I checked and this was just added in 0.18.2: https://github.com/LemmyNet/lemmy-ui/issues/1418

The weird thing (which they’re also discussing elsewhere in this thread: https://upvote.au/comment/148846) is that it links to OP’s instance rather than the community’s instance.

I think it would be best if each post had a canonical tag pointed at the originating server’s version of that post. The lemmy ui generates a canonical tag now but I’m not sure it doesn’t just point to itself.

Since you’re the only one, you might consider setting an expiration on the media so your local storage serves as more of a cache. Like, I’m sure you’re far more likely to revisit a recent thread than a super old one, and as long as the original instance is still around you could redownload the media. This might require software patches though idk