Show Navigation
Notices tagged with hashtag
-
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
-
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
→ 🔮
-
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
-
@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
-
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/
-
@vinzv on the other hand !gnusocial doesn't have centralised hashtags, i.e. clicking #hashtag will only show posts of the poster's instance
-
#rättshaverism #konkurrens #umeå #hashtag https://blog.mmn-o.se/2015/07/04/umea-kommun-orsakar-skev-konkurrens-bland-webbtjanster/
-
#JAMBB vid #Hamnmagasinet i #Umeå #hashtag #webm https://social.umeahackerspace.se/attachment/31345
-
@eleanor70001 Most software turns a #Hashtag into a link, just click or tap or select and follow it
-
@question No, it's not my name, you silly git #hashtag