Review of outbound RSS coming from Bluesky and Masto

Open
#329 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reviewing the Bluesky and Mastodon feed URLs in the issue and the corresponding reallySimple output linked for each. Compare what metadata and content each feed provides, then document a concise RSS profile or comparison that identifies any missing elements. The issue does not specify a target document or acceptance criteria, so confirm the intended deliverable first.

Written by the indexing model from the issue text.

Description

I posted a question on Mastodon yesterday:

here's a side-project we might work on. writing up what a good RSS feed coming from a social network would look like. they all seem to rush through it and often leave out one crucial bit. if we just wrote up a simple profile they probably would all just do it that way.

Bluesky

This is the address of an outbound RSS feed from Bluesky.

https://bsky.app/profile/did:plc:2q2hs5o42jhbd23pp6lkiauh/rss

This is the information FeedLand gets from reading the feed via the reallySimple package.

https://feeder.scripting.com/?feedurl=https://bsky.app/profile/did:plc:2q2hs5o42jhbd23pp6lkiauh/rss

Mastodon

This is the address of an outbound RSS feed from Mastodon.

https://mastodon.social/@davew.rss

This is the information FeedLand gets from reading the feed via the reallySimple package.

https://feeder.scripting.com/?feedurl=https://mastodon.social/@davew.rss

Dominant language
HTML
Stars
134
Forks
10
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.