GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by unsafe { Sir Alecks Gates } (agates@activitypub.agates.io), page 2

  1. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Sunday, 23-Apr-2023 09:02:49 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Adam Curry :pci: :pc2blue:
    • John Livingston
    • silverpill
    • Dave
    • Steven Bell :pci:
    @silverpill

    Not directly related but

    1) We're having similar talks with @John_Livingston regarding aligning chat specifications between the Podcast XML namespace and ActivityPub. I wonder if we could come up with some kind of "best practices" for going between XML Schema <-> JSON-LD?
    2) Similarly, @John_Livingston mentioned PeerTube 5.1.0 allows plugins to modify the ActivityPub object which would allow this functionally, once we decide what it could be

    CC @dave @errhead

    @StevenB @adam
    In conversation Sunday, 23-Apr-2023 09:02:49 JST from activitypub.agates.io permalink
  2. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Saturday, 18-Feb-2023 01:52:31 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • silverpill
    • errhead
    @silverpill

    Okay, that's good to know.

    I guess the other part we're thinking of is this:

    Say you start/own a thread for comments on a podcast or video. Someone from another instance makes a reply directly to the top-level AP object with highly illegal content and you want to delete it on your side to prevent it from being seen by others.

    While it's marked as deleted in your "gui", as peertube appears to be doing, should we expect to omit the "deleted" object from the replies/comments collection?

    Or do we merely rely on reporting + moderation and hope it's deleted eventually, even though we might not see the deleted activity?

    @alex @errhead @errhead
    In conversation Saturday, 18-Feb-2023 01:52:31 JST from activitypub.agates.io permalink
  3. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Friday, 17-Feb-2023 12:42:40 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • errhead
    @errhead Looks like it hasn't been removed from the comments collection. That could be caching or it might not be removed at all.

    @alex What is the generally expected behavior in a situation like this? We're trying to determine what AP servers do/expect when comments are "deleted" or "hidden" from a thread if you don't control the originating server.
    In conversation Friday, 17-Feb-2023 12:42:40 JST from activitypub.agates.io permalink

    Attachments


    1. https://activitypub.agates.io/media/d51f36a7-9c53-4afd-b34a-280a4b2cf9b7/image.png?name=image.png
  4. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Saturday, 31-Dec-2022 08:33:49 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • Nickolas
    Which company was this?

    Such a friendly and inviting project, not suspicious at all.
    In conversation Saturday, 31-Dec-2022 08:33:49 JST from activitypub.agates.io permalink
  5. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Saturday, 31-Dec-2022 05:57:15 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • Nickolas
    @alex didn't you do a bunch of AP work for them and they rejected it?
    In conversation Saturday, 31-Dec-2022 05:57:15 JST from activitypub.agates.io permalink
  6. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Tuesday, 27-Dec-2022 01:29:57 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • anongo
    @alex

    Have you considered OMEMO? Works very well for XMPP.

    @anongo
    In conversation Tuesday, 27-Dec-2022 01:29:57 JST from activitypub.agates.io permalink
  7. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Monday, 26-Dec-2022 02:38:40 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    • Alex Gleason
    Just upgraded to Rebased + Soapbox without a hitch. Thank you for the valuable software, @alex
    In conversation Monday, 26-Dec-2022 02:38:40 JST from activitypub.agates.io permalink
  8. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Saturday, 24-Dec-2022 03:31:01 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    • issdeinschnitzel
    • Dev
    @alex @issdeinschnitzel @dev @silverpill

    One of the issues I foresee is how we'll go about extending the AP schema from the client side while allowing users to post from a Mastodon-compatible API.

    Just as an example, if we want to add/utilize a podcast schema for ratings, there's no real way to do so unless the podcast application hosts their own AP server. Unless there's something I don't know about.

    Castopod has the problem solved from the *hosting* side but the client side is still up in the air.
    In conversation Saturday, 24-Dec-2022 03:31:01 JST from activitypub.agates.io permalink
  9. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Saturday, 24-Dec-2022 01:31:10 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    • Alex Gleason
    • issdeinschnitzel
    • Dev
    @silverpill @alex @issdeinschnitzel @dev

    I wish C2S was more prevalent.
    In conversation Saturday, 24-Dec-2022 01:31:10 JST from activitypub.agates.io permalink
  10. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Friday, 23-Dec-2022 09:27:48 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    in reply to
    • Alex Gleason
    @alex The main implication is when podcast clients query the ID with "Accept: application/activity+json", they have to fall back to the mastodon API for anything that doesn't implement the replies collection, causing more requests to happen anyway.
    In conversation Friday, 23-Dec-2022 09:27:48 JST from activitypub.agates.io permalink
  11. Embed this notice
    unsafe { Sir Alecks Gates } (agates@activitypub.agates.io)'s status on Friday, 23-Dec-2022 09:07:36 JST unsafe { Sir Alecks Gates } unsafe { Sir Alecks Gates }
    • Alex Gleason
    @alex Are you aware of any particular reason Pleroma doesn't implement the replies collection on AP objects? And does Rebased implement it?

    My attempts to add it to Pleroma are somewhat successful, although the object cache goes stales with new replies.
    In conversation Friday, 23-Dec-2022 09:07:36 JST from activitypub.agates.io permalink
  • After

User actions

    unsafe { Sir Alecks Gates }

    unsafe { Sir Alecks Gates }

    Podcasting 2.0 consultantMaster of the protocolsKnight of Podcasting 2.0

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          79151
          Member since
          23 Dec 2022
          Notices
          31
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.