Notices tagged with activitypub, page 5

  1. @oxenfree @cybermeow @elizafox @cyberpotato @cajun @thatbrickster @lain @heluecht

    Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for # and #

    I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship.

    So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.

    Monday, 11-Sep-17 08:50:08 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context Repeated by akionux
  2. @chriswere @elizafox doesn't # already allow for selective federation with other servers? I hear it has implemented #

    Friday, 15-Sep-17 15:14:16 UTC from quitter.se
  3. @bob @rbonifaz @sri that's great news (I presume). Does # include standards for federated !groups?

    Thursday, 14-Sep-17 07:47:50 UTC from quitter.se
  4. @rbonifaz @sri # is an attempt to provide all the features and benefits of #, #, and #'s variant of OStatus

    Thursday, 14-Sep-17 06:46:16 UTC from quitter.se in context
  5. @rbonifaz @sri unless something changed in the last couple of months, # uses #, not #, and doesn't support groups

    Thursday, 14-Sep-17 06:43:26 UTC from quitter.se in context
  6. @ajpz I was wondering if something like greater implementation of the draft # spec was increasing interconnections? See the map

    Wednesday, 13-Sep-17 09:08:44 UTC from quitter.se
  7. Apparently the folks working on the # spec have asked for some formal feedback to inform a final version
    http://qttr.at/1i0s

    Wednesday, 13-Sep-17 09:07:22 UTC from quitter.se in context
  8. @oxenfree @cybermeow @elizafox @cyberpotato @cajun @thatbrickster @lain @heluecht

    Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for # and #

    I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship.

    So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.

    Monday, 11-Sep-17 08:50:08 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context Repeated by therubackup
  9. @oxenfree @cybermeow @elizafox @cyberpotato @cajun @thatbrickster @lain @heluecht

    Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for # and #

    I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship.

    So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.

    Monday, 11-Sep-17 08:50:08 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context
  10. @cwebber Indeed you and others involved with AP spec development have been very inclusive, inviting and encouraging. I very much appreciate your (and everyone else's) efforts that have been put into #

    Tuesday, 05-Sep-17 22:40:10 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E in context
  11. @cwebber The only reason !GNUsocial doesn't have # yet is because I have a fulltime job and noone else has been up for the task .]

    Though I'm pretty sure it'd still just be the 100% public parts of AP that would be used/promoted, as I'm pretty much convinced there's no such thing as privacy in the social sphere anyway and anyone using "private" communication in an environment like !GNUsocial or # is fooled either by the platform, the administrator or other users. (anything accessible via a web browser isn't made for privacy)

    Tuesday, 05-Sep-17 22:37:58 UTC from social.umeahackerspace.se at 63°49'42"N 20°15'34"E
  12. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by dogjaw
  13. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W Repeated by moonman
  14. :

    I plan on writing an implementation.

    * In Common Lisp, because I want to get better at CL.
    * Client-facing server is top priority.
    * Federating server is second priority.
    * Client is least priority.
    * Client-facing server will use ROCA style.
    * Each part will implement checklist on AP Github.
    * All components will be as loosely coupled as possible.

    Wednesday, 05-Jul-17 15:00:45 UTC from glitch.social in context Repeated by hector
  15. :

    I plan on writing an implementation.

    * In Common Lisp, because I want to get better at CL.
    * Client-facing server is top priority.
    * Federating server is second priority.
    * Client is least priority.
    * Client-facing server will use ROCA style.
    * Each part will implement checklist on AP Github.
    * All components will be as loosely coupled as possible.

    Wednesday, 05-Jul-17 15:00:45 UTC from glitch.social in context
  16. I'm perfectly happy that # exists, and if it implements # in a future version, more power to it. And if it drops # support, well, that's what forks (or reimplementations) like # are for. But don't blame # developers for not following #'s road map for the future.

    Wednesday, 05-Jul-17 01:58:46 UTC from sn.jonkman.ca at 43°36'0"N 80°32'58"W
  17. @deadsuperhero Inspiring news! Glad that I noticed them at least now :-)
    I didn't think # adoption campaign could be so active :-)
    Just this weekend I started to refactor internal data model of # from "messages"/"users" with some "favorited", "followed" etc. attributes to "activities" with actors and actions... I'm trying to use terminology of ActivityPub/ActivityStreams as much as possible in order to make application's code more transparent...
    @maiyannah @cwebber @bob

    Monday, 22-May-17 05:52:13 UTC from loadaverage.org in context
  18. Oh boy, Evan Prodromou (of #StatusNet / #Pump / #OStatus fame) showed up on #Diaspora's GitHub Issue tracker and asked that we support #ActivityPub

    It's a nice thought, and hopefully we can do that in the long term. But some part of me is apprehensive about the spec and the leg work it will take to support it.

    There are certain unanswered questions, such as "Will ActivityPub support Diaspora's federated privacy controls?"

    Tuesday, 11-Apr-17 17:34:18 UTC from social.nasqueron.org Repeated by andstatus
  19. Yesterday I was implementing # API in # Comparing AndStatus with # client at some point I noticed that Tusky shows me a new post, which mentions myself. But I couldn't find the same post in any timeline that AndStatus feeds from the Mastodon server. It appeared that in addition to Twitter/GNU Social-like timelines Mastodon has something conceptually similar to an "Activity stream" that is called "Notifications" here and, as other parts of the API, is "hand made" :-) Actually, this is a good sign, showing that ideas of # (currently represented by the # standard https://www.w3.org/TR/activitypub/ ) are growing in the heads of the Mastodon developers. I would go one step further and formulate all timelines and actions as activities and activity streams... It's interesting that these ideas are growing in _my_ head also :-) - I decided that internal AndStatus model of notifications will be based on Ac

    Sunday, 14-May-17 07:32:14 UTC from loadaverage.org Repeated by andstatus
  20. Yesterday I was implementing # API in # Comparing AndStatus with # client at some point I noticed that Tusky shows me a new post, which mentions myself. But I couldn't find the same post in any timeline that AndStatus feeds from the Mastodon server. It appeared that in addition to Twitter/GNU Social-like timelines Mastodon has something conceptually similar to an "Activity stream" that is called "Notifications" here and, as other parts of the API, is "hand made" :-) Actually, this is a good sign, showing that ideas of # (currently represented by the # standard https://www.w3.org/TR/activitypub/ ) are growing in the heads of the Mastodon developers. I would go one step further and formulate all timelines and actions as activities and activity streams... It's interesting that these ideas are growing in _my_ head also :-) - I decided that internal AndStatus model of notifications will be based on Ac

    Sunday, 14-May-17 07:32:14 UTC from loadaverage.org
  21. @rayalez are you still developing #? If not, are you work on # support for #?
    http://qttr.at/1tg5

    Friday, 05-May-17 03:05:54 UTC from quitter.se
  22. @zatnosk a plug-in for # would connect to the existing # for now, another plug-in could be developed for #

    Tuesday, 25-Apr-17 13:44:08 UTC from quitter.se in context
  23. @kevinmarks @cdllm the main contenders for replacements that address the privacy needs are # and # See:
    http://qttr.at/1sex

    Tuesday, 18-Apr-17 02:14:40 UTC from quitter.se in context
  24. @cdllm @cdllm #, #, #, # and others are currently competing to be the successor to #

    Monday, 17-Apr-17 13:31:21 UTC from quitter.se in context
  25. The way to reintegrate the # is not to implement OStatus in pump.io, but to implement # in pump.io and GNU Social and derivatives. pump.io does have AP implementation as a goal.

    # and # will be the first implementations, from the looks of it.

    Wednesday, 12-Apr-17 23:54:17 UTC from social.heldscal.la Repeated by xj9
  26. The way to reintegrate the # is not to implement OStatus in pump.io, but to implement # in pump.io and GNU Social and derivatives. pump.io does have AP implementation as a goal.

    # and # will be the first implementations, from the looks of it.

    Wednesday, 12-Apr-17 23:54:17 UTC from social.heldscal.la
  27. Oh boy, Evan Prodromou (of #StatusNet / #Pump / #OStatus fame) showed up on #Diaspora's GitHub Issue tracker and asked that we support #ActivityPub

    It's a nice thought, and hopefully we can do that in the long term. But some part of me is apprehensive about the spec and the leg work it will take to support it.

    There are certain unanswered questions, such as "Will ActivityPub support Diaspora's federated privacy controls?"

    Tuesday, 11-Apr-17 17:34:18 UTC from social.nasqueron.org
  28. @sonyam pump.io has private messaging, followers-only posting, federated identity so you can run around on other servers and comment using your home id, the API is lightweight and very consistent and understandable in comparison with GS+Qvitter (I hear), and it's the basis for the Next Big Thing, #

    pump.io was built in a few months by one guy though, and GS was built in a couple of years by several full-time people, so there are still quirks in the (actually intentionally) limited web UI. pump.io works best with a client.

    @andstatus does a decent job. I'm not going to complain, because I still didn't file those bugs since last I complained, so the buck is with me. It's mostly about message formatting, other than that it's an awesome client for both GS and pump.

    Saturday, 18-Mar-17 21:48:12 UTC from social.heldscal.la Repeated by andstatus
  29. @sonyam pump.io has private messaging, followers-only posting, federated identity so you can run around on other servers and comment using your home id, the API is lightweight and very consistent and understandable in comparison with GS+Qvitter (I hear), and it's the basis for the Next Big Thing, #

    pump.io was built in a few months by one guy though, and GS was built in a couple of years by several full-time people, so there are still quirks in the (actually intentionally) limited web UI. pump.io works best with a client.

    @andstatus does a decent job. I'm not going to complain, because I still didn't file those bugs since last I complained, so the buck is with me. It's mostly about message formatting, other than that it's an awesome client for both GS and pump.

    Saturday, 18-Mar-17 21:48:12 UTC from social.heldscal.la
  30. IIUC # has convo anti-ghost measures.

    Tuesday, 24-Jan-17 14:40:10 UTC from gs.kawa-kun.com