Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Fred Gibson
    @gibsonf1
    Looks like all but the turtle is https: https://www.w3.org/ns/activitystreams# so I'll switch it to that
    Fred Gibson
    @gibsonf1
    I'm a bit confused on what as:bto means: "Identifies an Object that is part of the private primary audience of this Object." can anyone elaborate on what this is exactly?
    The example has:
    {
      "@context": "https://www.w3.org/ns/activitystreams",
      "summary": "Sally offered a post to John",
      "type": "Offer",
      "actor": "http://sally.example.org",
      "object": "http://example.org/posts/1",
      "target": "http://john.example.org",
      "bto": [ "http://joe.example.org" ]
    }
    So in this case, what would bto do for joe?
    Aaron Coburn
    @acoburn
    the as:to field defines the "primary audience" of the as:Object. The as:cc field defines the "secondary audience" of the as:Object. In the context of email, bcc is the "blind" form of cc as it is with AS2.0. Similarly, as:bto is the "blind" form of as:to
    So, in this case, as:bto would send the message to http://joe.example.org, but in such a way that other recipients would not see that this user was a recipient
    Fred Gibson
    @gibsonf1
    Thanks @acoburn
    Sarven Capadisli
    @csarven
    Carried over from last week.
    elf Pavlik
    @elf-pavlik
    PR for github workflow to render mermaid diagrams solid/notifications#39
    Fred Gibson
    @gibsonf1
    I think it would also be good to have an as:UnFollow as a complement to the as:Follow Activity
    Christoph Braun
    @uvdsl
    Wouldn't that be an as:Undo with as:object being an follow action?
    That is what I am using at the moment...
    Fred Gibson
    @gibsonf1
    @uvdsl Good idea!
    elf Pavlik
    @elf-pavlik
    solid/notifications#39 merged and github pages now serves the gh-pages branch https://solid.github.io/notifications/protocol
    Aaron Coburn
    @acoburn
    I will not be able to attend Thursday's Notification Panel meeting. I assume this is the agenda for the meeting: https://hackmd.io/86QK1g2_SpONRBF_3YqZiQ
    elf Pavlik
    @elf-pavlik
    I will also not be able to join tomorrow, I added my name to the Regrets section.
    CxRes
    @CxRes
    Sorry about missing this one as well, I am still sick.
    Sarven Capadisli
    @csarven
    Pete Edwards
    @edwardsph
    Sorry - I wasn't planning on attending either but I suspect you already won't have 5
    Sarven Capadisli
    @csarven
    @CxRes Get well.
    Waves to @kushaldas
    Kushal Das
    @kushaldas
    @csarven thank you :)
    Sarven Capadisli
    @csarven
    • 2020-02-17 cancelled. Let's try 2022-02-24.
    Sarven Capadisli
    @csarven
    I'm in the process of making some updates / referencing existing issues.. so expect minor changes until meeting.
    elf Pavlik
    @elf-pavlik
    Hi :wave: Are we going to meet today?
    Sarven Capadisli
    @csarven
    Yes. I'll post an agenda.
    elf Pavlik
    @elf-pavlik
    Tiny PR replacing png with mmd sources: solid/notifications#40
    CxRes
    @CxRes
    Are we meeting?
    Sarven Capadisli
    @csarven
    CxRes
    @CxRes
    Something I feel we should plan for is to systematically work through issues and see if we can move them into PRs
    Sarven Capadisli
    @csarven
    I'll update the agenda and notify here before the meeting.
    elf Pavlik
    @elf-pavlik
    I created this PR which only affects publishing of StreamingHTTP subscription type: solid/notifications#42
    Not sure if anyone needs to review it or I should just go ahead and merge it?
    Sarven Capadisli
    @csarven
    Aaron Coburn
    @acoburn
    I will be there in a few minutes
    Kushal Das
    @kushaldas
    I am missing the meeting due to another training.
    Ted Thibodeau Jr
    @TallTed
    Artificial limits make no sense to me. SemVer is typical (declared, I believe) practice across Solid.
    Ted Thibodeau Jr
    @TallTed
    +1 0.7 or any arbitrary version is fine by me. I think the <1.0 decision makes sense as it's not quite fully baked.
    Sarven Capadisli
    @csarven

    Based on my calculations [.. checks notes ..], tomorrow's meeting ( 2022-03-17 ) will be held at 15:00 CET / 14:00 GMT / 10:00 EST.

    If that still works for everyone, great. If not, please chime in.

    elf Pavlik
    @elf-pavlik
    @jaxoncreed would you be able to join tomorrow?
    jaxoncreed
    @jaxoncreed
    Yeah I can join
    elf Pavlik
    @elf-pavlik
    :rocket:
    Igor Jakovljevic
    @IgorJakovljevic
    Hi all, I would also like to join today's meeting. Does someone have to approve access for me or do I just join via the link on the Github repository :) A quick intro for those that do not know me (probably all of you), I am a PhD student working at CERN on the CERN Notifications Project.
    Sarven Capadisli
    @csarven
    @IgorJakovljevic You're welcome to join as a guest or as a member of the Solid CG. If you'd like to make contributions to the specs, eg., creating/updating technical reports or voting in meetings when necessary, then we ask that participants first join the Solid CG.
    Igor Jakovljevic
    @IgorJakovljevic
    @csarven amazing, thanks :D I will join as a guest for now and see if I can contribute somehow :D
    Sarven Capadisli
    @csarven
    ^ Please note "Date: 2022-03-17T14:00:00Z" .. meeting in 35 minutes as of this writing.
    elf Pavlik
    @elf-pavlik
    I hope we will find 5 min to get quick feedback on: solid/notifications#49