Feedbin VS Mastodon

It would work the same for me, if only because I'd redirect the email to my RSS reader (via Feedbin[0] or Kill the Newsletter[1] or similar)! I suspect most people who care about RSS would do the same, but the Webflow docs[2] show it being pretty straightforward to set up, and (imo) it's an easy backup hedge against all your comms getting stuck in spam filters. Plus, it just feels more ADHD-friendly to me to reduce ping noise as much as possible.

[0] https://feedbin.com/

[1] https://kill-the-newsletter.com/

[2] https://university.webflow.com/lesson/rss-feed

I use Feedbin to read them. Because of their open nature nobody can tell the sole developer there “people can only read feeds using our app, and you can go pound sand”.

Comes to my mind one that I bumped into a while ago: Feedbin, although I haven't tried it. It's web based and it costs $5/month but it has a 30 day trial period. It works also through third party apps on Android and iOS (well, the latter seems to have a dedicated one by themselves).

There’s a RSS feed which you can use with something like feedbin.com

Links and Show Notes:More Power Users: Ad-free episodes with regular bonus segmentsSubmit FeedbackApple Releases iOS and iPadOS 16.4 with New Emoji, Notifications for Web Apps on the Home Screen, Voice Isolation for Cellular Calls, New Shortcuts Actions, and More - MacStoriesReadwiseKindle ScribeAmazon.com: How to Calm Your Mind by Chris BaileyMac Power Users #550: The World of RSS - Relay FMReadwise ReaderReeder 5FeedbinSubscribe to Email Newsletters in FeedbinGoodLinksThe Disney Bundle: Stream Disney+, Hulu, and ESPN+YouTube TVJustWatch AppCuriosity StreamYouTube PremiumCGP Grey - YouTubeHands-On With Apple's New Classical Music App - MacRumorsOvercastLibbyThree Thoughts Spurred by a Random iOS 5 Screenshot – 512 PixelsStephen Hackett (@[email protected]) - eworld.socialMacSparky (@[email protected]) - MastodonSofa: Downtime Organizer

I can recommend https://feedbin.com/ as a great replacement. It's $50 a year, but in return you get a service that is rock solid with an owner who is luckily very good in >> not << implementing features: no feature creep, no breaking changes, no BS.

I enjoy using Feedbin, as it's not only my own newsfeed for blogs, but it also supports Twitter too. The interface has a clean, thoughtful design which is really important for me.

I no longer self host it, but there is a community contributed Docker Compose stack for Feedbin.

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Mastodon DMs have absolutely no privacy: https://github.com/mastodon/mastodon/issues/18079

For a decentralized protocol doing things right is much more important than doing things fast, it is very difficult (and in a lot of cases impossible) to break backwards compatibility.

Postmortem on what happened here: https://news.ycombinator.com/edit?id=39305884

The v1 API of Mastodon limits the size of the tree that it will expand for users who are not logged into the server: https://github.com/mastodon/mastodon/blob/main/app/controllers/api/v1/statuses_controller.rb . I am guessing that this or some similar limit applies to threads being returned to unauthenticated users of the web UI. It just arbitrarily stops expanding the replies at some point, including the main thread from the OP.

If a thread is truncated, users expect it to expand automatically and autoscroll when you hit the bottom. In my desktop browser, that does not occur, and there is no indication that there is more to see. This is the situation of the web interface as of Mastodon version 4.2.5.

The issue is very sensitive to observer conditions. If you are logged into the server, the behavior is different. If you use a Mastodon app instead of the web, the behavior might be different. As the tree expands, the cutoffs become different. If you look at the thread on a different Mastodon server, the tree is different because every server has its own view of the Fediverse.

HN needs a best practice for linking to Mastodon threads in a way that provides a consistent experience to HN readers. The average Mastodon server would be crushed by hundreds of HN readers grabbing the entirety of a huge thread all at once, so this might involve some thread-unroll-and-cache service. I tried https://mastoreader.io/ but it did not solve the problem.

Alternately, we push changes into the Mastodon web UI to warn users when they need to click to see more and assume that people will get used to the navigation.

Suggestions?

Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5

>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Mastodon is free and open-source. Go ahead and add the flag:

https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....

Didn't say anything about freedom of speech. And again: I'm not the one to talk to. I don't have any strong feelings on the topic, but if you do, you should take it somewhere that people who can do something about it will see.

I tried to find an existing discussion to help get you started, but couldn't. You can start one here: https://github.com/mastodon/mastodon/issues

It's easy to sit here on Hacker News and say "they should just..."

Coming up with a standard for an international project will be a long, noisy discussion. You'll tread on internecine conflicts you had no idea about. Old wounds from past related discussions will come out. People will soapbox.

This is why I have no interest in discussing it. It probably won't go anywhere in a place where it actually could. It definitely won't here.

I've written down how I set up my Mastodon server here. This includes some topics that seem not well covered currently:

- use nginx reverse proxy with the official nginx.conf [1], but with some changes needed for compatibility with docker

- use rootless docker, for security, together with bind mounts, for maintainability

- use compose, with some modifications to the official docker-compose.yml [2] that make life easier and are compatible with the reverse proxy

[1]: https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

[2]: https://github.com/mastodon/mastodon/blob/main/docker-compos...