Feature Requests

I just migrated from Blueskyfeeds where feeds held on to posts for 4 days, and with how small and niche a topic/community I have curated, sometimes there are only like a dozen posts in the last 2 days (which seems to be the limit for Graze). It would be useful for longer feeds that have lots of posts have their limit based on how long ago the post was made (current functionality), and shorter ones with less posts to hold on to posts either for a longer period of time, like 4 days, or hold on to a specific number of posts, like maybe 50, that wouldn't tax Graze's systems too hard. This way folks who only check their feeds for more niche topics every once in a while will have the ability to catch up on what happened over a longer period of time.

Just like the Editor mode by default on settings, collapsing the nodes should be on default if the user want it to be that way, so very long feed logic doesnt display a kilometric view when opening the editor.

On nodes that use starter packs and user lists to curate feed content, it would be helpful to have a counter on the right side of the node (proposed design pictured below) in order to help developers keep track of the number of users being used to curate their feeds, and to make sure that feeds on Graze are UTD.

Something that remains a limiting factor for algorithm development on Graze is feed algorithms are not user specific. No matter who a person is, when they look at a Graze feed they're still looking at the same algorithm that anyone else on Bluesky will see. One of the powers of social media is that we can build spaces that are UNIQUE to users and having greater tools to cultivate user-specific experiences on Graze would be incredibly powerful. I suggest creating a modifier on the Feed Sorting node at the top of feeds called "Social Circle" that will examine the posts in a feed and arrange them based on the proximity of a post/post-author to a user's social circle. There could be tools to define how far a post is from a person's social circle, and give feed developers tools to create blends of near-social circle posts and posts that are further afield but still popular and may be interesting for a user.

I have a feed with only images and I want to apply a regex filter that searches through both the post's text and the post's alt text, but as of now, the only way to do that is by duplicating the regex node which is not ideal given that every time I need to make an adjustment to the regex I need to adjust both nodes.

For the people who are running multiple feeds run from multiple accounts, being able to quickly toggle between different feeds without having to log out/log in each time would be incredibly helpful and make it easier to edit.

We have feed makers, but where are the label creators? Setting up an ozone and all that could be simpler and being able to do this with a tool would be nice. Then we could add these labeler services to our feeds (which I know support for custom labelers is on the roadmap) Some custom labelers allow automated assigning of labels (good labels we want). But some crowdsourced reporting functions for bad actors, maybe with manual review, etc would be great too.

I currently have a sticky post at the top of the Game Dev feed telling users how they can support the feed and remove ads. It'd be great to be able to remove this for users that are already patrons. This is related to https://grazesocial.canny.io/feature-requests/p/sticky-post-expiration-schedules-specific-users

we should get a little alert next to our feeds when/if a custom node used in the feed needs to be updated. ideally, if the node is used in multiple feeds, we would be able to update all of them with one click too.

When debugging a post, it would be really helpful to see where exactly in the regex string the post is getting filtered, either by highlighting the Regex term or some other way, like where the numbers appear on the side, state "filtered with regex term X". Would be very helpful on feeds where regex is a very important filtering tool but the list is very long.