Notices tagged with activitypub, page 5
-
@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 #Mastodon and #ActivityPub.
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 -
@chriswere @elizafox doesn't #Mastodon already allow for selective federation with other servers? I hear it has implemented #ActivityPub
-
@bob @rbonifaz @sri that's great news (I presume). Does #ActivityPub include standards for federated !groups?
-
@rbonifaz @sri unless something changed in the last couple of months, #Mastodon uses #OStatus, not #ActivityPub, and doesn't support groups
-
@ajpz I was wondering if something like greater implementation of the draft #ActivityPub spec was increasing interconnections? See the map
-
Apparently the folks working on the #ActivityPub spec have asked for some formal feedback to inform a final version
http://qttr.at/1i0s -
@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 #Mastodon and #ActivityPub.
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 -
@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 #Mastodon and #ActivityPub.
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. -
@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 #ActivityPub.
-
@cwebber The only reason !GNUsocial doesn't have #ActivityPub 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 #Mastodon is fooled either by the platform, the administrator or other users. (anything accessible via a web browser isn't made for privacy) -
I'm perfectly happy that #Mastodon exists, and if it implements #ActivityPub in a future version, more power to it. And if it drops #OStatus support, well, that's what forks (or reimplementations) like #Mastodon are for. But don't blame #GNUsocial developers for not following #Mastodon's road map for the future.
-
I'm perfectly happy that #Mastodon exists, and if it implements #ActivityPub in a future version, more power to it. And if it drops #OStatus support, well, that's what forks (or reimplementations) like #Mastodon are for. But don't blame #GNUsocial developers for not following #Mastodon's road map for the future.
-
I plan on writing an #ActivityPub 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. -
I plan on writing an #ActivityPub 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. -
I'm perfectly happy that #Mastodon exists, and if it implements #ActivityPub in a future version, more power to it. And if it drops #OStatus support, well, that's what forks (or reimplementations) like #Mastodon are for. But don't blame #GNUsocial developers for not following #Mastodon's road map for the future.
-
@deadsuperhero Inspiring news! Glad that I noticed them at least now :-)
I didn't think #ActivityPub adoption campaign could be so active :-)
Just this weekend I started to refactor internal data model of #AndStatus 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 -
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?"
-
Yesterday I was implementing #Mastodon API in #AndStatus. Comparing AndStatus with #Tusky 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 #ActivityStreams (currently represented by the #ActivityPub 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…
-
Yesterday I was implementing #Mastodon API in #AndStatus. Comparing AndStatus with #Tusky 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 #ActivityStreams (currently represented by the #ActivityPub 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…
-
@rayalez are you still developing #Nexus? If not, are you work on #ActivityPub support for #Mastodon?
http://qttr.at/1tg5 -
@zatnosk a plug-in for #OStatus would connect to the existing #Fediverse for now, another plug-in could be developed for #ActivityPub
-
@kevinmarks @cdllm the main contenders for replacements that address the privacy needs are #ActivityPub and #Zot. See:
http://qttr.at/1sex -
The way to reintegrate the #fediverse is not to implement OStatus in pump.io, but to implement #ActivityPub in pump.io and GNU Social and derivatives. pump.io does have AP implementation as a goal.
#mediagoblin and #pleroma will be the first implementations, from the looks of it. -
The way to reintegrate the #fediverse is not to implement OStatus in pump.io, but to implement #ActivityPub in pump.io and GNU Social and derivatives. pump.io does have AP implementation as a goal.
#mediagoblin and #pleroma will be the first implementations, from the looks of it. -
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?"
-
@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, #activitypub.
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. -
@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, #activitypub.
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. -
IIUC #ActivityPub has convo anti-ghost measures.