@bleakgrey have you looked at the server>client aspects of the #ActivityPub spec? The idea is that if you support that, you can support any app that federates with AP, although for some reason Mastodon and Pleroma have decided to use a bespoke variant of server>client AP @Gargron@lain
I've settled on a name for my #ActivityPub#WordPress plugin - #Pterotype! It's an early precursor to the typewriter, which seemed appropriate for WordPress.
Honestly though, the main reason I chose it is now it can have a cute Pterodactyl logo. That will go nicely with Mastodon's prehistoric theme!
Now I just need to find someone who can draw a cute pterodactyl...
Man I could work on getting the #ActivityPub#golang implementation to v1 but there's #Oktoberfest this weekend in Munich and I hear the beers there are as big as my face. So mixing the two is definitely not an option.
Hello dear #Fediverse, I'm calling for your help in the development of another implementation of #ActivityPub to federate with everyone. There is a nice place #Juick.com which started more than 10 years ago as a microblogging service via Jabber/XMPP. Over the years the support of posting/commenting via Telegram and by email were added. And now it's time to move further - implement ActivityPub and federate!
Current developer @vt@juick.com has already done great job in learning specs and implementing the protocol. But he is facing some issues which he can't solve himself.
This is a post (in Russian) about where he is stuck: https://juick.com/vt/2919780 And there is my translation below. Please, contact him if you beleive you can help. Thanks a lot!
-- So I completely understood specs, implemented those in Juick and can consult others. 8) It's just not federating with other existing instances:
1) #Mastodon - public servers show profiles from Juick, number of followers and number of messages. But they don't show messages themselves. It's not clear how to diagnose. They don't reply to my bug reports ( https://github.com/tootsuite/mastodon/issues/8625 ). I also can't run it locally: out of 1Gb of ruby-scripts 500Mb of ruby-scripts with native extentions don't compile successfully on a Mac (how did they manage to use such extentions which are not working on a favourite OS of Ruby developers?). On Linux it also fails most likely due to lack of 1Gb RAM in the virtual machine.
2) #Pleroma - starts perfectly but it shows only avatars from Juick, the rest - not. And it constantly floods logs with database constraint errors (after searching a user it records this in its db, and then second search doesn't work as it assumes the user already exists!)
3) #Misskey - that either Japanese or Chinese product, looks weird itself... and I couldn't find user search there.
What else can I do? I'm ready to drop this and just leave email for users... :)
Does anyone know if there is an #ActivityPub#Meetup replacement in the works? I would much prefer to organize events in the Fediverse instead of on Meetup.com
I'd love to see an #ActivityPub UI that follows the original model of social network apps like Orkut and Friendster; all "friend" connections are 2-way (no following without being followed and vice-versa), and when a friend request is accepted you can see their friend list (by default, subject to the privacy settings of each user). This would be for more of a 'friends & family' use case, rather than a 'community of interest' or 'federated publishing and promotion' use case.
@rick_777@frankiesaxx@crickxson some of the apps haven't finished their implementations of #ActivityPub yet, and are still federating with Mastodon via #OStatus. I'm hopeful most of them will roll it out by the end of the year (or at the lastest mid-2019). In the meantime, the behaviour of the meta-federation of all the apps remains *very* complicated to explain to newbies ;) Email was probably the same in its first few years (#FidoNet between #BBS prior to the net etc)
@Goffi@enkiv2@mathew@bhtooefr the problem continues to be, how will the #FreeCode networks join up so they have a large enough network effect to compete with corporate #DataFarms? The fediverse apps all have agreed on #ActivityPub as the solution to this, even those like #Hubzilla whose developers have harsh criticisms of it. It seems unlikely they'll all implement #XMPP. Maybe the solution is something that does for your apps what #BridgyFed does for the #IndieWeb? https://fed.brid.gy/
@Goffi@wuhei@LWFlouisa tools that work with hashtags and !groups (once they get implemented in all the #ActivityPub apps) and help people filter the types of posts the are interested in out of the general firehose would be great. But follows, favourites (saving to find later), and reposts are basic functions that social media apps need to be what they are.
@macgirvin OK, so once that happens, and #Zap, #Osada, and #Hubzilla are all ready to use together with #Zot/6, there will be 3 reference implementations of Zot, which will hopefully help other projects implement it. But will Hubzilla still have federation plug-ins for #ActivityPub etc? Or will HZ users who to connect with users outside the Zot network need to clone their channel(s) onto an Osada server?