Here ya go. ChatGPT did all the hard work: https://chat.openai.com/share/7703dbe5-6801-4d5b-8d56-c3f18ca3ac4a

Edit: here’s a manually refined version: https://gist.github.com/binwiederhier/70f13b7c7338a2b75e15438b5567a6d6

That’s what saving the IDs is for right? It’s easy enough to do in a bash script I think. I’ll post it here later, assuming I get it to work.

Oh that’s a good idea. Any reader suggestions? I have thought about trying RSS again for a while. Maybe this is a good enough reason.

Thanks dude. I’m going to try the curl route. What do you mean by it sends you every post? Isn’t that what I want?

That implies that it’s not a native feature. I gotta find the API docs then…

Edit: Looks like there is an easy-ish API. Examples:

$ curl -s "https://discuss.ntfy.sh/api/v3/post/list?sort=Hot"|jq '.posts[].post.name'
"Docker-compose + Traefik"
"[SOLVED] Self-hosted NTFY does not receive all notifications"
"Markdown is coming soon ... 🤩 😲"
"[disscussion] Lemmy push notifications with ntfy"
"Using healthchecks.io and ntfy.sh to wake you up if your services are down"
"Ntfy Connector: Modal-based discord bot to send,and now receive, ntfy notifications."
"Welcome to the new ntfy discussion board"
"ntfy Web Push / PWA support is coming soon"
"📢  ntfy Web Push / PWA: Request for testing!"
"ntfy release 🎉 - Now with Web Push and a progressive web app (hello iOS friends ❤️), and with dark mode for the web app! ntfy lets you send push notifications to your phone via a simple REST API, and"

There are plenty of instances that copy the original content. As an instance owner that runs a only a single project specific community, I should be able to decide what content is available on my domain, and what isn’t. Don’t you think?

Aside from the questionable content, there is also legal issues around it that I’d rather not deal with.

There is no way to exclude individual communities. The post URLs are generic, like /post/1234. From nginx or other proxies, I cannot tell what community they belong to. I would love to have my own be searchable, but not at the price of tainting my project’s reputation.

Cool thanks

This is neat, but it should really be part of Lemmy to be able to link between instances in a way that rewrites the link to your own instance, and makes subscribing easier.

The votes are equally f-ed up IMHO. Sometimes you click on an upvote and the number changes wildly…

WebSockets … causing live updates to the site which many users dislike

I appreciate all the work in this release. It’s insane how much you packed into one release. Well done. I am most excited about the live updates going away. It was quite disruptive. Thanks for that.

That said, WebSockets can be implemented very efficiently. I run an open source notification service called ntfy, and the public instance ntfy.sh currently keeps 6-8k WebSocket connections and thousands more HTTP stream (long polling HTTP) open, all on a 2 core machine with 4GB of RAM. My point being that WebSockets can be implemented very efficiently. Though in Lemmy’s case it’s likely not necessary.

– Another thing I wanted to notice is that I am missing mentions of security issues in the release notes. There are some tickets that sound really really really bad, like this one: https://github.com/LemmyNet/lemmy/issues/3060

Isn’t that more important than anything else?

I’d pay good money for “Relay for Lemmy”, assuming that the momentum sticks.