←back to thread

190 points amichail | 2 comments | | HN request time: 0.42s | source
Show context
xena ◴[] No.42194530[source]
Custom feeds are really cool. I made a custom feed that shows every time someone said "sneak peak" instead of "sneak peek" on a livestream: https://bsky.app/profile/stealthmountain.xeiaso.net/feed/sne...

It's currently running either under my desk or in the living room on my homelab Kubernetes cluster. It's a fun little thing to look into every so often to get a vertical slice of humanity.

replies(1): >>42195572 #
1. warunsl ◴[] No.42195572[source]
Custom feeds really intrigue me. If I understand the API right, if you are an implementer of a custom feed, you need to expose an endpoint that the bluesky server can hit whenever a user wants to load content for that custom feed. And the endpoint that you implement will return the results. Does this mean that the implementer of this feed will have to take into account the network costs? What I am trying to get at is that if you implement a custom feed, you need to be aware that you are potentially looking at hitting your data caps on your internet provider if a lot of folks start consuming that feed. Do I understand this right?

I am aware that there are services that let you create custom feeds. But they are mostly for simple compositions like a feed for the following set of words and/or set of people, etc.

replies(1): >>42197739 #
2. xena ◴[] No.42197739[source]
You end up sending back post IDs that get hydrated on the server side, but yeah!

There's more complicated feeds, but right now the easy to make feeds are more prevalent because they're easy to make.