~
Docs
LanguageCoursesUserspaceSystemToolsManualGuidesOverviewReference
GlossaryAgentAmesAPIAquaArmArvoAtomAuraAural ASCIIAzimuthBatteryBehnBowlBridgeBuntCardCaseCaskCellCensuresClaimsClayCold atomCometCommitConsContextCordCoreDelegated SendingDeskDillDocument ProposalDojoDoorDouble-bootDry GateDuctEclipticEntropyEvent LogEyreFaceFactFoo Bar BazGalaxyGallGardenGateGeneratorGiftGlobHD WalletHelmHoodHoonInvite TreeIrisJaelJetKelvin versioningKelvin versioningKeyfileKeywordsKhanKilnLandscapeLegListLoobeanLullMarkMetalsMoldMonadMoonMoveNockNoun~OTA UpdatesPath PrefixPath@pPayloadPeekpHPierPillPlanetPokeProxiesScryReplayFactory ResetRollerNaive rollupsRuneRuntimeSailSampleScrySenateShipSlamSpiderSponsorStarStringSubject Oriented Progr...SubjectSubscriptionTapeThreadTrapUdonUpgrade ProposalUserspaceVaneVaseVereVotingWarm atomWet GateWingWireWrapper~zodZuse
Additional
Reference/Glossary/Poke

Poke

A poke is a kind of note passed from one agent to another in a card. A poke is a one-off request/action, as opposed to an ongoing subscription. A poke may contain any kind of data, and may go over the network to remote ships. A poke is handled by the ++on-poke arm of an agent.

Further reading

  • App school: cards: A lesson on cards, which includes pokes.
  • App school: pokes: A lesson on pokes.
Edit this page on GitHub

Last modified October 8, 2023

~Urbit
HomeGet StartedOverviewEcosystemGrantsEventsBlog
GitHubAirlock APIsUrbit BinariesDeveloper Mailing ListIssue TrackerWhitepaper
Privacy Policy
Terms of Service
support@urbit.org