home.social

#foaf — Public Fediverse posts

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

fetched live
  1. @orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam

    ==Email==

    Maybe I only need to receive email over SMTP.

    Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?

    Perhaps even?

    Perhaps as part of NNCPNET?

    Maybe (text-only) also via NNCP?

    Edit: bc I just found and and think this could be a solution

    ==Webdev==

    I can use as needed ¯\_(ツ)_/¯

  2. @orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam

    ==Email==

    Maybe I only need to receive email over SMTP.

    Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?

    Perhaps #FOAF even?

    Perhaps as part of NNCPNET?

    Maybe (text-only) #USENET also via NNCP?

    Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution

    ==Webdev==

    I can use #RubyOnRails as needed ¯\_(ツ)_/¯

  3. @orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam

    ==Email==

    Maybe I only need to receive email over SMTP.

    Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?

    Perhaps #FOAF even?

    Perhaps as part of NNCPNET?

    Maybe (text-only) #USENET also via NNCP?

    Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution

    ==Webdev==

    I can use #RubyOnRails as needed ¯\_(ツ)_/¯

  4. @orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam

    ==Email==

    Maybe I only need to receive email over SMTP.

    Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?

    Perhaps #FOAF even?

    Perhaps as part of NNCPNET?

    Maybe (text-only) #USENET also via NNCP?

    Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution

    ==Webdev==

    I can use #RubyOnRails as needed ¯\_(ツ)_/¯

  5. @orsinium I know, they stole email from us claiming to combat spam and somehow there is still spam

    ==Email==

    Maybe I only need to receive email over SMTP.

    Otherwise email transfer using NNCP with known-trusted-hosts of friends and family?

    Perhaps #FOAF even?

    Perhaps as part of NNCPNET?

    Maybe (text-only) #USENET also via NNCP?

    Edit: bc I just found #NNCP and #NNCPNET and think this could be a solution

    ==Webdev==

    I can use #RubyOnRails as needed ¯\_(ツ)_/¯

  6. Circles #etc #google #facebook #twitter #socialgraph #opengraph #opensocial #foaf #xup #altly #diaspora #buzz #wave Did the Google+ Circles concept revolutionize social networking, and what we should have instead.

    ithoughthecamewithyou.com/post

  7. Circles #etc #google #facebook #twitter #socialgraph #opengraph #opensocial #foaf #xup #altly #diaspora #buzz #wave Did the Google+ Circles concept revolutionize social networking, and what we should have instead.

    ithoughthecamewithyou.com/post

  8. Circles #etc #google #facebook #twitter #socialgraph #opengraph #opensocial #foaf #xup #altly #diaspora #buzz #wave Did the Google+ Circles concept revolutionize social networking, and what we should have instead.

    ithoughthecamewithyou.com/post

  9. Circles #etc #google #facebook #twitter #socialgraph #opengraph #opensocial #foaf #xup #altly #diaspora #buzz #wave Did the Google+ Circles concept revolutionize social networking, and what we should have instead.

    ithoughthecamewithyou.com/post

  10. 🆕 Introducing four new "RDF Vocabularies on Elixir" projects:

    - SKOS.ex
    - FOAF.ex
    - PROV.ex
    - DCAT.ex

    These provide Grax schemas for all classes of the respective RDF vocabularies, so you can easily load RDF graph data into Elixir structures or create them from scratch.

    Find all projects here: github.com/rdf-elixir

    (2/3)
    #rdf #skos #foaf #prov #dcat

  11. 🆕 Introducing four new "RDF Vocabularies on Elixir" projects:

    - SKOS.ex
    - FOAF.ex
    - PROV.ex
    - DCAT.ex

    These provide Grax schemas for all classes of the respective RDF vocabularies, so you can easily load RDF graph data into Elixir structures or create them from scratch.

    Find all projects here: github.com/rdf-elixir

    (2/3)
    #rdf #skos #foaf #prov #dcat

  12. 🆕 Introducing four new "RDF Vocabularies on Elixir" projects:

    - SKOS.ex
    - FOAF.ex
    - PROV.ex
    - DCAT.ex

    These provide Grax schemas for all classes of the respective RDF vocabularies, so you can easily load RDF graph data into Elixir structures or create them from scratch.

    Find all projects here: github.com/rdf-elixir

    (2/3)
    #rdf #skos #foaf #prov #dcat

  13. 🆕 Introducing four new "RDF Vocabularies on Elixir" projects:

    - SKOS.ex
    - FOAF.ex
    - PROV.ex
    - DCAT.ex

    These provide Grax schemas for all classes of the respective RDF vocabularies, so you can easily load RDF graph data into Elixir structures or create them from scratch.

    Find all projects here: github.com/rdf-elixir

    (2/3)
    #rdf #skos #foaf #prov #dcat

  14. Dan Bri and Libby Miller created a specification called FOAF xmlns.com/foaf/spec; latest version is almost a decade old. Remembering using it and thinking it was a great and easy way to ride on top of html and let the spiders and indexers build a graph that could be traversed db style. It really is a solid basis to build on what we should have referenced as Web3 back then. Many of the semantics could easily fit right into ActivityPub w3.org/TR/activitypub/ and with a trust algorithm you essentially have a real basis for what is Web3 as explained without a middle man, fees, protocols that aren’t distributed and etc. Need to think about it more, I’m sure it breaks down somewhere but seeing as you can keep existing protocols without major modification while ensuring security through trust metrics and possibly even taking it all the way down to the likes of standard system libs, could be something worth investigating. Wonder why Dan and Libby stopped? 🤔#foafstodon #foaf #web3 #distributedsystems

  15. Dan Bri and Libby Miller created a specification called FOAF xmlns.com/foaf/spec; latest version is almost a decade old. Remembering using it and thinking it was a great and easy way to ride on top of html and let the spiders and indexers build a graph that could be traversed db style. It really is a solid basis to build on what we should have referenced as Web3 back then. Many of the semantics could easily fit right into ActivityPub w3.org/TR/activitypub/ and with a trust algorithm you essentially have a real basis for what is Web3 as explained without a middle man, fees, protocols that aren’t distributed and etc. Need to think about it more, I’m sure it breaks down somewhere but seeing as you can keep existing protocols without major modification while ensuring security through trust metrics and possibly even taking it all the way down to the likes of standard system libs, could be something worth investigating. Wonder why Dan and Libby stopped? 🤔#foafstodon #foaf #web3 #distributedsystems

  16. Dan Bri and Libby Miller created a specification called FOAF xmlns.com/foaf/spec; latest version is almost a decade old. Remembering using it and thinking it was a great and easy way to ride on top of html and let the spiders and indexers build a graph that could be traversed db style. It really is a solid basis to build on what we should have referenced as Web3 back then. Many of the semantics could easily fit right into ActivityPub w3.org/TR/activitypub/ and with a trust algorithm you essentially have a real basis for what is Web3 as explained without a middle man, fees, protocols that aren’t distributed and etc. Need to think about it more, I’m sure it breaks down somewhere but seeing as you can keep existing protocols without major modification while ensuring security through trust metrics and possibly even taking it all the way down to the likes of standard system libs, could be something worth investigating. Wonder why Dan and Libby stopped? 🤔#foafstodon #foaf #web3 #distributedsystems

  17. Dan Bri and Libby Miller created a specification called FOAF xmlns.com/foaf/spec; latest version is almost a decade old. Remembering using it and thinking it was a great and easy way to ride on top of html and let the spiders and indexers build a graph that could be traversed db style. It really is a solid basis to build on what we should have referenced as Web3 back then. Many of the semantics could easily fit right into ActivityPub w3.org/TR/activitypub/ and with a trust algorithm you essentially have a real basis for what is Web3 as explained without a middle man, fees, protocols that aren’t distributed and etc. Need to think about it more, I’m sure it breaks down somewhere but seeing as you can keep existing protocols without major modification while ensuring security through trust metrics and possibly even taking it all the way down to the likes of standard system libs, could be something worth investigating. Wonder why Dan and Libby stopped? 🤔#foafstodon #foaf #web3 #distributedsystems

  18. Here's an article about the federated social network that never was. By putting a #FOAF file on your homepage, the #SemanticWeb would have linked us all together, at least in theory. I'm going to update my FOAF file tonight.

    twobithistory.org/2020/01/05/f

    #foafstodon #SmallWeb #AlternateHistory

  19. Here's an article about the federated social network that never was. By putting a #FOAF file on your homepage, the #SemanticWeb would have linked us all together, at least in theory. I'm going to update my FOAF file tonight.

    twobithistory.org/2020/01/05/f

    #foafstodon #SmallWeb #AlternateHistory

  20. @Edent @trwnh
    OGP is based on #RDF.
    Just use community driven, tested and proven vocabularies like #FOAF

  21. @Edent @trwnh
    OGP is based on #RDF.
    Just use community driven, tested and proven vocabularies like #FOAF

  22. @Edent @trwnh
    OGP is based on #RDF.
    Just use community driven, tested and proven vocabularies like #FOAF

  23. @Edent @trwnh
    OGP is based on #RDF.
    Just use community driven, tested and proven vocabularies like #FOAF

  24. @Edent @trwnh
    OGP is based on #RDF.
    Just use community driven, tested and proven vocabularies like #FOAF

  25. @burningbird @AKMA @anildash @davew Do they serve a purpose? Well, they would for some people in some instances. But especially if they were programmatically accessible someone might figure out how to use them to create loose, asymmetrical social networks of a different sort. #ForlornHopes #FOAF #DanBrickley #LibbyMiller

  26. @burningbird @AKMA @anildash @davew Do they serve a purpose? Well, they would for some people in some instances. But especially if they were programmatically accessible someone might figure out how to use them to create loose, asymmetrical social networks of a different sort. #ForlornHopes #FOAF #DanBrickley #LibbyMiller

  27. @burningbird @AKMA @anildash @davew Do they serve a purpose? Well, they would for some people in some instances. But especially if they were programmatically accessible someone might figure out how to use them to create loose, asymmetrical social networks of a different sort. #ForlornHopes #FOAF #DanBrickley #LibbyMiller

  28. @burningbird @AKMA @anildash @davew Do they serve a purpose? Well, they would for some people in some instances. But especially if they were programmatically accessible someone might figure out how to use them to create loose, asymmetrical social networks of a different sort. #ForlornHopes #FOAF #DanBrickley #LibbyMiller

  29. @burningbird @AKMA @anildash @davew Do they serve a purpose? Well, they would for some people in some instances. But especially if they were programmatically accessible someone might figure out how to use them to create loose, asymmetrical social networks of a different sort. #ForlornHopes #FOAF #DanBrickley #LibbyMiller

  30. @janmartinkeil It was more a high level overview of this field, this event is to network with other fields to exchange knowledge and ideas.

    Regarding your points (my view):

    Ontologies are more like the description of how the data is modeled. For example, the ontology #FOAF says `foaf:Person` is a Person. While the #KnowledgeGraph (KG) will have `<Dylan> rdf:type foaf:Person` to say that I'm a person modeled according to the FOAF ontology. The data in the KG is modeled after the ontology.

  31. @janmartinkeil It was more a high level overview of this field, this event is to network with other fields to exchange knowledge and ideas.

    Regarding your points (my view):

    Ontologies are more like the description of how the data is modeled. For example, the ontology says `foaf:Person` is a Person. While the (KG) will have `<Dylan> rdf:type foaf:Person` to say that I'm a person modeled according to the FOAF ontology. The data in the KG is modeled after the ontology.

  32. @janmartinkeil It was more a high level overview of this field, this event is to network with other fields to exchange knowledge and ideas.

    Regarding your points (my view):

    Ontologies are more like the description of how the data is modeled. For example, the ontology #FOAF says `foaf:Person` is a Person. While the #KnowledgeGraph (KG) will have `<Dylan> rdf:type foaf:Person` to say that I'm a person modeled according to the FOAF ontology. The data in the KG is modeled after the ontology.

  33. One of my favorite things here is how #FOAF works here.

    So many great people to follow!

  34. One of my favorite things here is how #FOAF works here.

    So many great people to follow!

  35. One of my favorite things here is how #FOAF works here.

    So many great people to follow!

  36. One of my favorite things here is how #FOAF works here.

    So many great people to follow!

  37. @judeswae @kfleerko @mfowler @mheiber

    #semanticWeb and #FOAF, the ability to connect to a data mesh a layer of people, org structure and roles, etc.

    Imagine I push out a new design or idea and what to start gathering feedback on it asap

  38. @judeswae @kfleerko @mfowler @mheiber

    #semanticWeb and #FOAF, the ability to connect to a data mesh a layer of people, org structure and roles, etc.

    Imagine I push out a new design or idea and what to start gathering feedback on it asap

  39. @judeswae @kfleerko @mfowler @mheiber

    #semanticWeb and #FOAF, the ability to connect to a data mesh a layer of people, org structure and roles, etc.

    Imagine I push out a new design or idea and what to start gathering feedback on it asap

  40. @judeswae @kfleerko @mfowler @mheiber

    #semanticWeb and #FOAF, the ability to connect to a data mesh a layer of people, org structure and roles, etc.

    Imagine I push out a new design or idea and what to start gathering feedback on it asap

  41. @martinmcwhorter Yea, that kind of ad is not going to work here.

    For intranet, this is however a place you can possibly build on top of the API services too, and build a way to have linked conversations over topics that people can find - in big, siloed businesses that could be a benefit.

    Slack, Teams, etc are not great - they still create too many silos.

    Here I'm seeing #FOAF and other #ontologies at play.

  42. @martinmcwhorter Yea, that kind of ad is not going to work here.

    For intranet, this is however a place you can possibly build on top of the API services too, and build a way to have linked conversations over topics that people can find - in big, siloed businesses that could be a benefit.

    Slack, Teams, etc are not great - they still create too many silos.

    Here I'm seeing #FOAF and other #ontologies at play.

  43. @martinmcwhorter Yea, that kind of ad is not going to work here.

    For intranet, this is however a place you can possibly build on top of the API services too, and build a way to have linked conversations over topics that people can find - in big, siloed businesses that could be a benefit.

    Slack, Teams, etc are not great - they still create too many silos.

    Here I'm seeing #FOAF and other #ontologies at play.

  44. @martinmcwhorter Yea, that kind of ad is not going to work here.

    For intranet, this is however a place you can possibly build on top of the API services too, and build a way to have linked conversations over topics that people can find - in big, siloed businesses that could be a benefit.

    Slack, Teams, etc are not great - they still create too many silos.

    Here I'm seeing #FOAF and other #ontologies at play.

  45. Clearly this is a sign we need to have an IndieWebCamp in Vienna #indie #foaf