home.social

#hyperlink — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #hyperlink, aggregated by home.social.

  1. Is there a way to create a hyperlink on a website that links to Mastodon, but in a way that it pre-fills the message box with a user handle?

    I guess that what I am asking is the equivalent of a mailto link.

    #mastodon #hyperlink #hypermedia

  2. Ah, the humble #hyperlink, the unsung hero of the web 🙄. Here we are, 2025, and some wizard finally realizes links might be useful for "context engineering"—revolutionary! Next, they'll discover the wheel and fire 🔥.
    mbleigh.dev/posts/context-engi #contextengineering #webinnovation #digitalrevolution #unsunghero #HackerNews #ngated

  3. #Identity #Authenticity, remains a HUGE problem at the #Internet->#Web->#SocialMedia levels. It's so big that it has trivially imploded #Twitter via the recent Blue Checkmark/Badge disaster.

    A #SemanticWeb solves this headache, once understood, by way of #TLS integration using a #Hyperlink -- as demonstrated by protocol extensions such as #NetIDTLS and #WebIDTLS.

    Here's a post that includes a NetIDTLS Sequence Flow Diagram to aid understanding.

    community.openlinksw.com/t/how

    #LinkedData #DPKI

  4. @Cyberpunk @protonmail,

    Yes, and my fundamental issue has more to do with offering users choice, since there's functionality in #SMIME that isn't available via #OpenPGP.

    For example, #X509 cert subject naming using a #hyperlink that resolves to a public profile doc.

    That capability enables sophisticated filters construction for fighting #phishing attacks via #DPKI (rather than centralized #PKI)

    Choice is important.

  5. @bertrand,
    We have different scenarios (enterprise or personal) where #Identity #Authenticity is achieved via common use of #DPKI (enhanced by #hyperlink based subject denotation that resolves to a machine-computable entity relationship graph [the subjects profile data]).

    #SSI as I've been speaking about relates to the individual seeking control over their identity and privacy at #Web and #Internet scales.

    /cc @meneer @aniltj @w3c

  6. @meneer,

    To be clear, I am a firm believer in loosely-coupling the following:

    1. #Identity -- via identifiers (e.g., a #hyperlink)
    2. #Identification -- via credentials (graph)
    3. #authentication -- using various protocols
    4. #authorization -- access controls (eg #ABAC)
    5. #storage -- file systems or #DBMS

    When I speak about #DPKI and #ZeroTrust the focal points are 1-3.

    #HTTP offers abstraction atop the #Internet that deemphasizes #DNS re entity naming.

    /cc @bertrand @aniltj @w3c

  7. @bertrand ,

    The scalability problem with #PGP arises from the need for in-person signing parties.

    That's solved by using a #hyperlink to denote the subject of an #X509 cert that resolves to a profile document comprising matching credentials from said cert. This triangulation happens at the end of a #TLS handshake re scalable #ZeroTrust based #DPKI.

    /cc @meneer @aniltj @w3c

    #NetIDTLS #HTTPS #Identity #Authenticity #SSI

  8. @meneer,

    Great question!
    A the core of what I describe lies the fact that authenticity is no longer a function of a centralized CA; rather, the triangulation of a "proof of control" scoped to:

    1. Private Key possession
    2. Profile Document Control
    3. #X509 Cert Credentials cross-referencing to what's in #1

    #DPKI is about #Identity #Authenticity proof without centralized CAs, courtesy of #Hyperlink based subject naming and the connectivity it unleashes :)

    /cc @aniltj @w3c

  9. @atomicpoet,

    Regarding Finger, how about the fact that #WebFinger is its #Web rendition?

    Injecting #hyperlink power into utilities that existed in the earlier #Unix dominated #Internet is something that folks sometimes overlook.

    Google #Search enhanced by a #gptChat browser extension.

    google.com/search?q=How+are+Fi

    A lot of existing stuff is simply being tweaked for the #Web (an Internet abstraction layer) 😊

    /cc @abathur

  10. @aniltj,

    "..And a core component that they are trying to break is the first class support for JSON-LD within the standard, that gives the data representation its power and flexibility."

    Yep!

    Unfortunately for them, #Fediverse apps exist, and the broader community is much wiser due to the #Web20 experience.

    #JSONLD is a #JSON dialect that makes it easier to harness the fundamental essence of the #Web:

    Name everything unambiguously using a #Hyperlink to make #DataConnectivity magic happen.

  11. @KevinMarks ,

    Here's a single #hyperlink that denotes the @anildash post that kicked off this thread.

    linkeddata.uriburner.com/about

    That's a fully fledged data source name that delivers structured data to user-agents in a variety of negotiable formats.

    Just click to explore 😀

    /cc @atomicpoet

    #LinkedData #Fediverse #Web30 #SemanticWeb #WebWeWant

  12. Yep!

    Today, there's a massive #Fediverse comprising lots of entities and entity relationship types named using a #Hyperlink.

    All of this data flows #DataSpaces without the disturbance of silos.

    /cc @openlink @Mastodon

    #DataFlow #DataConnectivity #LinkedData #SemanticWeb #ActivityStreams #ActivityPub

  13. @atomicpoet,

    Yes, from day one 😀

    Revisit my profile page and take note of the SHA1 hash on display -- that pairs with the #PublicKey component of one of my privately held #X509 certs.

    The hurdle here isn't tech at all. It's more to do with end-user education re what's already in place, in plain sight -- but unused re #Identity #Authencity that scales to both the #Web and #Internet.

    Skeptics of this approach presume #PKI whereas this is #DPKI, courtesy of #Hyperlink power.

    /cc @youid

  14. @rmrfslashbin,

    Somewhat in that public and private credentials are cross-referenced.

    In the case of #NetIDTLS (what I write about), an #X509 certificate holds private credentials cross-referenced to public equivalents by looking-up a #Hyperlink that serves as a certificate subject identifier.

    Basically, it's all based on existing open standards 😀

    /cc @atomicpoet @youid

    #NetID #HTTPS #TLS #WebID #YouID

  15. @pdxjohnny,

    Great to hear, and more to come!

    #gptChat is a really handy tool for demonstrating the power of a #SemanticWeb fueled by incorporating #hyperlink based entity denotation into structured data representation.

    #RDF #LinkedData #DataAccess #DataConnectivity

  16. I've uploaded an #RDFTurtle document to my personal #ODSBriefcase at:

    kingsley.idehen.net/public_hom

    If you have our #OSDS Browser Ext. installed, you can start #Fediverse exploration via any profile of interest.

    Specific steps:
    1. Click on the #hyperlink that denotes the doc in my briefcase

    2. Click on a hyperlink that denotes a user

    3. Click on the hyperlink that denotes the #RSS or #ActivityStreams of a selected user

    That's it.

    /cc @observablehq @mauforonda @Mastodon @judell

    #DataSpaces

  17. @bobwyman,

    Yes!

    BTW -- using an #HTTP-based #Hyperlink as an Entity Name addresses the concerns you've raised.

    Thanks to the #Fediverse, the power of hyperlink-base entity names will become increasingly obvious, as hashtags demonstrate right now 😀

    Here's a publicly accessible #GoogleSpreadsheet that demonstrates hyperlink-based unambiguous entity names (a/k/a #WebID).

    docs.google.com/spreadsheets/d

    /cc @ben @MildlyAggrievedScientist

    #DataConnectivity #OpenWeb #Identity

  18. I've always had multiple tools for processing #RSS. Net effect, I can search back into my own database of interesting posts from the past.

    Here's a gem from @anildash, regarding "Link In Bio" and Links in general -- regarding the miracle we know as the #Web.

    anildash.com/2019/12/10/link-i

    A #hyperlink is an extraordinary piece of technology that's still partially understood -- especially by those who stubbornly push silos.

    SeeAlso:
    anildash.com/2022/04/13/a-web-

    #OpenWeb #WebWeWant

  19. Nice read about #FeedBurner, and the eternal flame if provided to the #Web via #RSS.

    tedium.co/2017/11/14/google-fe

    BTW -- our #URIBurner service [1] was coined after (and inspired by) FeedBurner, but with a focus on simplifying #LinkedData usage via proxyURIs that bring #hyperlink-based unambiguous entity naming to all :)

    Links:

    [1] linkeddata.uriburner.com/

  20. @atomicpoet,

    The magic of a #hyperlink lies in the ability to use it for unambiguous entity naming. Unfortunately, this super-power is generally misunderstood.

    #Web #AWWW #LinkedData #WebWeWant

  21. @demosthenes,

    The key thing here is unambiguous denotation, using a #hyperlink.

    Ultimately, we can all interpret as we see fit -- thanks to the underlying "horses for courses" nature of #HTTP based entity denotation.

    As indicated, if you take the HTTP-based topic denotation route -- it leads to progressive and unobtrusive #KnowledgeGraph construction 😀

    {
    mastodon:KnowledgeGraph
    owl:sameAs
    dbpedia:KnowledgeGraph,
    wd:Q33002955 .
    }

    /cc @vrandecic @nichtich

    #Nanotation