Watching the flow of ActivityPub posts via WordPress

Aperta
#339 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
wordpress
Ambito
backend, web-dev

Direzione di ricerca

Start by reviewing the proposed wordpress.com changes.json feed and the six fields listed in the issue. Determine where this project could consume and present the feed, and clarify the desired display and polling behavior before coding. Done means the ActivityPub/WordPress activity is visible beyond the user's own posts and the result is useful for evaluating the connection.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

I want to see how people are using the connection between WordPress and ActivityPub.

Right now all I see are the posts I write.

Seeing what people are doing might give us ideas how to improve our respective products.

1999

We had a similar itch in 1999 when we wanted to see what the bloggers were writing. When a blog updated it would ping, we'd verify that they changed and if so, it would appear at the top of the list at weblogs.com.

Its output was a file called changes.xml, it had three bits of info for each update, the name, a url and timestamp.

There was a limit to 100 items in the file.

2025

wordpress.com maintains a changes.json file at a fixed location which we can poll.

there's a limit to the number of items in the file.

each item has:

  1. name of blog it came from
  2. title of the post if it has one
  3. when it was published
  4. url of the post via mastodon
  5. url of the post via wordpress
  6. url of rss feed for the site

that's where to start. let's see what we get to see where we go with this.

What will happen

We will of course share the info with the people who are using it. ;-)

Guess what we'll all start writing about -- how great it is and what doesn't work.

Giving a voice to the bloggers to help drive the direction of the tech.

I bet the users we're attracting now are pretty leading edge people.

Lingua principale
HTML
Stelle
134
Fork
10
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di scripting/Scripting-News

Tutte le issue di scripting/Scripting-News

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.