Skip to main content
Sifa Docs

Activity feed

What Sifa shows on your profile and why we leave most of your AT Protocol activity out.

The activity feed on your Sifa ID profile follows one opinion. We do not show everything you do on AT Protocol. We show the things you made, not the things you reacted to.

The rules come from a taxonomy in the Sifa SDK. Each build of this page reads that taxonomy and renders the tables below. The tables therefore cannot drift away from what the product does.

How your activity gets here

You do not connect anything. Your activity follows your DID, so when you use an app on the Atmosphere, the records it writes to your provider are yours already. Sifa reads them and renders the ones that count as work.

Start using a new app and it shows up on your profile on its own. Stop using one and it stops appearing. There is no list to maintain and nothing to reconnect. Supported apps lists every app that Sifa recognises.

Two things work differently:

  • Accounts off the Atmosphere (GitHub, a Fediverse server, an RSS feed, ORCID) have no DID to follow. You add and verify them once under External accounts. After that they behave the same way.
  • Your own posts only. Sifa reads what you published, never what you saw. See below.

What we show: "Made"

These are the record types Sifa treats as your work. They show up on your public profile.

Substantive records the actor authored: posts, articles, repos, galleries, livestreams, RSVPs, CV entries. Surfaced on the public profile and in the network timeline.

LexiconAppNotes
app.atmobb.discussion.replyatmobbReplies are authored text, consistent with app.bsky.feed.post covering replies.
app.atmobb.discussion.threadatmobb
app.beaconbits.beaconbeaconbits
app.bsky.feed.postblueskyAmbiguous: many posts are casual, but the lexicon also carries long-form posts and threads. Treated as creation; empty quote-posts (no text + record embed) are filtered at the consumer layer, not here.
app.bsky.graph.verificationblueskyDiverges from app.bsky.graph.follow (action) on purpose: verifying another account's handle is a deliberate trust statement the actor authors, not a tap. Sifa renders it with its own card.
app.collectivesocial.feed.listcollectivesocialAuto-created default Inbox lists are filtered at the consumer layer via isDefault=true predicate.
app.mcp.servermcp
app.sidetrail.trailsemble
app.sidetrail.walksemble
app.userinput.discussionuserinput
app.userinput.replyuserinputReplies are authored text, consistent with app.bsky.feed.post covering replies.
at.margin.annotationmarginAn annotation on someone else's text is still authored writing.
at.margin.notemargin
at.marque.domainmarque
at.youandme.connectionyouandme
blue.flashes.feed.postflashes
buzz.bookhive.bookbookhive
com.minomobi.music.compositionminomobi
com.voxport.podcast.seriesvoxport
com.whtwnd.blog.entrywhitewind
community.lexicon.badge.awardbadgesThe award record is authored by the giver, so it is their attestation about someone else.
community.lexicon.calendar.rsvpsmokesignalAmbiguous: RSVPs are reactions to events, but they are public commitments and the only Smoke Signal record Sifa scans today. Classified as creation.
community.nooki.commentsnookiComments are authored text.
community.nooki.membershipnookiJoining a community, classified like social.colibri.membership (creation).
community.opensocial.membershipopensocialJoining a community, classified like social.colibri.membership (creation).
computer.aetheros.pageaetheros
dev.atvouch.graph.vouchatvouchVouching for someone. Authored attestation, same reasoning as fund.at.graph.endorse.
dev.baileytownsend.guestbook.entryguestbookSigning someone else's guestbook is a short authored message.
dev.keytrace.claimkeytrace
exchange.recipe.reciperecipe
fm.plyr.commentplyrComments are authored text.
forum.barazo.community.memberbarazo
forum.barazo.postbarazo
forum.barazo.reputation.eventbarazo
fund.at.graph.endorseatfundEndorsing someone. Authored attestation, not engagement.
fyi.asq.answerasq
fyi.asq.questionasq
fyi.atstore.listing.reviewatstore
fyi.unravel.frontpage.postfrontpage
id.sifa.endorsementsifaEndorsement authored by the actor about another profile.
id.sifa.graph.connectionsifaMutual professional connection record.
id.sifa.meetingsifa
id.sifa.profile.certificationsifa
id.sifa.profile.coursesifa
id.sifa.profile.educationsifa
id.sifa.profile.externalAccountsifa
id.sifa.profile.honorsifa
id.sifa.profile.languagesifa
id.sifa.profile.locationsifa
id.sifa.profile.positionsifa
id.sifa.profile.presentationsifa
id.sifa.profile.presentationDeliverysifa
id.sifa.profile.projectsifa
id.sifa.profile.publicationsifa
id.sifa.profile.selfsifaSifa professional profile root.
id.sifa.profile.skillsifa
id.sifa.profile.volunteeringsifa
id.sifa.project.membersifaDeprecated, never implemented. Superseded by id.sifa.confirmation.
id.sifa.project.membershipsifaDeprecated, never implemented. Superseded by id.sifa.confirmation.
id.sifa.project.selfsifa
io.atcr.repo.pageatcr
io.calabro.watsm.programwatsm
io.kich.recipe.recipekich
is.kevara.directory.speakerkevara
li.plonk.pasteplonk
link.pastesphere.snippetpastesphere
net.alternativeproto.submissionalternativeproto
net.anisota.feed.listanisota
net.anisota.feed.postanisota
one.papili.postpapili
org.v-it.skillvit
os.aether.docs.presentationaetherdocs
place.stream.livestreamstreamplace
pub.leaflet.commentleaflet
quest.atmo.checkinatmorsvpAttendance, classified like community.lexicon.calendar.rsvp (creation) rather than as engagement. The creation tier description names RSVPs explicitly.
quest.atmo.eventatmorsvp
sh.tangled.repotangled
sh.tangled.repo.issuetangled
sh.tangled.repo.pulltangled
site.standard.documentstandard
so.sprk.feed.postspark
so.sprk.story.postspark
social.colibri.membershipcolibri
social.crate.contentcrate
social.crate.notecrate
social.grain.gallerygrain
social.passports.fiftyStates.visitpassports
social.passports.travel.legpassports
social.popfeed.feed.notepopfeed
social.popfeed.feed.postpopfeed
social.popfeed.feed.reviewpopfeed
social.psky.feed.postpicosky
space.roomy.space.personalroomy
st.lifepo.lifeEventlifepo
stream.thought.blipstreamthought
tech.waow.doodl.drawingwaow
tech.waow.doodl.iconwaow
tech.waow.doodl.iconsetwaow
tech.waow.doodl.logowaow
tech.waow.pollz.pollwaow
tech.waow.slides.deckwaow
tech.waow.slides.slidewaowIndividual slides are components of a deck. Both are kept; the consumer decides whether to collapse them.
wiki.lichen.notelichen
wiki.lichen.wikilichen

Source: @singi-labs/sifa-sdk v1.1.0 (updated 2026-07-29). This table is regenerated from the SDK at build time; if it looks stale, the docs site needs to be rebuilt against a newer SDK release.

What we leave out: "Did"

Things you did on the network: likes, follows, reposts, RSVPs. We keep these off your public profile so the page stays a record of work, not a record of taps. The Bluesky app and the originating apps already show this side of you.

Engagement records (likes, reposts, follows, votes, stars, reactions). Visible to the actor on the 'What is public about me' page and on the originating app, but not surfaced on the Sifa public profile.

LexiconAppNotes
app.bsky.feed.likebluesky
app.bsky.feed.repostbluesky
app.bsky.graph.followbluesky
forum.barazo.reactionbarazo
forum.barazo.replybarazoShort conversational reply — engagement signal.
fyi.unravel.frontpage.votefrontpage
id.sifa.confirmationsifaConfirmation that a record naming the actor is accurate (co-speaker credit, project membership).
id.sifa.endorsement.confirmationsifaConfirmation/acceptance of an endorsement received.
id.sifa.graph.followsifa
net.alternativeproto.votealternativeprotoVote record on a third-party protocol.
pub.leaflet.interactions.recommendleaflet
sh.tangled.feed.startangled
sh.tangled.graph.followtangled
social.popfeed.feed.likepopfeed

Source: @singi-labs/sifa-sdk v1.1.0 (updated 2026-07-29). This table is regenerated from the SDK at build time; if it looks stale, the docs site needs to be rebuilt against a newer SDK release.

A third tier (filtered) covers configuration records, moderation records, and other infrastructure that we hide from every Sifa surface. Those records still live on your PDS, we just do not render them.

Why we work this way

Most professional networks rank, score, or pad your profile with engagement metrics. We do not. Your profile is a record of work you did. If you want to know if someone is good at what they say they do, click through to the actual work.

Hide something from your profile

The taxonomy decides which records can appear. You decide which records do appear.

A hide changes Sifa only. The record stays on your provider. Every other app on the Atmosphere can still read it. To remove a record from the network, delete it in the app that wrote it.

One app. Open your activity settings. Turn the app off. Sifa stops showing every record from that app.

One item. Open your own activity page. Each card carries a hide control that only you see. Hide one post and the other posts from the same app stay.

Your activity settings list every item that you hide. Select an item in that list to show it again. A hidden item also leaves your activity graph and the activity image on your link previews.

Want a different filter?

Sifa has no switch for a whole category yet. You can hide one app or one item, as above. Do you want a record type added or removed? Open an issue against sifa-sdk with a link to the lexicon and a short reason.

On this page