betaFeedback

WorksComputer Science

Middleware for Feed Recommendation in Practice: How Feed Creators Build, Maintain, and Sustain Custom Feeds on Bluesky

Abstract

Scholars have long proposed third-party middleware as an alternative to centralized algorithmic feeds: feeds built and distributed by independent feed creators. This vision saw no large-scale instantiation until Bluesky, a decentralized microblogging platform, introduced custom feeds in 2023. Although central to the middleware ecosystem, we know little about how feed creators understand their role, build feeds, and sustain them. Through interviews with n = 26 feed creators and third-party developers of feed-building tools, and analysis of n = 88,302 custom feeds, we identify two creator orientations—utility-providing and community-building. Additionally, creators struggle to maintain feeds that fully realize middleware ideals: they lack granular interaction data, receive little feedback, and lack technical expertise to act on either. Finally, creators sustain their feeds as unpaid hobbyists with little platform support and are divided on whether to monetize beyond covering costs. We conclude with design and policy implications for strengthening the middleware feed ecosystem.

Introduction

Social media platforms increasingly organize users’ online experiences through centralized, top-down algorithmic feeds. They determine what content is surfaced, prioritized, or suppressed, leaving users little ability to understand or meaningfully steer the logic behind what they see [2, 3, 39, 64]. In response, scholars have proposed an alternative vision of social media: middleware, an open, composable layer where users can choose among third-party services for core components of online experiences such as recommendation and moderation [28, 38]. This vision posits that opening recommendation and moderation to a competitive ecosystem of third-party providers would decentralize platform power over users’ online experiences [34, 36]. However, realizing these benefits also shifts challenges of governance, accountability, and sustainability from platform providers down to middleware operators [38, 47].

While many have written about this vision, only in the last few years has it taken shape at scale. On Bluesky, a decentralized microblogging platform built around the goal of enabling user-driven “algorithmic choice” [65], platform developers instantiated a feature in 2023 called custom feeds, which allows users to freely create, govern, and distribute feed recommendation algorithms on the platform [40]. As this custom feed ecosystem grew, several new user roles arose to support custom feed infrastructure, including feed creators who author and maintain feeds, feed contributors whose content populates various feeds, feed consumers who subscribe to and browse feeds, and third-party developers who build tooling that supports feed creation and hosting. As of writing, Bluesky has grown to over 45 million total users and more than 100 thousand custom feeds [15, 16]. We thus argue that the custom feed ecosystem on Bluesky represents the first large-scale instantiation of third-party middleware for social media feed recommendation.

Despite being central to this middleware ecosystem, feed creators remain understudied beyond a few quantitative characterizations of the broader ecosystem [8, 26, 56]. These analyses find that feeds are created and sustained by a

relatively small population of creators, making it all the more important to understand their motivations, work, and challenges. While much research has studied community moderators on platforms such as Reddit or Discord [60, 68], feed creators occupy a fundamentally different space with distinct interactions and user expectations from those community settings. As such, we ask the following research questions:

  • RQ1: How do feed creators understand their role, and how do these orientations manifest in user activity across the custom feed ecosystem?

  • RQ2: How do feed creators and third-party developers build custom feeds and what tradeoffs shape their choices?

  • RQ3: How are feed creators and third party developers maintaining and sustaining the custom feed ecosystem over time?

To answer these research questions, we interviewed n=24n = 24 Bluesky feed creators and n=2n = 2 third-party developers of feed-related tools and conducted a large-scale analysis of n=88,302n = 88,302 custom feeds. We identify two distinct orientations of feed creators—utility-providing and community-building—that reflect distinct goals, maintenance practices, and relationships between feed creators and consumers. Despite the ecosystem’s open architecture, we discern dynamics in power: Bluesky retains privileged access to interaction data that custom feeds cannot yet match, and only a handful of creators hold the technical expertise to build powerful feeds beyond third-party tooling. At the same time, the ecosystem is sustained entirely through volunteer hobbyist labor, with creators and third party developers absorbing both the time costs of maintenance (e.g., promotion) and the financial costs of sustainment (e.g., server hosting). We conclude by offering a framework of power in the custom feed ecosystem and design implications for improving the current custom feed ecosystem and future middleware-based social media systems.

Algorithmic Feed Curation

While early social media platforms deployed content in reverse chronological order [49, 70], today, popular social media platforms such as Facebook, YouTube, and TikTok have adopted algorithmic recommender systems that curate content by learning from behavioral signals to maximize user engagement [7, 17, 23]. Despite their popularity, these systems have drawn criticism for providing users limited control over their feeds [25, 62, 67]. This is exacerbated by the fact that many users are not aware of available options for personalizing their opaque feeds [35, 54]. Additionally, because these systems reward content that performs well by their metrics, creators are pressured to shape their posts to perform for the algorithm rather than for their communities, a dynamic found to homogenize content across creators [41, 44] and narrow the diversity of content and communities on a platform [50].

These problems have motivated a range of alternative efforts to shift feed curation away from a platform’s engagement-optimized recommender systems. One direction encodes human values beyond engagement into a feed’s ranking objective [12, 37]. Because platforms have little incentive to adopt these objectives, such interventions are in practice deployed on the client side, re-ranking or rewriting the feed a platform has already delivered according to values drawn from the literature [42] or each user’s own criteria [58, 66]. While these modifications could give users increased agency over centralized recommendations, they are fundamentally limited by the subset of content surfaced by the platform’s recommenders in the first place. An adjacent line of work focuses on enabling users to build their own personal feeds from the broader pool of content available on the platform. Users can communicate their preferences through varied ways, from explicit filter controls [13], in-situ feedback during browsing feeds [22], to natural language [46, 55]. Yet these interventions require both upfront and continuous configuration from users themselves as their interests evolve [10].

Such effort is poorly aligned with the entertainment-oriented nature of feed consumption, especially since users may not have a clear articulation of their preferences.

Lastly, distributing content curation to third parties or crowdsourcing is a common but less visible way to build a feed. This ranges from curation by a single source, such as a personal blog or a followed account, to curation aggregated across many sources, as when journalists curate news feeds for their audiences [5]. Crowdsourced venues such as Reddit subreddits, Stack Overflow forums, and Slashdot posts represent a further variant of this, where curation emerges from a community rather than a single curator [21, 43, 53]. More recently, these ideas have been formalized into a model for collaborative feed curation, in which users democratically delegate curation to trusted people or communities rather than to a platform whose incentives they distrust or to themselves alone [32]. These examples suggest that a promising space of intervention lies between the platform and the individual end user.

Third Party Middleware for Social Media

In light of these developments, scholars have long been interested in a vision of third party middleware for social media that would offer composable components that interoperate under an open networking protocol [28, 38]. In theory, middleware could allow core components of social media, such as recommendation and moderation, to be hosted by third party providers and developed through standardized protocols instead of centralized platforms [47]. For example, a recommendation provider could access a platform’s content through its open protocol and apply its own ranking logic to compile feed recommendations, while a moderation provider would return whether a post aligns with their respective moderation rules instead.

The potential benefits of middleware are substantial. Middleware enables an ecosystem of competitive services where users choose between services that best fit their needs [34, 38]. Different communities could encode their own values into third-party services, such as a racial-justice-oriented lens from a civil rights organization, a fact-checking layer from a trusted news source, or a family-friendly version of an otherwise unfiltered feed [38]. This ecosystem could also result in a greater diversity of content on the platform and a proliferation of diverse communities [36]. Lastly, middleware could serve as a counterweight to misinformation and unaccountable state power, as scholars have theorized that concentrating curation and moderation in a handful of platforms has made it easier for governments to pressure those platforms into suppressing disfavored speech [28].

However, realizing the benefits of middleware in practice holds distinct challenges. Importantly, middleware would require lending users’ data, previously centralized and secured by a single platform, to a growing number of third-party developers, introducing privacy and security vulnerabilities with these new points of access [47, 71]. Middleware is also demanding cost-wise, as third party providers would be expected to host and serve independent technical infrastructure, and it remains unclear what would incentivize them to take on this work [38]. Perhaps most fundamentally, it is unclear whether third party middleware could compete with centralized recommenders. Today’s billions of social media users are accustomed to large-scale personalized recommendation [6], and third party providers would need to build and run the algorithms and infrastructure required to match it reliably at that scale. Removing a clear centralized algorithm might therefore deteriorate the quality of users’ online experiences and introduce confusion or decision fatigue [34].

While the literature enumerates distinct challenges for fully realizing the ideals of middleware, today’s social media platforms already exhibit roles and tools that partly align with the goals of middleware, despite not fully satisfying its tenets. For instance, Jhaver et al. argue that community moderators could be considered middle level providers of governance (e.g., on Reddit subreddits and Discord servers) [36]. Similarly, community-maintained blocklists that used to be on Twitter1 (now X) could be seen as providers of moderation, allowing users to filter unwanted content for others beyond what the platform moderates [29]. However, these systems are supported in-house, removing technical and cost barriers associated with self-hosting as well as many security and privacy concerns; this also leaves them more beholden to and limited by the platform. Even fully protocol-based approaches have only partially realized the ideals of middleware: Mastodon’s ActivityPub limits feed curation to personal filters and server policies rather than shared, third party, user-built infrastructure [4, 45, 57]. While some newer tools such as Graffiti attempt to push composable curation and moderation entirely to a client-side API to avoid infrastructure costs, they currently struggle to support complex feed recommendation algorithms [33]. More closely, Compass suggests a hybrid model in which a platform-provided base recommendation algorithm remains responsible for large-scale personalization, while users could layer lightweight continuously-updated customizations on top, pointing towards a middle ground between platform-controlled and user-created feeds [10].

Together, these examples show that middleware-like roles support governance and moderation in some limited ways natively on social media, yet few platforms have significantly opened up their core services to third parties. In this work, we focus on Bluesky custom feeds to study the potential of third party middleware for algorithmic feed recommendation.

Custom Feeds and Algorithmic Choice on Bluesky

We argue that custom feeds on Bluesky represent the first widely used instantiation of third party middleware for feed recommendation at scale [1]. Bluesky’s vision of “algorithmic choice” parallels the goals of middleware, aiming “to offer an open and diverse marketplace of algorithms in which communities can adapt the system to suit their needs, and users have more agency over how they spend their time and attention” [40]. To do so, custom feeds are implemented on Authenticated Transfer Protocol (ATProto), Bluesky’s open-source decentralized networking protocol [24]. We define several roles users play in supporting custom feeds within this ecosystem (see tbl:1).

Particularly, custom feeds differ from prior instantiations of third-party curation (e.g., journals, blogs, subreddits) in that they are not just curated by a trusted individual or community, but implemented as an explicitly shareable and publicly subscribe-able algorithm within an open protocol. Any user can create, discover, and adopt a custom feed, and any developer can build tooling which supports the functionality of custom feeds [24]. Beyond other middle-level actors [36], feed creators can directly author and maintain an algorithm rather than simply selecting, modifying, or creating content—making them also algorithmic providers for communities. Bluesky also does not at the moment natively support custom feed creation within its own web application,2 so custom feeds must be built off-platform by third-party tooling [65].

Due to the public nature of ATProto, recent large-scale quantitative analyses have confirmed that third-party tools such as SkyFeed hosted 85% of all Bluesky custom feeds in 2024 and that keyword-matching feeds dominate the ecosystem [8, 56], raising questions of what benefits custom feeds bring compared to existing similar features such as hashtags on YouTube or TikTok. Other work has investigated how users leverage general Bluesky moderation practices, such as starter packs for bootstrapping social media migration, and moderation practices for individual users and communities through vetted blocklists [9, 18, 51, 63]. However, prior work has not built a concrete understanding of feed creators themselves. We understand little about who are feed creators, how they build and maintain custom feeds,

UserRole
Feed CreatorA user who builds, maintains, and sustains a custom feed, either through using a third-party tool, or directly via the ATProto API.
Feed ContributorA user whose content appears in a custom feed, either knowingly (e.g., by including a designated hashtag in their post) or unknowingly (e.g., when their posts match a keyword filter set by a feed creator).
Feed ConsumerA user who pins, likes, or otherwise views a custom feed’s content without necessarily contributing to it. Akin to a subscriber.
Third Party DeveloperA developer who builds and maintains third-party tools supporting custom feed creation (e.g., SkyFeed, Graze, Bluesky Feed Creator (BFC)). Distinctly, these are not feed creators who implement their own infrastructure for custom feeds, but third party feed building service providers across the ecosystem.

caption: tbl:1. Definitions of four key roles within Bluesky’s custom feed ecosystem: feed creators, feed contributors, feed consumers, and third-party developers. We order these roles top-down by their level of involvement in an individual custom feed.

:::

and why and how they sustain their custom feeds over time. Feed creators are key to Bluesky’s vision of algorithmic choice [65], yet they remain the least understood role in the custom feed ecosystem; thus, our work aims to fill this gap.

Method

We conduct a mixed-methods study, with qualitative analysis of semi-structured interviews with feed creators and third party developers of feed tools, coupled with a large-scale quantitative analysis of all publicly accessible custom feeds on Bluesky.

Feed Creator Interviews

We conducted interviews over Zoom with n=24n = 24 Bluesky feed creators and n=2n = 2 third party developers. All participants were compensated with an online gift card at a rate of $20 USD per 45 minutes and $30 USD per 60 minutes, except four participants who voluntarily declined compensation. Our study protocol was approved and deemed exempt by our institutional review board.

3.1.1 Recruitment. We recruited participants primarily on Bluesky itself through two calls for participation posted in April 2025 and October 2025, which spread naturally through dissemination on the platform. We also posted calls for participation on Discord servers and Reddit subreddits that facilitate discussion related to Bluesky. Based on a public list of top feeds,3 we also directly messaged or emailed feed creators. We pre-screened participants to ensure that all participants held experience in creating custom feeds as a feed creator or developing third party tools for custom feeds.

We designate each participant a numerical ID according to their role of feed creator (C1–C24) or third party developer (D1–D2). Our set of feed creator participants maintained a diverse range of custom feeds. Three had 10,000+ likes, seven had 1000+ likes, nine had 100+ likes, and five had < 100 likes. Feed topics varied from casual hobbies (e.g., art, gaming) and fandoms (e.g., anime, streaming) to professional communities (e.g., science, news reporting). Our two third party developer participants built two of the most widely used third party tools on the platform; specifically, D1 is the lead backend developer of one and D2 is the solo full-stack developer of the other. We report participant details in Table 2 and demographics in Appendix A.

Table 2. We lay out our 24 feed creator interview participants, including the third party tool they used, intended feed purpose, orientation, feed likes, feed logic stated in interviews, and a description of their feed. Creators who implemented their own custom feed infrastructure and/or feed logic instead of using a common third party tool are marked as N/A.

IDToolOrientationLikesFeed LogicFeed Description
C1N/ACommunity1000+KeywordsA custom-built feed serving scientists and science communicators, with a team of user moderators for specific subfields of expertise.
C2N/AUtility100+Personalized algorithmA custom-built personalized recommendation feed that draws on user-specific data by custom implementation.
C3SkyFeedCommunity100+KeywordsA fandom feed using hashtag-based keyword matching, actively curating fanart and community content.
C4GrazeCommunity<100KeywordsA fandom feed for a popular video game, migrated from SkyFeed to Graze to support community features.
C5GrazeCommunity1000+KeywordsA hobbyist nature topic feed using emoji and hashtag keyword matching, managing spam and self-promotion.
C6SkyFeedUtility<100KeywordsA simple political topic feed to catch discussion of these posts, primarily set-it-and-forget-it in their maintenance approach.
C7BFCCommunity1000+KeywordsAn cross-disciplinary feed of multiple topics welcoming community contributions and enforcing content standards.
C8N/ACommunity10000+Keywords, User ListsA custom-built community feed using a self-hosted algorithm and infrastructure, enabling users to self-add and self-post via hashtag.
C9SkyFeedUtility10000+Keywords, User ListsA high-traffic curated news feed, focusing on delivering quality journalism and curated content.
C10SkyFeedCommunity100+KeywordsA scientific-adjacent feed drawing from contributor-curated images and publications.
C11SkyFeedCommunity1000+KeywordsA literary fandom community feed, attracting popular power users and fostering fandom discussion.
C12GrazeCommunity<100KeywordsA streamer fandom feed, displayed live on stream and requires DM-based onboarding in a bilingual community.
C13SkyFeedCommunity100+KeywordsA board game and fighting game community, actively welcoming newcomers who discover the feed organically.
C14GrazeCommunity1000+Keywords, User ListsA popular crowdsourced social feed where users trigger inclusion and discussion by replying to posts with a specific keyword.
C15GrazeUtility10000+KeywordsA high-traffic news feed based on a vetted allowlist of verified organizations, mentioned transparently with ads.
C16GrazeCommunity1000+KeywordsAn art feed which surfaces content from new creators under a follower count, enforcing a no-AI policy.
C17BFCCommunity100+KeywordsA gaming feed with active livestreaming events, onboarding new members and using labeler functionality to manage AI-generated content.
C18BFCCommunity1000+KeywordsA hobbyist image-forward feed using emoji-based keyword matching, with a set-it-and-forget-it maintenance approach.
C19GrazeCommunity100+KeywordsA professional academic feed using custom labeler functionality, serving multilingual and specialized audiences.
C20GrazeCommunity100+KeywordsAn art feed using hashtags, enforcing strict content standards including a no-AI/NFT policy with banning for violations.
C21GrazeCommunity100+KeywordsA children’s illustration feed using hashtag keyword matching, primarily used by professional illustrators and publishers.
C22SkyFeedCommunity<100KeywordsA scientific feed using hashtag keyword matching, which has seen limited growth since its creation.
C23BFCCommunity<100KeywordsAn art subgenre feed for photography and artwork with minimal ongoing maintenance and contributors posting sporadically.
C24GrazeCommunity100+KeywordsA gaming fandom feed covering fanart and community events; creator actively onboards and promotes the feed to new community members.

Table 2.

Manuscript submitted to ACM

Table 3. We lay out our two third party developer participants, who had built two of the most widely used third party tools on Bluesky.

IDFeeds HostedTool FeaturesTool Description
D11000+block-based algorithm building, moderation support, monetization, ML rankingsA free third-party tool supporting keyword matching and machine learning ranking, with monetization options for feed creators.
D21000+keywords, regular expression-based algorithm building, labeler supportA free no-code, regular expression-based feed creation third party tool responsible for a sizable percentage of all custom feeds on Bluesky.

Table 3.

Study procedure

Each interview was conducted by two study team members, a primary interviewer and a notetaker, with one team member serving as primary interviewer for the majority of interviews. In each interview, we discussed participants’ motivations for joining Bluesky, their experiences creating and growing their feeds, and thoughts they had on the future of custom feeds and Bluesky as a whole. We detail our semi-structured interview protocol in Appendix B.

After all interview sessions were conducted, one study team member downloaded each meeting transcript as a raw text file from Zoom, lightly edited each transcript for clarity, and thematically coded participant responses [20] on an online whiteboarding tool.4 Three study team members met weekly to discuss emerging themes and align on progress.

Data Collection

In alignment with related work [9, 56], we built our custom feed dataset by scraping all accessible ATProto user decentralized identifiers (DIDs) from 146 known personal data server (PDS) instances5 through the Bluesky Relay in January 2026. We used the atproto.sync.listRepos6 endpoint, yielding a set of 33,199,368 unique DIDs representing 31.8M active and 1.4M inactive accounts. While public statistics at the time tracked ∼40M+ total Bluesky users, this discrepancy may stem from accounts hosted on PDS instances outside our set of 146, or accounts registered but not yet propagated through the Relay at our time of collection. We then directly scanned ATProto repositories and extracted custom feed records created by users from our set of DIDs using the getActorFeeds7 endpoint. We collected the feed DID, the feed creator’s DID, the feed creator’s domain handle, the feed creation date, and likes at the time of collection. These requests ran asynchronously on four NVIDIA 2080ti GPUs via our university cloud computing cluster, ultimately yielding n=97,719n = 97{,}719 unique feed DIDs. We provide a sample JSON object of each feed’s metadata we collected in Appendix C.

Collecting custom feed metadata

To collect further metadata from our set of custom feed DIDs, we performed a second large-scale data collection using publicly accessible endpoints from ATProto API. For each of our n=97,719n = 97{,}719 feed DIDs, we collected (i) the complete set of users who had liked the feed, (ii) metadata for up to the 500 most recent posts in each feed, including authorship, timestamps, replies, quotes, media, languages, and engagement statistics, and (iii) the set of users who interacted with those posts through likes and replies. We use users who liked a feed as a proxy for feed subscribers. This is our best proxy of a traditional subscriber because ATProto currently does not provide any signal as to whether a user has pinned or viewed a feed explicitly.

For each feed, we then identified the unique sets of users who had either liked or replied to the post as post likers and post repliers. We define an active consumer as a user who appears in both i) the feed’s subscriber base and ii) the set of all unique users who have liked a post on the feed within the 500-post window. We additionally formulate an active consumer participation rate for each feed as the intersection of post likers and post repliers over the total feed likers:

active consumer participation=Feed Likers∩(Post Likers∪Post Repliers)Feed Likers\text{active consumer participation} = \frac{\text{Feed Likers} \cap(\text{Post Likers} \cup\text{Post Repliers})}{\text{Feed Likers}}

Custom feed dataset and summary statistics

After discarding feeds that did not return any metadata, our final dataset comprised of n=88,302n = 88{,}302 custom feeds created by n=41,955n = 41{,}955 unique feed creators. The median creator maintains one feed (with mean being 2.1 feeds per creator). Of our feeds, 49,069 had at least one subscriber at our time of collection, with 1,319,921 total likers for all feeds. The median feed had just 3 subscribers, while the mean was 26.9 and the maximum was 50,757. The majority of feeds (77.0%) had between 1 and 10 subscribers, 20.2% had between 11 and 100, 2.5% had between 101 and 1,000, and only 0.2% (n=121n = 121) exceeded 1,000 subscribers (see Appendix D). These summary statistics are consistent with prior quantitative analyses that suggest the custom feed ecosystem largely consists of smaller individual feeds with a handful of high-visibility feeds [56]. This dataset enabled us to characterize creator activity, consumer participation, and the structural properties of custom feeds at ecosystem scale paired with our qualitative findings.

Findings

Characterizing Feed Creators and Feeds

Two ways feed creators see their role: utility-providing and community-building. Through our interviews, we inductively derived two orientations that custom feed creators expressed towards their custom feeds. We term these utility-providing and community-building. Each orientation captures how creators understand their role, how they curate their feeds over time, and what their feeds’ success means to them. Below we define and characterize these orientations in more detail.

  • Utility-providing creators treat their feed primarily as a content delivery mechanism for consumers. In their feeds, the typical consumer is foremost a follower of the feed and need not contribute posts to the feed’s content. A utility-providing feed creator desires to surface relevant content on Bluesky to the feed, and feed contributors may not even be aware that their content is being sourced for the feed.

  • In contrast, community-building creators support feeds that foster consumers interacting with each other. In these feeds, feed consumers themselves are the primary contributors to the feed. Instead of serving simply as a source of information, these feeds support communities around shared interests. In many cases, they support existing communities that predated Bluesky, helping consumers find each other on a new platform.

We note that these orientations loosely map onto prior theoretical work on community types, such as bond-based versus interest-based communities [59]. At the content level, utility feeds function similarly to traditional communities of interest [27] or networked publics [19], optimizing for information routing, discoverability, and passive consumption across a large audience. In contrast, community feeds operate closer to communities of practice [69] or intimate publics [11], relying on mutual engagement and a shared social repertoire. Furthermore, this distinction extends to the feed creators themselves. Drawing from Seering et al.’s metaphors in moderation [60], community-building creators seem to embody values of a Gardener as tending to a community, while utility-providing creators function closer to the Filter, as engaging less with community members and oriented towards screening out problematic content or users.

Feed creator tasks and measures of success: “set-it-and-forget-it” versus community steward

Unsurprisingly, the two feed creator orientations have distinct ideas about the tasks they should take on. Utility-providing creators passively view their feed as observers or focus their efforts on curating content, without asking subscribers for feedback. Creators described this approach as “set it and forget it”, where they configure the feed’s logic upfront and then step back. As a result, these creators measure success largely by whether the feed does its job of surfacing relevant high-quality content. Some utility-providing creators additionally described seeking to improve information access for their subscribers. For example, C9 maintains a news sourcing feed that provides access to articles behind paywalled publishers. Their role “is not to make money or get personal attention” but instead to “enable people to connect with actual news, as opposed to being captured by whatever happens to be free and pushed to them.”

Community-building creators instead act as the steward of spaces where consumers can interact with each other through the feed. For example, C14 maintains a feed where consumers directly use a hashtag to forward content to the feed; C3’s artwork feed welcomes contributions from consumers themselves to share their artwork with each other, not just sourcing posts via hashtag filters from across the network. This role require more sustained involvement, including tasks such as onboarding new members, moderating content, and actively participating in the feed themselves:

“I almost see myself as the librarian. If we’re in a library, I’m the librarian behind the desk. I’m making sure people aren’t yelling, they’re picking up their trash, and putting books back where they’re supposed to be. I’m making the place as presentable and welcoming as possible.” —C19

Community-building creators measure success relationally, e.g., whether consumers found each other, felt welcomed, or discovered a community they didn’t know existed on the platform. “I feel achievement in the fact that it gives people looking to find the [feed topic] community a pretty quick and easy way to do it, without having to be included in a starter pack or a list. It’s open for basically anybody to be like, "Oh, I like [feed topic]," and get their post seen. That part, I do feel proud of” (C11).

How feeds got started and evolved: from replication and migration from other platforms to new experiments in feed curation

We found that many feed creators got their start in one of two ways. First, in the early days of Bluesky, creators explained that it was difficult to find content that catered to their specific interests. As such, they made feeds purely as an easier way to curate content for themselves, without initially seeking to share with other users: “*I was just excited by the idea of having control, so I would create, unpublish, and delete feeds just for the hype of it.” (C6). They then realized that because their feeds are public, they could curate content not just for themselves but also for other users. Coupled with Bluesky moving out of invite-only access, creators recognized that they could use feeds to replicate features from existing social media platforms (e.g., Twitter, Reddit, Discord). Soon, these creators began expanding their feeds towards wider audiences. Many feeds that got their start this way have a feed logic that relies on simple keyword matching, where any post containing a chosen term or hashtag is automatically surfaced (e.g., C5, C18). Over time, other feeds have adopted a more deliberate curation: feeds that filter posts only from a vetted list of contributors (C1), surface high-quality journalism from selected sources (C9), or even personalize content for individual consumers (C2). Together, these forms span a spectrum from feeds that broadcast a creator’s personal interests platform-wide to feeds whose value comes from careful or complex curatorial gatekeeping.

While the first way maps onto utility-providing feed creators, the second way maps to creators seeking to build or recreate community. As Bluesky is a relatively new platform, many creators initially sought to migrate existing communities from other platforms onto Bluesky. For example, C11, who maintains a reading community, stated: “The community existed long before social media—back in forums, even before the internet was widespread. But specifically, I was trying to court the people from [genre] Twitter and help them find each other again, and also just to capture anybody who likes [genre] novels.” Over time, as the community grew, creators also sought to bring in new members. For instance, C13’s feed catches posts with any keywords related to their hobbyist board game community. Since this catches any discussion on Bluesky related to their topic, the feed can draw engagement from new contributors:

“The great thing about these feeds is that even if you don’t know about the feed, your posts are still in it. So somebody will be like, "I want to learn about [board game]," and anyone can just jump in, and this complete stranger has found us and is invited into the community.” –C13

Some community-building creators devised new social mechanics to shape how people participate in their feeds. For example, C17 built a feed that surfaces content from contributors below a certain follower threshold, where a community of users then amplifies content from these new users rather than established ones on Bluesky. C14 took a different approach, building crowdsourced feeds where any consumer could take part in feed curation: if you replied to a post with a specific keyword, that post would automatically go to the feed, leveraging comment engagement itself as a curation mechanism.

Feed creator orientations as a lens onto differing user activity around feeds.

The two main feed creator orientations provide a useful lens for us to better understand differences in activity around feeds. We find that many custom feeds on Bluesky operate without active participation from feed creators or consumers. Across n=88,302n = 88,302 feeds, 67.5% (n=59,582n = 59,582) did not include any posts authored by the feed creator in the last 500-post window (see Figure 3). We also found that most feeds had no active consumers (78.8%), by our definition in §3.2.1. While not always the case, this behavior more closely aligns with the utility-providing orientation, where the creator produces the feed algorithm but does not create content for the feed or seek to foster engagement among consumers. This suggests that most feed creators are operating from a goal of providing utility.

Proportions of creator and consumer engagement across active custom feeds

Figure 3. Proportions of creator and consumer engagement across active custom feeds in our dataset (n=88,302n = 88,302). The left histogram illustrates the frequency of creators posting within their own feeds, while the right histogram displays the distribution of active consumer participation rates.

We also find that feeds with an active creator see higher levels of feed interaction. We define a feed’s average interaction per post as the mean number of total interactions (e.g., likes, reposts, and replies) across up to 500 of the feed’s most recent posts. Feeds with an active creator generated substantially higher median average interactions per post (median = 11.94, IQR=[4.00,36.32]IQR = [4.00, 36.32]) compared to those with inactive creators (median = 1.56, IQR=[0.00,9.22]IQR = [0.00, 9.22]) (see Figure 4). We confirm via a Mann-Whitney U test that this difference in engagement is statistically significant (p < 0.001). This suggests that higher levels of engagement occur in feeds where the feed creator is actively participating (i.e. where the creator likely sees themselves as community-building).

Figure 4. Boxplots of average interactions per post compared between feeds with inactive versus active feed creators. Feeds with active creators exhibit significantly higher average interactions per post. We omitted outliers above the 95th percentile for visual clarity.

Building Custom Feeds

While creators differ in their orientations and motivations for building their feeds, we found that they largely rely on the same set of third-party tools to build them, with technical complexity scaling up as curation needs grow. Table 4 summarizes these tools and their features.

FeatureSkyFeedGrazeBluesky Feed Creator (BFC)
Feed logicRule-basedRule-based + MLRule-based
ModerationRegex filtersBlock lists, labelersBlock lists, labels
Creator analyticsBasicAdvancedBasic
MonetizationNoneAdsDonations

Table 4. Overview of the most popular third party tools used by feed creators on Bluesky.

4.2.1 Nearly all feeds use keyword matching through third party tools. The majority of feed creators we interviewed (n=21n = 21) used a third party tool to create their feed or had eventually migrated onto a third party tool. Aligning with work in 2024 that found SkyFeed hosted 85% of all feeds on the network [56], creators explain that third party tools are simply the easiest and best way to create custom feeds on Bluesky, citing their favorites as SkyFeed, Graze, and BFC [14, 30, 61]. Creators describe that these tools offer customizable ways to add functionality to their feeds, and some creators chose specific third party tools for their intended use cases. C17, who built a community gaming feed, determined: “As much as I loved it, SkyFeed didn’t have the security I wanted, especially for a growing community. I didn’t just want a place for people to post; I wanted a place where I could curate certain things that shouldn’t be in the feed and block users. So I decided to use BFC. With that, you have terms, you have labels, and you can completely block bad actors from interacting with the feed. You can also link all your feeds, so if you block someone in one, you can block them in all.” This flexibility stems from the ATProto’s dynamic between third party developers, creators, and Bluesky as a platform itself. Creators have the freedom to choose from a range of options of interoperating third-party middleware providers, which differ from prior approaches: “It would be cool if more things were built into Bluesky, but I like that it’s flexible. Having that control is worth the trade-off of less direct support.” (C16)

While the actual feed logic for many custom feeds is commonly through defining keyword matching regular expressions (regex), creators evolved beyond this to designate lists of users whose posts would appear on the feed, as well as labeler-based features. Nontechnical feed creators also enumerated challenges with learning to use regex. Some creators fully admitted that while they had derived a basic working regex filter, they still were unsure of how the expressions exactly worked and therefore aim to touch their feed settings as little as possible (C21).

4.2.2 Creators devised functionality beyond keyword matching to enhance custom feeds. For creators who needed more precise control over who could post in their feed, keyword matching alone proved insufficient. Some creators evolved to maintaining vetted lists of approved accounts as their primary feed logic, such as a collective workout accountability group where the feed creator actively adds contributors by request (C18), or a news feed restricted to verifiable journalism organizations (C15). Unlike keyword matching, which surfaces any post matching a string, list-based feeds give creators control over whose contributions appear.

As feed creators grew familiar with third party tools, some developed more specific content filtering mechanisms to complement their feed building processes, such as for AI-generated imagery and misinformation. For example, C17, a feed creator who uses Graze for their feeds, built a popular labeler for AI-generated imagery, where their aim is “to always be neutral and factual: either it is or is not AI” (C17).

Many feed creators also desired more features from third party tools. While third party developers do try to meet all feed creators’ needs, some tasks can become unwarranted responsibilities for them. Specifically, D2 stated that they had to implement features that they originally did not want to but had to for the community, such as caching posts beyond seven days. D2 states, “I hate this feature because it makes my life harder. I have to worry about backups. But the demand was overwhelming.”

Some creators who did not have technical expertise but wanted to improve their feed logic beyond keyword matching had to ask for help to devise custom functionality to support their feeds. For example, while C19 was satisfied with their current level of feed functionality, their community required specific labeling functionality to which they had to reach out for help with: “The biggest limiting factor was for the labeler. There’s no simple tool for that like there is for feeds. It requires coding, so I had to ask people for assistance. But I’m comfortable with the technical expertise I have to run things currently. The community is looking for a basic place to talk and network, and to limit misinformation and harassment.”

4.2.3 Some creators find value in implementing their own feed infrastructure. While third party tools are used ubiquitously, three feed creators (C1, C2, C8) explained that they built their own custom infrastructure to support their custom feed. This was because third-party tools could not meet their needs; these creators wanted to operate on larger slices of available ATProto data and build more sophisticated logic for their custom feeds beyond the capabilities of existing third party tools. For example, C2’s feed is a personalized feed that draws from signals on who a feed consumer follows. They precompute personalized recommendations for each individual user’s feed and transitioned their storage from a serverless AWS Lambda instance to a hosted AWS EC2 cloud server to keep costs low. The freedom of working without a third-party tool and building directly with the ATProto provides C2 the ability to do “real recommendation work”:

“Recently, they made a choice to release interaction data to custom feed developers. Previously, we only knew that a user "liked" a post and that they used our feed around that timestamp, but we didn’t know for sure if they liked it while on our feed. Now, Bluesky sends us the same fine-grained data they use for their DISCOVER feed. This is a big difference because it allows us to do real recommendation work.” –C2

C8 faced a different limitation, as their feed logic was too complex to express through block-based tooling, requiring custom ranking, video support, trending detection, and community membership logic that no existing tool could handle together. They built their feed from scratch in Rust, implementing their own open-source ATProto client in the process, stating that they “had to scale the infrastructure to handle a massive increase in traffic, especially during major events, when the feed had to serve a million people at once” (C8).

These feeds illustrate that third party tools do not work for everyone. Creators always have the ability to implement logic beyond the relatively simple functionality that third party tools provide. Feeds that began as community projects like C8’s have grown into independent infrastructure, complete with moderation teams and protocol-level implementations that can function independently of Bluesky itself.

Maintaining Custom Feeds

Creators describe custom feed maintenance as ongoing work that introduces tasks specific to the feed creator role, extending beyond what prior research on online community moderation has documented [60]. Specifically, we identified two kinds of maintenance tasks: proactive tasks (e.g., evaluating analytics, updating feed logic) and reactive tasks (e.g., moderation, responding to user feedback). Notably, for utility-providing creators, their maintenance is infrequent, consistent with the common set-it-and-forget-it philosophy (§4.1.1). Community-building creators, by contrast, engage in substantially more ongoing maintenance work across both categories.

Feed moderation is supported by labelers and often anticipated beforehand. In utility-providing feeds, a feed creator’s moderation is largely reactive. Because utility-providing feeds focus on curating content from contributors that the feed creator is already familiar with, unwanted posts and rule violations can be anticipated beforehand and dealt with by exclusion criteria. Creators add block lists for known bad actors and connect feeds to third-party labelers that pre-screen content by type such as spam, unwanted ads, AI-generated imagery, or misinformation. Before these moderation features existed, creators oftentimes had to “manually find keywords and add hundreds of accounts to a blocklist to filter them out.” [C3], but now many creators have adopted these strategies across their feeds. As C24 explained, “If someone makes a new account to spam, it takes me one second to add them to the filter list. There are people who use the top 10 hashtags on every post to sell stuff like Amazon links. I filter those out by putting popular hashtags in the removal list if they appear alongside spam keywords.” –C24

In contrast, community-building feeds require more nuanced moderation. Because these feeds thrive on user interaction, moderation decisions carry social weight that content-based exclusions do not. Creators like C12 describe preferring corrective actions over permanent bans, recognizing that their relationship with community members matters more beyond a single violation: “On Twitter, removing someone from the community was a permanent, heavy-handed action. On Bluesky, I can remove a contributor from my feed’s list if they post something inappropriate, which removes their posts, but I can also add them back. This allows for a discussion, which is a big improvement.”

Community-building creators put in more active effort to maintain their feed community. Some community-building creators describe proactive promotion and engagement as an essential task to maintain a healthy feed, rather than waiting for potential consumers to organically discover their feed. While browsing other feeds on Bluesky, they actively scan their custom feed to detect new users and continue “onboarding new people to this day” by reaching out and introducing themselves as the feed creator. More extremely, C24 directly markets their fandom feed on Bluesky to potential consumers by persistently engaging with any relevant content on Bluesky: “I have been commenting on every single [fandom] post I find, telling them about feeds and how to set up their Bluesky accounts. I’ve sent thousands of messages. It works; people tell me, "I stayed on Bluesky because of your post." But obviously, that is not a sustainable strategy.”

Creators voluntarily choose to do this because they have found the feed discovery process ineffective and largely unsupported by Bluesky. C24 and six other creators expressed that Bluesky should support feed discovery as “new users on Bluesky have no idea that you can create or subscribe to custom feeds” (C24). For new users, other features on Bluesky (e.g., the Discover feed, user lists, and starter packs) compete for their attention, and that Bluesky as a platform fails to communicate the potential of custom feeds as an alternative to these more traditional social media features (C12, C20). Creators like C12 criticized Bluesky’s feed discovery as stagnant: “The feed discovery inside Bluesky itself is not great. It’s stuck in time. If you create a new account and go to the “Feeds” tab, you’ll see the same top feeds from two years ago. They are all in English and often about the U.S., so it’s not interesting for people outside that. This is one of my biggest pains.” –C12

4.3.3 Feed creators are responsive to feedback but rarely receive explicit feedback. All creators state that feedback of any kind is largely uncommon. To maintain their feeds, they must anticipate both implicit and explicit feedback from contributors and consumers alike.

  • Understanding implicit feedback. Because direct user feedback is rare, creators use third-party analytics as an implicit signal of feed health. This includes feed post likes, daily active users, total volume of posts captured by the feed (Graze), how often a feed is loaded (SkyFeed), and how many times the feed is opened (BFC). While this helps to get a sense of growth over time, creators recognize that this isn’t a directly actionable way to maintain their feeds: “These metrics don’t really affect what I do. I’m not trying to optimize for growth. Unless the numbers dropped suddenly, I don’t care too much about them. The feed is my own thing that I’m happy to share.” (C4) Creators largely treat these analytics as passive evaluations rather than metrics to optimize for.

  • Receiving explicit feedback. Because there currently exists no direct way for consumers to communicate with the feed creator through the feed itself, creators actively solicit feedback from workarounds such as through commenting under their pinned posts or through auxiliary channels (e.g., direct messaging, Discord, feedback forms). Creators reported acting on much of this feedback to improve their feeds, but emphasized that final decisions remain at their personal discretion. For example, C19 reflected on balancing community input against their own judgment: “People might get offended that I allow posts about Israel bombing hospitals. My argument is that this is medically relevant, and the suppression of that kind of speech is what made me leave other platforms.”

Sustaining Custom Feeds

We find that the task of sustaining a custom feed over time carries real costs in time, motivation, and money.

Creators’ sustaining motivations are directly from hobbyism.

Utility-providing creators tied their sustained motivation to a feed’s continued growth. Stagnant feeds tended to go unmaintained—C21 reflected that while starting their feed was exciting, keeping it going without visible momentum proved difficult. On the other hand, community-building creators are largely willing to sustain their feeds through ongoing personal investment, mirroring those of hobbyist moderators on platforms like Reddit and Discord [60, 68]. C23 framed this volunteer labor as central to Bluesky’s value:

“I think if they go away from hobbyists, they’re going to alienate the entire base that was cheering for Bluesky. I think it’s a quick way to do the “Vine upset,” where you build this community and then crash it because you don’t give back to the people that helped build it.” –C23

Creators were divided, however, on whether Bluesky itself adequately supports this volunteer labor. Some creators viewed the current hobbyist model well-aligned with the decentralization philosophy of Bluesky. As C16 acknowledged, “I feel like Bluesky absolutely could do more. But I’m also on board with their mission for people to build their own things.” Others, like C11, found the absence of concrete platform support alienating, since the motivation to sustain a feed had to come entirely from the creator rather than from the platform: “I don’t really feel any particular support from Bluesky. Maybe SkyFeed feels differently, or someone who set up their own server, but nobody from Bluesky ever reached out or did anything to help me.”

Creators distinguish personal monetization from ecosystem support

Most third party tools are free to use, and many feeds’ infrastructural needs are able to be fully supported by free features. However, some tools have monetized features that creators desire to be monetarily supported. For example, BFC follows a freemium model: basic feed setup is free, while a subscription unlocks more advanced capabilities such as additional post-capturing logic and translation [14]. Every 100 posts in a feed, BFC also inserts an ad that this feed was created with BFC which feed creators cannot remove. To cover the cost of premium tools like BFC, creators solicit community support through donation links (e.g., Ko-Fi), though creators state they do not personally take any of these funds and only use this to cover the cost of using a third party tool for the feed (C1, C6, C21).

Adjacently, Graze has introduced an advertisement marketplace where feed creators can monetize their feeds, with potential advertisers placing an ad on the feed set at the creator’s price [31]. Creators were divided on whether they should take advantage of it. Many felt that personal monetization should not be necessary for sustaining their feeds, particularly when doing so would profit off content they do not own (e.g., artwork). As C16 explained, “People who are going to monetize are going to need to bring something very special and not easily replicated. If your feed is just a simple string match for hashtags, like some of mine, people will just build the same feed themselves, ad-free.” These creators nonetheless accepted monetization that supported the infrastructure behind feeds. C21, for instance, cited paying for BFC and framed monetization in terms of cost recovery rather than profit: “It’s not about getting rich; it’s about covering the expense so I’m not paying out of pocket to help the community.”

A second group of creators went further, arguing that modest personal compensation can itself align with Bluesky’s ethos. C20, who maintains a community-building art feed, framed feed creator monetization as part of a positive community loop: “My feeling is that the person building and maintaining that feed has a right to ask for a couple of bucks. The people taking out ads on Bluesky are indie creators, authors, and self-publishing people. It’s not Jeff Bezos; it’s people giving $20 to place an ad. That’s supporting the creators, the feed builders, and the community. It’s creating a positive loop of dollars going through the community.”

C15’s utility-providing feed offers as a working example of this vision of monetization. This high-traffic news feed, one of the largest on Bluesky, has grown to sufficient scale to make advertising viable. All advertisers go through Graze, and C15 personally approves every ad, with ads making up roughly 2%2\% of posts in the feed. Each ad must also carry a specific hashtag for regulatory compliance, which doubles as a mechanism for consumers to opt out: “I’ve always been transparent about opting out. Users can just mute that hashtag if they want.” C15 estimates earning $2,000–$3,000 USD through Graze over the past year and donates roughly half of these funds back to ATPROTO development projects. They frame monetization not as personal income but as a mechanism for returning value to the ecosystem, putting C20’s positive community loop into practice.

In contrast, some third party tools are simply not monetarily sustainable. For example, D2’s tool hosts thousands of feeds on the ecosystem. Their tool has grown so large that it has become unsustainable to cover server hosting costs:

“For the past two years, I’ve used GitHub Sponsors, and about 150 users have supported the project. This used to cover most of the server costs. I also received a $1,000 grant from Bluesky once, which covered a couple of months. However, my primary goal has been to keep the service online as a hobby project, not to make money personally. Now, with the surge in growth around the U.S. elections, the server costs have become much more expensive, and donations no longer cover them. This is why I’m currently thinking about how to make the project sustainable, which might involve making it a full-time job and finding a way to pay myself in addition to the infrastructure costs.” —D2

Discussion

Decentralized Middleware in Practice: Power and Cost Asymmetries

The custom feed ecosystem offers a large-scale example of the middleware vision for algorithmic feed recommendation, giving actors beyond the Bluesky platform (e.g., third-party tool developers, feed creators, and consumers) direct agency in shaping how feeds are designed and maintained (see Figure 2). At the same time, our findings show that this ecosystem contains important asymmetries across these actors, especially in who holds control and who bears the costs of sustaining custom feeds.

Feed creator orientations: utility-providing and community-building; 4.1 Roles and Tasks; 4.2 Building Feeds; 4.3 Maintaining Feeds; 4.4 Sustaining Feeds. Utility-providing: Passive observers focused on content delivery and metric-driven success; Rely on third-party tools (SkyFeed, Graze, BFC) and keyword-matching regular expressions; “Set-it-and-forget-it” approach; relying on reactive moderation via blocklists and labelers; Motivated by feed growth; more open to covering costs via transparent ad monetization. Community-building: Active stewards focused on user interaction and relationship-driven success; Evolve to vetted allowlists, advanced labelers, or custom-built infrastructure on Rust or AWS; Proactive tasks (onboarding, active promotion) and nuanced, conversational moderation; Motivated by community health; sustained through hobbyist volunteer labor and donations.

Figure 2. An overview of our findings mapped along our two feed creator orientations. Both utility-providing and community-building feed creators show distinctions across how they understand their roles and build, maintain, and sustain their custom feeds.

5.1.1 Power asymmetries in platform and tooling control. Bluesky still retains several forms of power that remain inaccessible to feed creators and third-party developers. The most direct is privileged access to user data, since 98.9% of users’ data in 2024 were still hosted on Bluesky’s own servers (bsky.social) rather than on self-hosted alternatives [8]. As D2 explained, “The official Discover feed from Bluesky has a special advantage because it can collect a ton of interaction metrics (clicks, views, etc.) that third-party developers can’t.” Bluesky also exercises power through less visible interface choices, shaping how accessible custom feeds are to users. For instance, custom feeds are not prominently surfaced during onboarding or in the platform’s main UI (see Figure 1) and creators are frustrated with the lack of support from Bluesky itself to promote feed discovery.

Screenshots illustrating the Gardening custom feed on Bluesky

Figure 1. The Gardening custom feed on Bluesky. Any user can (A) choose to scroll through any number of custom feeds, (B) view specific posts under the feed such as the feed creator’s pinned post, (C) search for any feed to view on the platform, and (D) view the feed description, feed creator, and like, pin, or report the feed. Users can also (E) access their pinned feeds through an aggregated list from their profile. Screenshots were captured from the Bluesky web application on September 6th, 2026.

At the tooling layer, power concentrates around a small number of third-party developers whose design choices determine what features feed creators can use. The deeper asymmetry, however, stems from technical capability itself. Only three interviewed feed creators had the expertise to bypass third-party tooling entirely and build their own infrastructure. Most others struggled with even the regex-based filters that underlie these tools. Due to these power asymmetries at both the platform and tool levels, many creators were frustrated that their feeds would never be as popular or performant as Bluesky’s Discover feed despite the ecosystem’s formally open architecture for custom feeds. As we were finishing this paper, a personalized For You feed8 became the most liked custom feed on the platform, suggesting that within the ostensibly open ecosystem, the most popular feeds still reproduce prior centralized, personalized algorithms.

5.1.2 Cost asymmetries in sustaining custom feeds. Beyond power asymmetries, the custom feed ecosystem is sustained primarily through hobbyist labor, paralleling prior work on volunteer moderators on Reddit and Discord [60, 68]. In contrast to traditional content moderators, feed creators also must take on extensive additional work introduced by this new role, such as gathering user feedback and promoting their feeds, with, unfortunately, little platform support. Beyond time commitments, sustaining the ecosystem incurs financial costs as well, most notably the servers required to host curation algorithms and store user data. Third-party tools such as BFC shift some of these costs onto creators through subscription fees for advanced features. Creators either absorb these costs themselves or recover them through donations and, increasingly, in-feed advertising. While these efforts represent an early attempt to promote financial sustainability of this ecosystem, our interviews surfaced several unresolved tensions, such as whether feed creators are worth compensating for their personal efforts beyond infrastructure cost, and, furthermore, whether in-feed ads should be allowed in custom feeds even if they can align with the ethos of Bluesky.

5.1.3 Implications. Our findings suggest that improving and sustaining the custom feed ecosystem requires directly addressing the power and cost asymmetries that currently burden creators and consumers. Meaningful decentralization requires reducing both the power gap (concentrated data and tooling control) and the cost gap (disproportionate creator burdens), while avoiding interventions that would create new forms of centralization.

(1) Future decentralized infrastructures could separate data portability from data visibility. Interaction signals remain exclusively accessible to Bluesky’s DISCOVER feed, giving platform-operated feeds a structural advantage that third-party creators cannot close through feed logic alone. While Bluesky is alleviating this by starting to provide data to developers (as C2 mentioned), we posit that Bluesky could offer aggregated anonymized engagement data (e.g., which posts in a feed were clicked versus scrolled past) without exposing individual user behavior. Furthermore, there could be features in which feed subscribers voluntarily label posts and provide feedback on whether feeds are matching individual and collective preferences. These possibilities could provide data for creators to improve their feeds that does not infringe upon users’ privacy.

(2) AI-assisted features could significantly lower barriers to the technical complexity of feed creation. Researchers have found that conversational elicitation could help individual users articulate what content they want to surface or suppress for their custom feeds, and AI can assist with translating preferences into regular expressions or more advanced feed logic [46, 55]. We envision that such systems could similarly help feed creators author their custom feeds, and help feed consumers articulate their feedback more accurately. For instance, a tool could surface examples of content that a feed would include and exclude and verify with creators whether these match their intent. This would expand the design space for non-technical creators beyond what current low- or no-code tools support.

(3) Sustaining the custom feed ecosystem requires supporting feed discovery and creator maintenance work. Our findings suggest that feed discovery could be supported more directly by platform infrastructure, reducing the need for creators to self-promote. Existing third party websites9 aggregate feeds into topical lists for ease of search, but it is unclear how effective this is for individual users to discover feeds. A potential solution could be Bluesky utilizing a simple personalized ranking algorithm to recommend feeds based on user interests through their already public data as a complement to the DISCOVER feed. But we note that this can raise the question of who designs that ranking algorithm and by what criteria, reintroducing another form of centralized power over which feeds gain visibility. Additionally, we believe collective costs can be sustained through community-guided labeler, moderation, and monetization systems for creators to lower the operational burden of maintenance.

Characterizing the Feed Landscape Through the Lens of Powers

End users today choose among a broad and growing landscape of feeds: commercial personalized feeds curated by platforms (e.g., TikTok’s For You page), approaches that let individual users assemble feeds for their own consumption (e.g., Bonsai [46]), feed elicitation interviews [55], Compass [10], creator-built custom feeds like those on Bluesky, and established community platforms such as Reddit subreddits. These feeds differ less in the content they carry than in who is entitled to shape them, and how. Extending prior work that discerns platform power dynamics in decentralized social media protocols [52], we reflect on the feeds in our study, and characterize this landscape along three forms of power over a feed (see Table 5):

Feed ParadigmPower to HostPower to CuratePower to Contribute
Commercial feeds (e.g., TikTok, Instagram)Centralized platformCentralized platformAlgorithmic gatekeeping by platform
Custom feeds by utility-providing creators (e.g., C9, C15)Third-party tool or self-hostedFeed creatorRead-only for consumers
Custom feeds by community-building creators (e.g., C14, C19)Third-party tool or self-hostedFeed creatorDirect contribution (e.g., via hashtags or replies)
Personal feed tooling (e.g., Go [13], Bonsai [46], Compass [10])Client-side or self-hostedIndividual consumerLimited to a user’s personal scope

Table 5. A comparison of feed curation paradigms across three rights of feed governance: the right to host, the right to curate, and the right to contribute.

  • The power to host: control over the infrastructure a feed runs on, e.g., the servers that execute its logic and store its data.

  • The power to curate: authority over a feed’s selection and ranking logic—what content it surfaces. This power also depends on what data the actor has access to, and their engineering resources. A platform that observes every click and dwell time can curate in ways that a creator limited to public posts cannot.

  • The power to contribute: the ability to push content directly into a feed that others consume. Unlike the first two, this right is graded: a news homepage gives readers no way to contribute; feeds like TikTok’s For You page let anyone post but leave the odds of surfacing to the platform; and some feeds let contributors place content straight into what consumers see.

Where these powers sit distinguishes one feed from another, and further shapes what consumers experience. A commercial personalized feed like TikTok’s For You keeps all three with the platform: it hosts the feed, sets its logic, and tightly controls what users can contribute. This full power lets the platform build more effective recommendation feeds than any other actor can. Custom feeds, by contrast, pull these rights apart. Utility-providing feeds delegate hosting to a third-party tool while the creator holds curation, though consumers typically have no direct power to contribute to the feed. Community-building feeds extend direct contribution to consumers themselves. Personal feed-building tools, in turn, hand curation to individual users, who define a feed’s logic for their own consumption. Across these forms, custom feeds occupy a distinctive region of this spectrum, where the three powers rarely rest with a single actor. This decentralization comes at the cost of recommendation quality, but closing that gap would require the pervasive data collection that motivated many users to leave prior platforms in the first place. Viewed through this lens, the boundary between a feed and an online community itself begins to blur: a community-building feed, for instance, becomes hard to cleanly separate from a subreddit.

Holding Feed Creators Accountable: Transparency of Feed Logic and Its Trade-off

As custom feeds move the power to curate from platforms to feed creators, that power might now be exercised with far less oversight than platforms face. Some creators we interviewed worried that their feeds could easily be repurposed or acquired without subscribers knowing. C14 illustrated the risk by converting a joke feed into one about trans rights overnight while dozens of subscribers still had it pinned. Similarly, C16 worried that “I can come to you and say, ‘Hey, I’ll buy the feed off you,’ and no one would ever know. Then I could pivot it to my own content, my own agenda. It’s the same as when people sell their large Reddit accounts so certain opinions can get more traction.” Feed creators may also come to hold more of consumers’ interaction data than consumers would willingly share, especially as Bluesky has recently begun releasing fine-grained interaction data to feed developers (C2). D2 was wary of this direction: “I would prefer if this data wasn’t collected at all, as I dislike multiple entities being informed of my actions. I worry it will be used for personalized ads in the future.”

While the middleware ecosystem lets consumers keep their data and switch to a different feed, a more direct way to hold creators accountable for this power is to make their feed logic transparent to consumers. A central design question, then, is how much of a feed’s logic should be exposed to consumers. Today, consumers can only infer what a feed does from its description and its content; some third party tools publish the full definition of every feed they host, but most feeds expose nothing. Publishing feed logic would let consumers judge whether a feed still matches what they subscribed to and hold creators to their stated purpose. However, such transparency also invites abuse of the power to contribute: once contributors know the exact keywords a feed matches, they can insert them to push their own content into it, as creators already experience with hashtag spam. To address this trade-off, we envision exposing what a feed does rather than how it does it, for instance by showing sample posts it surfaces and suppresses.

Limitations and Future Work

We recognize two limitations with our work. First, we did not directly solicit perspectives from feed consumers or contributors. This is because we hypothesized that feed creators’ experiences would be a more representative view of the custom feed ecosystem. Existing third party tools are built for supporting feed creators and feed creators are publicly contactable from both the Bluesky web application and public lists of custom feeds, which supported our recruitment for creators rather than contributors or consumers. Our findings also highlight that communicating with consumers is difficult even for feed creators themselves. A promising future direction could focus on understanding consumer perspectives of custom feeds and algorithmic curation on Bluesky.

Second, our quantitative analysis does not aim to classify custom feed logic or algorithms at scale. While we attempted to run an LLM-based inference to classify custom feed logic based on feed descriptions and the last 500 posts in a feed, we could not draw meaningful conclusions from it. Many unkept custom feeds do not have descriptions to draw from or whose algorithm does not show many recent posts, and the vast majority of feeds still hold little to no indication as to how its’ algorithm functions. As Bluesky grows and draws more interest in research, we encourage future work to quantitatively categorize custom feed algorithms and logic at scale.

Conclusion

Custom feeds on Bluesky represent the first large-scale instantiation of a long-envisioned middleware-centered feed recommendation model for social media. By returning meaningful control over algorithmic curation to users and third-party developers, the growing custom feed ecosystem demonstrates that middleware can exist in practice for feed recommendation at scale, allowing users of all kinds to achieve new control over their online experiences beyond simply centralized algorithmic recommendations. Feed creators have built a diverse range of algorithmic infrastructure ranging from simple keyword filters to large-scale community spaces, sustained largely through hobbyist labor and third-party tooling instead of direct platform support.

However, our findings show that these middleware ideals remain only partially realized in practice. We find that power and infrastructural labor remain unevenly distributed across actors in the ecosystem, particularly stressed on third party developers and feed creator labor. This is exacerbated by gaps between what Bluesky provides for third party tool developers, the normalized roles of creators, and also compounded by tensions between personalization, transparency, and community-oriented curation. We enumerate future guidelines to support these visions, and we hope our work provides a foundation for future research and design toward more usable and sustainable decentralized social media ecosystems.

References

Participant Demographics

IDAgeGenderCountrySocial Media UseFeed Expertise
C135–44ManAustralia5–9Expert
C235–44ManUSA10+Expert
C318–24WomanUSA10+Competent
C425–34Prefer not to sayUSA5–9Competent
C525–34WomanUSA1–2Expert
C625–34ManUSA10+Expert
C735–44ManUSA10+Competent
C845–54ManCanada5–9Expert
C925–34ManUSA10+Expert
C1018–24ManGermany10+Expert
C1145–54ManUSA10+Expert
C1255–64ManUSA10+Competent
C1335–44WomanUSA10+Competent
C1425–34Non-binaryBrazil10+Competent
C1535–44ManUSA10+Competent
C1635–44Non-binaryUSA10+Expert
C1735–44Non-binaryUK10+Expert
C1635–44ManUSA10+Competent
C1725–34ManUSA5–9Competent
C1835–44WomanUSA10+Beginner
C1925–34ManUSA10+Expert
C2035–44WomanUSA10+Competent
C2145–54Prefer not to sayCanada10+Beginner
C2245–54WomanUSA10+Beginner
C2325–34WomanCanada10+Beginner
C2435–44WomanUSA10+Expert

Table 6. Study participant demographics. Participants were asked to provide their years of social media usage and rate their custom feed expertise on a four-point scale (Novice: Has no or minimal knowledge, Beginner: Basic knowledge of custom feeds, Competent: Good working or background knowledge, or Expert: Has in-depth knowledge and understanding).

Study Information

Interview Protocol

Motivations.

  • What inspired you to start using Bluesky as a social media platform?

  • How long after joining did you consider making your own custom feeds?

  • What kinds of custom feeds have you created on Bluesky?

    • What are their topics?

    • How many feeds did you create and how long did it take?

    • How did you initially start creating them?

    • Did you use any third party feed-building tools? If so, how was that experience?

    • Why did you decide to create a custom feed in the first place?

  • How long have you still been actively maintaining your first feed? Or any others?

  • What motivates you to still keep maintaining your feed?

Feed Metrics and Growth.

  • How many subscribers have your feeds attracted?

  • How many posts does your feed publish every day or every week?

  • Do you keep track of any specific feed metrics, such as interactions, engagement, or click-throughs?

    • If so, how does tracking these metrics help you understand growth or plan for the future?

    • Which metrics matter most to you?

    • Given all these metrics you track, what actually makes you feel like your feed is working or successful?

  • Have you been inspired to create more feeds after one took off?

Maintenance Tasks.

  • Can you walk me through what a typical week looks like maintaining your feed?

    • What tasks are you working on, and what improvements are you thinking about?

    • How easy or enjoyable is it for you?

  • Do you feel you can keep dedicating this time and effort to your feed? Do you wish it were more or less?

  • Do you see yourself doing this a year from now? Two years? Five years?

Moderation and Content Curation.

  • What kinds of unwanted content or behavior occurs on your feed? (spam, off-topic content, incivility, etc.)

    • How do you find this type of unwanted content?

    • Do your subscribers ever report content to you?

    • How often do you patrol or monitor your feed?

  • How do you deal with removing unwanted content from your feeds?

    • Do you use third party tools? Does Bluesky provide any support?

    • Do you then update your feed rules accordingly?

    • Have you ever encountered a case where someone tried to exploit your algorithm rules to get into your feed?

    • Do you ever consider moderating comments or interactions by users that have been viewed through your feed?

  • What is your perceived role in this kind of moderation?

  • Do you feel a sense of achievement or happiness curating feeds for your audience?

  • Are there moments of frustration in this process?

  • How do you communicate your feed rules or guidelines to your subscribers?

    • How transparently are your content curation rules communicated to your subscribers?

    • How do you balance the tradeoff and potential risks between communicating more or less of this?

Feed Collection Data

A sample JSON object we collected for each custom feed.

{
  "uri": "at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.feed.generator/thevids",
  "cid": "bafyreigsetw3cy2ryav7lwuzv7kwhh5ay7apnruva2ybsorsee7efzn4aa",
  "did": "did:web:discover.bsky.app",
  "creator_did": "did:plc:z72i7hdynmk6r22z27h6tvur",
  "creator_handle": "bsky.app",
  "display_name": "Video",
  "description": "Trending videos in the Bluesky network",
  "avatar": "https://cdn.bsky.app/img/avatar/plain/did:plc:z72i7hdynmk6r22z27h6tvur/
  bafkreicrnrylrdlwja5rsku7763xw6o2bjopkhvl3rubpaf4t54lkss2ja@jpeg",
  "like_count": 6710,
  "indexed_at": "2025-01-19T20:07:12.948Z",
  "collected_at": "2026-01-18T13:08:07.952667"
},

Descriptive statistics of our dataset

MetricValue
Collection overview
Total feeds collected88,302
Feeds with ≥1\ge1 subscriber49,069 (55.6%)
Unique feed creators41,955
Total posts scanned3,695,724
Total unique subscribers1,319,921
Subscribers per feed (feeds with ≥1\ge1 subscriber)
Median3
Mean26.9
Maximum50,757
1–10 subscribers37,801 (77.0%)
11–100 subscribers9,908 (20.2%)
101–1,000 subscribers1,239 (2.5%)
1,000+ subscribers121 (0.2%)
Posts per feed
Median posts scanned18
Mean posts scanned41.9
Feeds with 0 posts21,517 (24.4%)
Feed age
Median612 days (1.7 yrs)
Mean631 days (1.7 yrs)
Content composition (median / mean)
Media ratio75.0% / 59.4%
Reply ratio0.0% / 6.2%
Non-chronological ordering15.1%
Language (feeds with ≥1\ge1 subscriber)
English25,981 (52.9%)
Unknown (no tag)11,638 (23.7%)
Japanese7,423 (15.1%)
German907 (1.8%)
Portuguese679 (1.4%)

Table 7. Descriptive statistics of our custom feed dataset.

References

  1. [1]About Bluesky. 2025. https://bsky.social/about/faq.
  2. [2]Oscar Alvarado and Annika Waern. 2018. Towards algorithmic experience: Initial efforts for social media contexts. In Proceedings of the 2018 chi conference on human factors in computing systems. 1–12.
  3. [3]Mike Ananny and Kate Crawford. 2018. Seeing without knowing: Limitations of the transparency ideal and its application to algorithmic accountability. new media & society 20, 3 (2018), 973–989.
  4. [4]Ishaku Hassan Anaobi, Aravindh Raman, Ignacio Castro, Haris Bin Zia, Damilola Ibosiola, and Gareth Tyson. 2023. Will admins cope? Decentralized moderation in the fediverse. In Proceedings of the ACM Web Conference 2023. 3109–3120.DOI
  5. [5]Shubham Atreja, Shruthi Srinath, Mohit Jain, and Joyojeet Pal. 2023. Understanding journalists’ workflows in news curation. In Proceedings of the 2023 CHI Conference on Human Factors in Computing Systems. 1–13.DOI
  6. [6]Lars Backstrom. 2016. Serving a billion personalized news feeds. In Proceedings of the Ninth ACM International Conference on Web Search and Data Mining. 469–469.DOI
  7. [7]Lars Backstrom and Jure Leskovec. 2011. Supervised random walks: predicting and recommending links in social networks. In Proceedings of the fourth ACM international conference on Web search and data mining. 635–644.
  8. [8]Leonhard Balduf, Saidu Sokoto, Onur Asciigil, Gareth Tyson, Björn Scheuermann, Maciej Korczyński, Ignacio Castro, and Michał Król. 2024. Looking at the blue skies of bluesky. In Proceedings of the 2024 ACM on Internet Measurement Conference. 76–91.
  9. [9]Leonhard Balduf, Saidu Sokoto, Andrea Baronchelli, Ignacio Castro, Michał Król, Gareth Tyson, George Pavlou, Björn Scheuermann, and Onur Asciigil. 2025. Bootstrapping Social Networks: Lessons from Bluesky Starter Packs. In Proceedings of the International AAAI Conference on Web and Social Media, Vol. 19. 178–192.arxiv.org/abs/2501.11605
  10. [10]Aadit Barua, Leijie Wang, and Amy X Zhang. 2026. Compass: Continuously Aligning Social Media Feeds via In-Situ Reflections. arXiv preprint arXiv:2608.04274 (2026).DOI
  11. [11]Lauren Berlant. 1998. Intimacy: A special issue. Critical inquiry 24, 2 (1998), 281–288.DOI
  12. [12]Michael Bernstein, Angèle Christin, Jeffrey Hancock, Tatsunori Hashimoto, Chenyan Jia, Michelle Lam, Nicole Meister, Nathaniel Persily, Tiziano Piccardi, Martin Saveski, et al. 2023. Embedding societal values into social media algorithms. Journal of Online Trust and Safety 2, 1 (2023).
  13. [13]Rahul Bhargava, Anna Chung, Neil S Gikwad, Alexis Hope, Dennis Jen, Jasmin Rubinovitz, Belén Saldías-Fuentes, and Ethan Zuckerman. 2019. Gobo: A system for exploring user control of invisible algorithms in social media. In Companion publication of the 2019 conference on computer supported cooperative work and social computing. 151–155.
  14. [14]Bluesky Feed Creator. 2026. https://blueskyfeedcreator.com.
  15. [15]Bluesky Post Count and Author Stats. 2026. https://bsky.jazco.dev/stats.
  16. [16]Bluesky Top Feeds and Statistics. [n. d.]. https://bluefacts.app/feeds.
  17. [17]Maximilian Boeker and Aleksandra Urman. 2022. An empirical investigation of personalization factors on TikTok. In Proceedings of the ACM web conference 2022. 2298–2309.DOI
  18. [18]Carlo Bono, Chang Liu, Giuseppe Russo, and Francesco Pierri. 2026. Self-moderation in the decentralized era: decoding blocking behavior on bluesky. In Proceedings of the International AAAI Conference on Web and Social Media, Vol. 20. 315–329.
  19. [19]Danah Boyd. 2010. Social network sites as networked publics: Affordances, dynamics, and implications. In A networked self. Routledge, 47–66.DOI
  20. [20]Virginia Braun and Victoria Clarke. 2006. Using thematic analysis in psychology. Qualitative research in psychology 3, 2 (2006), 77–101.
  21. [21]Jackie Chan, Fred Choi, Koustuv Saha, and Eshwar Chandrasekharan. 2026. Examining algorithmic curation on social media: An empirical audit of reddit’s r/popular feed. In Proceedings of the International AAAI Conference on Web and Social Media, Vol. 20. 391–406.
  22. [22]Frederick Choi and Eshwar Chandrasekharan. 2025. Designing Usable Controls for Customizable Social Media Feeds. arXiv preprint arXiv:2509.19615 (2025).
  23. [23]Paul Covington, Jay Adams, and Emre Sargin. 2016. Deep neural networks for youtube recommendations. In Proceedings of the 10th ACM conference on recommender systems. 191–198.
  24. [24]Custom Feeds. 2026.
  25. [25]Michael Ann DeVito, Darren Gergle, and Jeremy Birnholtz. 2017. “Algorithms ruin everything” # RPTwitter, Folk Theories, and Resistance to Algorithmic Change in Social Media. In Proceedings of the 2017 CHI conference on human factors in computing systems. 3163–3174.
  26. [26]Andrea Failla and Giulio Rossetti. 2024. “I’m in the Bluesky Tonight”: Insights from a year worth of social data. PloS one 19, 11 (2024), e0310330.DOI
  27. [27]Gerhard Fischer. 2001. Communities of interest: Learning through the interaction of multiple knowledge systems. In Proceedings of the 24th IRIS Conference, Vol. 1. Department of Information Science, Bergen, 1–13.
  28. [28]Francis Fukuyama, Barak Richman, Ashish Goel, Roberta R Katz, A Douglas Melamed, and Marietje Schaake. 2020. Middleware for dominant digital platforms: A technological solution to a threat to democracy. CyberPolicy Center, Freeman Spogli Institute (2020).
  29. [29]R Stuart Geiger. 2016. Bot-based collective blocklists in Twitter: the counterpublic moderation of harassment in a networked public space. Information, Communication & Society 19, 6 (2016), 787–803.
  30. [30]Graze. 2026. https://graze.social.
  31. [31]Graze Marketplace. 2026. https://www.graze.social/marketplace.
  32. [32]Wanmong He, Mitchell L Gordon, Lindsay Popowski, and Michael S Bernstein. 2023. Cura: Curation at social media scale. Proceedings of the ACM on Human–Computer Interaction 7, CSCW2 (2023), 1–33.DOI
  33. [33]Theia Henderson, David R Karger, and David D Clark. 2025. Graffiti: Enabling an Ecosystem of Personalized and Interoperable Social Applications. In Proceedings of the 38th Annual ACM Symposium on User Interface Software and Technology, 1–21.DOI
  34. [34]Luke Hogg, René DiResta, Francis Fukuyama, Richard Reisman, Daphne Koller, Aviv Ovadya, Luke Thorburn, Jonathan Stray, and Shubhi Mathur. 2024. Shaping the Future of Social Media with Middleware. arXiv preprint arXiv:2412.10283 (2024).arxiv.org/abs/2412.10283
  35. [35]Silas Hsu, Kristen Vaccaro, Yin Yue, Aimee Rickman, and Karrie Karahalios. 2020. Awareness, navigation, and use of feed control settings online. In Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems, 1–13.DOI
  36. [36]Shagun Jhaver, Seth Frey, and Amy X Zhang. 2023. Decentralizing platform power: A design space of multi-level governance in online social platforms. Social Media + Society 9, 4 (2023), 20563051231207857.
  37. [37]Chenyang Jia, Michelle S Lam, Minh Chau Mai, Jeffrey T Hancock, and Michael S Bernstein. 2024. Embedding democratic values into social media AIs via societal objective functions. Proceedings of the ACM on Human–Computer Interaction 8, CSCW1 (2024), 1–36.DOI
  38. [38]Daphne Keller. 2021. The future of platform power: making middleware work. Journal of Democracy 32, 3 (2021), 168–172.DOI
  39. [39]Jon Kleinberg, Sendhil Mullainathan, and Manish Raghavan. 2024. The challenge of understanding what users want: Inconsistent preferences and engagement optimization. Management science 70, 9 (2024), 6336–6355.
  40. [40]Martin Kleppmann, Paul Frazee, Jake Gold, Jay Graber, Daniel Hoang, Devin Ivy, Jeremy Johnson, Bryan Newbold, and Jaz Volpert. 2024. Bluesky and the at protocol: Usable decentralized social media. In Proceedings of the ACM Conext-2024 Workshop on the Decentralization of the Internet. 1–7.
  41. [41]Daniel Klug, Yiluo Qin, Morgan Evans, and Geoff Kaufman. 2021. Trick and please. A mixed-method study on user assumptions about the TikTok algorithm. In Proceedings of the 13th ACM web science conference 2021. 84–92.DOI
  42. [42]Akaash Kolluri, Renn Su, Farnaz Jahanbakhsh, Dora Zhao, Tiziano Piccardi, and Michael S Bernstein. 2025. Alexandria: A Library of Pluralistic Values for Realtime Re-Ranking of Social Media Feeds. arXiv preprint arXiv:2505.10839 (2025).arxiv.org/abs/2505.10839
  43. [43]Cliff Lampe and Paul Resnick. 2004. Slash (dot) and burn: distributed moderation in a large online conversation space. In Proceedings of the SIGCHI conference on Human factors in computing systems. 543–550.
  44. [44]Jae Kook Lee, Jihyang Choi, Cheonsoo Kim, and Jonghwan Kim. 2014. Social media, network heterogeneity, and opinion polarization. Journal of communication 64, 4 (2014), 702–722.
  45. [45]Yuhan Liu, Emmy Song, Owen Xingjian Zhang, Jewel Merriman, Lei Zhang, and Andrés Monroy-Hernández. 2025. Understanding decentralized social feed curation on mastodon. Proceedings of the ACM on Human–Computer Interaction 9, 7 (2025), 1–25.arxiv.org/abs/2504.18817
  46. [46]Omar El Malki, Marianne Aubin Le Quéré, Andrés Monroy-Hernández, and Manoel Horta Ribeiro. 2025. Bonsai: Intentional and Personalized Social Media Feeds. arXiv preprint arXiv:2509.10776 (2025).
  47. [47]Mike Masnick. 2019. Protocols, Not Platforms: A Technological Approach to Free Speech. Knight First Amendment Institute (2019). https://knightcolumbia.org/content/protocols-not-platforms-a-technological-approach-to-free-speech.
  48. [48]Meet Attie. Your research companion for the open social web. 2026. https://attie.ai/.
  49. [49]Arvind Narayanan. 2023. Understanding social media recommendation algorithms. (2023).
  50. [50]Efrat Nechushutai, Rodrigo Zimth, and Seth C Lewis. 2024. More of the same? Homogenization in news recommendations when users search on Google, YouTube, Facebook, and Twitter. Mass Communication and Society 27, 6 (2024), 1309–1335.DOI
  51. [51]Gianluca Nugara, Erfan Samieyan Sahneh, Matthew R DeVerna, Nick Liu, Luca Luceri, Filippo Menczer, Francesco Pierri, and Silvia Giordano. 2026. A longitudinal analysis of misinformation, polarization and toxicity on Bluesky after its public launch. Online Social Networks and Media 51 (2026), 100342.
  52. [52]Tolulope Oshinowo, Sohyeon Hwang, Amy X Zhang, and Andrés Monroy-Hernández. 2025. Seeing the Politics of Decentralized Social Media Protocols. arXiv preprint arXiv:2505.22962 (2025).arxiv.org/abs/2505.22962
  53. [53]Chris Parnin, Christoph Treude, Lars Grammel, and Margaret-Anne Storey. 2012. Crowd documentation: Exploring the coverage and the dynamics of API discussions on Stack Overflow. (2012).
  54. [54]Thomas Poell. 2020. Three challenges for media studies in the age of platforms. Television & New Media 21, 6 (2020), 650–657.DOI
  55. [55]Lindsay Popowski, Xiyuan Wu, Charlotte Zhu, Tiziano Piccardi, and Michael S Bernstein. 2026. Social Media Feed Elicitation. arXiv preprint arXiv:2602.18594 (2026).arxiv.org/abs/2602.18594
  56. [56]Dorian Quelle and Alexandre Bovet. 2025. Bluesky: Network topology, polarization, and algorithmic curation. PLoS one 20, 2 (2025), e0318034.DOI
  57. [57]Aravindh Raman, Sagar Jogl ekar, Emiliano De Cristofaro, Nishanth Sastry, and Gareth Tyson. 2019. Challenges in the decentralised web: The mastodon case. In Proceedings of the internet measurement conference. 217–229.arxiv.org/abs/1909.05801
  58. [58]Rayhan Rashed and Farnaz Jahanbakhsh. 2025. What If Moderation Didn’t Mean Suppression? A Case for Personalized Content Transformation. arXiv preprint arXiv:2509.22861 (2025).DOI
  59. [59]Yuqing Ren, Robert Kraut, and Sara Kiesler. 2007. Applying common identity and bond theory to design of online communities. Organization studies 28, 3 (2007), 377–408.
  60. [60]Joseph Seering, Geoff Kaufman, and Stevie Chancellor. 2022. Metaphors in moderation. New Media & Society 24, 3 (2022), 621–640.
  61. [61]SkyFeed. 2026. https://skyfeed.app.
  62. [62]Jessie J Smith, Lucia Jayne, and Robin Burke. 2022. Recommender systems and algorithmic hate. In Proceedings of the 16th ACM conference on recommender systems. 592–597.
  63. [63]S Sokoto, L Badhuf, O Ascigil, G Tyson, I Castro, B Scheuermann, A Baronchelli, and M Krol. 2026. Open or Blocked Skies? Community Moderation Practices in Bluesky. In ACM The Web Conference.
  64. [64]Joëlle Swart. 2021. Experiencing algorithms: How young people understand, feel about, and engage with algorithmic news selection on social media. Social media + society 7, 2 (2021), 20563051211008828.
  65. [65]Bluesky Team. 2024. https://bsky.social/about/blog/7-27-2023-custom-feeds.
  66. [66]Leijie Wang, Kathryn Yurechko, Pranati Dani, Quan Ze Chen, and Amy X Zhang. 2025. End user authoring of personalized content classifiers: Comparing example labeling, rule writing, and llm prompting. In Proceedings of the 2025 CHI Conference on Human Factors in Computing Systems. 1–21.
  67. [67]Shoujin Wang, Xiuzhen Zhang, Yan Wang, and Francesco Ricci. 2024. Trustworthy recommender systems. ACM Transactions on Intelligent Systems and Technology 15, 4 (2024), 1–20.
  68. [68]Galen Cassebeer Weld, Leon Leibmann, Amy X Zhang, and Tim Althoff. 2025. Perceptions of Moderators as a Large-Scale Measure of Online Community Governance. Proceedings of the ACM on Human-Computer Interaction 9, 7 (2025), 1–29.
  69. [69]Etienne Wenger. 1999. Communities of practice. Vol. 92. Cambridge university press Cambridge.
  70. [70]Amy X Zhang, Michael S Bernstein, David R Karger, and Mark S Ackerman. 2024. Form-from: A design space of social media systems. Proceedings of the ACM on Human-Computer Interaction 8, CSCW1 (2024), 1–47.
  71. [71]Ethan Zuckerman and Isaac Brickman. 2024. Improving social media with middleware. The ANNALS of the American Academy of Political and Social Science 715, 1 (2024), 99–114.

Paper details

vlnc:W_efgqh4rq
Version
v1 · latest
Published
Added
License
CC BY 4.0
Usage

views · 12

downloads · 0

A view counts once per browser per day, a download each time the PDF is requested.

  • Computer Science

Not recorded for this paper

View statement
Looking for related papers…
Contents