[Social] More internal use of ActivityStreams?

[Mikael Nordfeldth]

Hello list,

I've been mostly active with the StatusNet codebase, but given that it's
essentially the same as the GNU Social codebase, I feel this may be the
correct place to have the discussion (especially as Evan Prodromou,
status.net/identi.ca, will be focusing his efforts on the
http://pump.io/ software).

Today the GNU Social/StatusNet software, and most other federated social
networking we plan to interact with, are focused around ActivityStreams
(in Atom or JSON), it would likely be good for the software to handle
these items not only externally but internally too.

Migrating to a mainly/entirely Activity based infrastructure would
simplify the coding necessary to enhance federation and maintain
compatibility in the future with possible protocol changes.

I'm curious if this mailing list thinks this is a good idea and would
appreciate work being made for an ActivityStreams oriented approach of
notice/activity handling, despite perhaps breaking some legacy plugins
and modifications.

(I believe it would also ease the migration to a less PHP dependent
codebase in the future, perhaps making it easier to exchange code with
other Free web service software such as GNU MediaGoblin which is Python)

--
Mikael Nordfeldth
Maintainer of https://freesocial.org/
http://www.ohloh.net/p/freesocial