status.blaise.ca
type: Site
name: stadeus
space of: hashtag

hashtag
type: Container
type: channel
description: Updates tagged with hashtag on stadeus!
licence: http://creativecommons.org/licenses/by/3.0/
items: hashtag-proposal-datetags
items: indiewebcamp-auto-link
items: indiewebcamp-auto-linking
items: summary-w3c-tpac-2023
items: objectType=note
items: mmn: Woop, dags att cykla ner och kolla vad #VänIUmeå pysslar med i #INFOGA's lokal i #Utopia idag #hashtag #mania https://infoga.se/2016/05/01/kalendarium/
items: mcscx: @vinzv on the other hand !gnusocial doesn't have centralised hashtags, i.e. clicking #hashtag will only show posts of the poster's instance
items: mmn: #rättshaverism #konkurrens #umeå #hashtag https://blog.mmn-o.se/2015/07/04/umea-kommun-orsakar-skev-konkurrens-bland-webbtjanster/
items: mmn: #JAMBB vid #Hamnmagasinet i #Umeå #hashtag #webm https://social.umeahackerspace.se/attachment/31345
items: bobjonkmanformer: @eleanor70001 Most software turns a #Hashtag into a link, just click or tap or select and follow it
items: inscius: @question No, it's not my name, you silly git #hashtag

hashtag-proposal-datetags
type: item
type: MicroblogPost
title: : Simple hashtag proposal for dates: datetags for the #indiewebIn summary by example:* #2026_08_04 ISO8601 YYYY_MM_DD date of this post* #2026_216 ISO8601 YYYY_DDD ordinal date of this post* #2026_08 ISO8601 YYYY_MM month of this postMany of us posting on the indieweb often post about things in the past. Photos, events, or sometimes throwback posts. Hashtags communicate and aggregate what posts are about. Posts about the past are usually about a specific date in the past, or sometimes an entire month. Thus it makes sense to use hashtags for those dates and months.I have been hashtagging such posts about the past for several years, and with some iteration have developed a convention that works for international readability, and is linked and indexed in #federated #hashtag systems like #ActivityPub (#Mastodon etc.).Examples of posts 10 years ago and this past week that use datetags:* https://tantek.com/2016/153/t4/june — monthtag and datetag* https://tantek.com/2026/215/t1/watched-odyssey-metreon-70mm-imax — normal and ordinal ISO8601 dates.Additional possibilities to explore:* yeartags — hashtags for entire years* timetags — hashtags for specific times, undated/floating timesAfter several web searches I didn’t find any prior proposals for hashtags for dates or times. Hopefully by hashtagging this post, future web searches will find this proposal.Have you hashtagged your posts with dates or times? Share your examples!This is post 11 of #100PostsOfIndieWeb. #100Posts#dateTag #dateTags #monthTag #monthTags #yearTag #yearTags #timeTag #timeTags#August #Blaugust #Blaugust2026← https://tantek.com/2026/214/t2/watch-posts-movie-tv-emoji→ 🔮
link: https://status.blaise.ca/notice/116330
description: 's status on Tuesday, 04-Aug-2026 21:00:00 EDT
encoded: Simple hashtag proposal for dates: datetags for the #indieweb In summary by example: * #2026_08_04 ISO8601 YYYY_MM_DD date of this post * #2026_216 ISO8601 YYYY_DDD ordinal date of this post * #2026_08 ISO8601 YYYY_MM month of this post Many of us posting on the indieweb often post about things in the past. Photos, events, or sometimes throwback posts. Hashtags communicate and aggregate what posts are about. Posts about the past are usually about a specific date in the past, or sometimes an entire month. Thus it makes sense to use hashtags for those dates and months. I have been hashtagging such posts about the past for several years, and with some iteration have developed a convention that works for international readability, and is linked and indexed in #federated #hashtag systems like #ActivityPub (#Mastodon etc.). Examples of posts 10 years ago and this past week that use datetags: * https://tantek.com/2016/153/t4/june — monthtag and datetag * https://tantek.com/2026/215/t1/watched-odyssey-metreon-70mm-imax — normal and ordinal ISO8601 dates. Additional possibilities to explore: * yeartags — hashtags for entire years * timetags — hashtags for specific times, undated/floating times After several web searches I didn’t find any prior proposals for hashtags for dates or times. Hopefully by hashtagging this post, future web searches will find this proposal. Have you hashtagged your posts with dates or times? Share your examples! This is post 11 of #100PostsOfIndieWeb. #100Posts #dateTag #dateTags #monthTag #monthTags #yearTag #yearTags #timeTag #timeTags #August #Blaugust #Blaugust2026 ← https://tantek.com/2026/214/t2/watch-posts-movie-tv-emoji → 🔮
date: 2026-08-04T21:00:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110393
enclosure: watch-posts-movie-tv-emoji
links to: watch-posts-movie-tv-emoji
enclosure: june
links to: june
enclosure: watched-odyssey-metreon-70mm-imax
links to: watched-odyssey-metreon-70mm-imax
tagged: concept

watch-posts-movie-tv-emoji
date: 2026-08-04T21:51:13-04:00
type: text/html; charset=UTF-8

june
date: 2026-08-05T13:57:49-04:00
type: text/html; charset=UTF-8

watched-odyssey-metreon-70mm-imax
date: 2026-08-05T13:57:50-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: 100posts

concept
type: Tag
label: 100postsofindieweb

concept
type: Tag
label: 202608

concept
type: Tag
label: 20260804

concept
type: Tag
label: 2026216

concept
type: Tag
label: activitypub

concept
type: Tag
label: blaugust

concept
type: Tag
label: blaugust2026

concept
type: Tag
label: datetags

concept
type: Tag
label: federated

concept
type: Tag
label: hashtag

concept
type: Tag
label: indiewebin

concept
type: Tag
label: monthtag

concept
type: Tag
label: monthtags

concept
type: Tag
label: timetag

concept
type: Tag
label: timetags

concept
type: Tag
label: yeartag

concept
type: Tag
label: yeartags

indiewebcamp-auto-link
type: item
type: MicroblogPost
title: : Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ https://tantek.com/2024/242/t1/indiewebcamp-portland
link: https://status.blaise.ca/notice/116221
description: 's status on Sunday, 25-Aug-2024 19:00:00 EDT
encoded: Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → https://tantek.com/2024/242/t1/indiewebcamp-portland
date: 2024-08-25T19:00:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110290
enclosure: reply-domain-above-address-and-silo
links to: reply-domain-above-address-and-silo
enclosure: footnotes-unicode-links
links to: footnotes-unicode-links
enclosure: auto-linked-hashtags-federated
links to: auto-linked-hashtags-federated
enclosure: updated-auto-linking-mention-use-cases
links to: updated-auto-linking-mention-use-cases
enclosure: autolink²
links to: autolink²
enclosure: cassis.jsThis
links to: cassis.jsThis
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
tagged: concept

reply-domain-above-address-and-silo
date: 2023-01-21T04:12:23-05:00
type: text/html; charset=UTF-8

footnotes-unicode-links
date: 2023-02-14T17:50:22-05:00
type: text/html; charset=UTF-8

auto-linked-hashtags-federated
date: 2023-04-19T22:24:38-04:00
type: text/html; charset=UTF-8

updated-auto-linking-mention-use-cases
date: 2024-03-13T00:20:15-04:00
type: text/html; charset=UTF-8

autolink²
date: 2024-08-25T21:56:52-04:00
type: text/html; charset=UTF-8

cassis.jsThis
date: 2024-08-25T21:56:53-04:00
type: text/html; charset=utf-8

indiewebcamp-portland
date: 2024-08-25T21:56:53-04:00
type: text/html; charset=UTF-8

indiewebcamp-portland
date: 2024-09-02T21:41:18-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: autolink

concept
type: Tag
label: footnote

concept
type: Tag
label: footnotespreviously

concept
type: Tag
label: hashtags

concept
type: Tag
label: indiewebcamp

indiewebcamp-auto-linking
type: item
type: MicroblogPost
title: : Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹.I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.* URLs, @-s, and @-@-s* # hashtags* ^ footnotes#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotesPreviously, previously, previously:* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated* https://tantek.com/2023/043/t1/footnotes-unicode-links* https://tantek.com/2023/019/t5/reply-domain-above-address-and-siloReferences:¹ https://indieweb.org/autolink² https://github.com/tantek/cassis/blob/main/cassis.jsThis is post 18 of #100PostsOfIndieWeb. #100Posts← https://tantek.com/2024/238/t1/indiewebcamp-portland→ 🔮
link: https://status.blaise.ca/notice/116212
description: 's status on Sunday, 25-Aug-2024 19:00:00 EDT
encoded: Nice #IndieWebCamp discussion session with @KevinMarks.com (@kevinmarks@xoxo.com @kevinmarks) on the topic of auto-linking¹. I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^). Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services. It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients. I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post. * URLs, @-s, and @-@-s * # hashtags * ^ footnotes #IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes Previously, previously, previously: * https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases * https://tantek.com/2023/100/t1/auto-linked-hashtags-federated * https://tantek.com/2023/043/t1/footnotes-unicode-links * https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo References: ¹ https://indieweb.org/autolink ² https://github.com/tantek/cassis/blob/main/cassis.js This is post 18 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/238/t1/indiewebcamp-portland → 🔮
date: 2024-08-25T19:00:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110281
enclosure: reply-domain-above-address-and-silo
links to: reply-domain-above-address-and-silo
enclosure: footnotes-unicode-links
links to: footnotes-unicode-links
enclosure: auto-linked-hashtags-federated
links to: auto-linked-hashtags-federated
enclosure: updated-auto-linking-mention-use-cases
links to: updated-auto-linking-mention-use-cases
enclosure: autolink²
links to: autolink²
enclosure: cassis.jsThis
links to: cassis.jsThis
enclosure: indiewebcamp-portland
links to: indiewebcamp-portland
tagged: concept

summary-w3c-tpac-2023
type: item
type: MicroblogPost
title: : I recently wrote a high level summary blog post:W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023https://tantek.com/2023/262/b1/w3c-technical-plenary-tpacof my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before.Posting this note to explicitly #hashtag that article with topics mentioned therein:#Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPubbecause I forgot to put explicit categories (p-category markup) in the article post.Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works.Post glossary:article post https://indieweb.org/articlenote post https://indieweb.org/notep-category https://indieweb.org/p-categorytags https://indieweb.org/tags
link: https://status.blaise.ca/notice/116135
description: 's status on Sunday, 24-Sep-2023 21:33:00 EDT
encoded: I recently wrote a high level summary blog post: W3C Technical Plenary and Advisory Committee (TPAC) Meetings 2023 https://tantek.com/2023/262/b1/w3c-technical-plenary-tpac of my time at the #W3C (@W3.org, @w3c@w3c.social, @W3C) #TPAC the week before. Posting this note to explicitly #hashtag that article with topics mentioned therein: #Sevilla #Seville #Spain #WICG #SocialCG #SWICG #Fediverse #SocialWeb #sustainability #IndieWeb #ActivityPub because I forgot to put explicit categories (p-category markup) in the article post. Adding that markup after publishing, and then sending an ActivityPub update (via #BridgyFed) is apparently not enough for #Mastodon to notice that the Update has new tags to display and aggregate on tag pages. In my next #w3cTPAC article post I’ll be sure to include category markup before publishing and see if that works. Post glossary: article post https://indieweb.org/article note post https://indieweb.org/note p-category https://indieweb.org/p-category tags https://indieweb.org/tags
date: 2023-09-24T21:33:00-04:00
creator: Tantek
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/110212
enclosure: articlenote
links to: articlenote
enclosure: notep-category
links to: notep-category
enclosure: p-categorytags
links to: p-categorytags
enclosure: tags
links to: tags
tagged: concept

articlenote
date: 2023-09-24T23:16:24-04:00
type: text/html; charset=UTF-8

notep-category
date: 2023-09-24T23:16:25-04:00
type: text/html; charset=UTF-8

p-categorytags
date: 2023-09-24T23:16:27-04:00
type: text/html; charset=UTF-8

tags
date: 2023-09-24T23:16:28-04:00
type: text/html; charset=UTF-8

concept
type: Tag
label: activitypubbecause

concept
type: Tag
label: bridgyfed

concept
type: Tag
label: fediverse

concept
type: Tag
label: indieweb

concept
type: Tag
label: mastodon

concept
type: Tag
label: seville

concept
type: Tag
label: socialcg

concept
type: Tag
label: socialweb

concept
type: Tag
label: spain

concept
type: Tag
label: sustainability

concept
type: Tag
label: swicg

concept
type: Tag
label: tpac

concept
type: Tag
label: w3c

concept
type: Tag
label: w3ctpac

concept
type: Tag
label: wicg

objectType=note
type: item
type: MicroblogPost
title: mmn: @dwmatiz Also I could expand on what I meant: Only programmers would have anything against the specific '!' character as opposed to others, as that's the only area (I know) it has semantic meaning when prepended to a word. ¡Not even Spain uses it! And if there's no specific preference against for most people, then reasonably there's no reason to choose one character over the other. By following the rationale of how the #hashtag was chosen by normal people because noone ever uses # at all, but we're sort of out of characters normies don't use _and_ can be written on a majority of keyboards easily (~ is not easily written, to tie back into that suggestion). cc: @clacke
link: https://status.blaise.ca/notice/100616
description: mmn's status on Friday, 05-May-2017 04:23:36 EDT
encoded: @dwmatiz Also I could expand on what I meant: Only programmers would have anything against the specific '!' character as opposed to others, as that's the only area (I know) it has semantic meaning when prepended to a word. ¡Not even Spain uses it! And if there's no specific preference against for most people, then reasonably there's no reason to choose one character over the other. By following the rationale of how the #hashtag was chosen by normal people because noone ever uses # at all, but we're sort of out of characters normies don't use _and_ can be written on a majority of keyboards easily (~ is not easily written, to tie back into that suggestion). cc: @clacke
date: 2017-05-05T04:23:36-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/98526
tagged: concept

mmn: Woop, dags att cykla ner och kolla vad #VänIUmeå pysslar med i #INFOGA's lokal i #Utopia idag #hashtag #mania https://infoga.se/2016/05/01/kalendarium/
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/86757
description: mmn's status on Saturday, 07-May-2016 07:38:14 EDT
encoded: Woop, dags att cykla ner och kolla vad #VänIUmeå pysslar med i #INFOGA's lokal i #Utopia idag #hashtag #mania https://infoga.se/2016/05/01/kalendarium/
date: 2016-05-07T07:38:14-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/86757
tagged: concept

concept
type: Tag
label: infoga

concept
type: Tag
label: mania

concept
type: Tag
label: utopia

concept
type: Tag
label: vaniumea

mcscx: @vinzv on the other hand !gnusocial doesn't have centralised hashtags, i.e. clicking #hashtag will only show posts of the poster's instance
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/84454
description: mcscx's status on Friday, 01-Apr-2016 12:26:52 EDT
encoded: @vinzv on the other hand !gnusocial doesn't have centralised hashtags, i.e. clicking #hashtag will only show posts of the poster's instance
date: 2016-04-01T12:26:52-04:00
creator: McScx
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/84454
tagged: concept

mmn: #rättshaverism #konkurrens #umeå #hashtag https://blog.mmn-o.se/2015/07/04/umea-kommun-orsakar-skev-konkurrens-bland-webbtjanster/
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/60828
description: mmn's status on Saturday, 04-Jul-2015 08:54:58 EDT
encoded: #rättshaverism #konkurrens #umeå #hashtag https://blog.mmn-o.se/2015/07/04/umea-kommun-orsakar-skev-konkurrens-bland-webbtjanster/
date: 2015-07-04T08:54:58-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/60828
tagged: concept

concept
type: Tag
label: konkurrens

concept
type: Tag
label: rattshaverism

concept
type: Tag
label: umea

mmn: #JAMBB vid #Hamnmagasinet i #Umeå #hashtag #webm https://social.umeahackerspace.se/attachment/31345
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/60639
description: mmn's status on Wednesday, 01-Jul-2015 16:48:47 EDT
encoded: #JAMBB vid #Hamnmagasinet i #Umeå #hashtag #webm https://social.umeahackerspace.se/attachment/31345
date: 2015-07-01T16:48:47-04:00
creator: MMN-o ✅⃠
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/60639
tagged: concept

https://social.umeahackerspace.se/file/9e3ad9b801ef76cfe7169f86d9d146460e83be925bbd4d020cee0cdbfb6b51da.webm
date: 2015-07-01T16:49:52-04:00
length: 5616081
type: video/webm

concept
type: Tag
label: hamnmagasinet

concept
type: Tag
label: jambb

concept
type: Tag
label: webm

bobjonkmanformer: @eleanor70001 Most software turns a #Hashtag into a link, just click or tap or select and follow it
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/35427
description: bobjonkmanformer's status on Monday, 18-Aug-2014 22:43:13 EDT
encoded: @eleanor70001 Most software turns a #Hashtag into a link, just click or tap or select and follow it
date: 2014-08-18T22:43:13-04:00
creator: Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
reply of: https://status.blaise.ca/notice/35426
has discussion: https://status.blaise.ca/conversation/29117
tagged: concept

inscius: @question No, it's not my name, you silly git #hashtag
type: item
type: MicroblogPost
link: https://status.blaise.ca/notice/6629
description: inscius's status on Sunday, 07-Jul-2013 06:29:56 EDT
encoded: @question No, it's not my name, you silly git #hashtag
date: 2013-07-07T06:29:56-04:00
creator: inscius
has creator: acct
licence: http://creativecommons.org/licenses/by/3.0/
has discussion: https://status.blaise.ca/conversation/5064
tagged: concept

inscius
type: Agent
nick: inscius
holds account: acct