If an actor provides an outbox URL, but not an inbox URL, it means that it cannot receive Follow activities and it can not push content to the followers. In such cases, the follower's server should switch to periodic polling like RSS.
This will enable statically-built blogs ( #jekyll#hugo etc) to appear in Mastodon network.
So, my curiosity to try all the things that connect to the #fediverse... Currently running #Akkoma and testing it out (not followed anyone to avoid confusion and annoying people. I do follow fellow Akkoma admins @MisterArix and @eviloatmeal). Also running #GoToSocial on a different box, but that one maybe torn down soon. It's great alpha software, I'm super curious to see how it is when they get more features added.
Finally worked out how to get #GotoSocial federating to #Honk with a couple of quick-fix-kludges. I know how to (mostly) properly fix the second (Honk rejecting GtS statuses) but the first (GtS rejecting Honk follows) is a bit trickier.
In the process of debugging that, I had to debug #Toot and fix that to allow it to post statuses to both GtS and#Akkoma. FFHS.
Hopefully the ActivityPub spec will get firmed up now it’s in active use and we can get rid of these stupid nonsense incompatibilities before I go completely insane.
When someone asks about options for servers or clients I have a habit of tagging recommendations, and when there is not an account for the thing, I have to stop and search for a dev or find a website address to link to etc.
@liaizon I don't know who operates friendica.me, so libranet.de would be my preferred choice.
@alfred would you like to do the honors of creating the first official regular Friendica account for the project on your node as described in this post: social.wake.st/ ?
Hi. I see your point, but I think snac is too niche to need a different account than mine, which I use only for snac talking and announces. If usage out there grows, I'll probably create a specific one.
I enjoy much of the built-in security practices #yunohost offers, but I'm willing to evaluate alternatives that offer some server hardening baked in and that simplify deployment.
Anyone who knows #react or some other front end type stuff want to help me with a small project? Looking to created a frontend for #gotosocial (#golang powered #mastodon like service). Just something super basic.
Just curious, according to the #gotosocial page while it does not provide it's own web client, one can use any mastodon client with it: https://joinmastodon.org/apps
@paksydavid after posting this and thinking about it more I might not need a client yet. What I am wanting to do is to build something that uses GPT3 to pull interesting words out of a post I make and add them automatically as hashtags. I am thinking I can build that in gotosocial itself, and not have it happen on the client. I may then experiment with a client that analyzes and suggests hashtags before posting, and displays hashtags separately from a post (both incoming and outgoing).
To understand them better, I will not stop with just reading and documenting, but might write a app (server, client, bot) to solidify my understanding.
There are different approaches to developing apps for #fediverse
• a typical mastodon app implements both front-end and back-end
• #gotosocial type of apps implement only backend api (along with cli all in #Golang )
• apps like @sengi_app are only at the front-end
• @brianmmdev is implementing a fediverse app via #serverless model
As mastodon picks up steam, we will see different types of apps
Thus far the easiest #activitypub service I’ve installed has been #gotosocial, followed by #mastodon, and I wasn’t actually able to get #pleroma (or any forks) to build properly. I’m really rooting for the @gotosocial team and am looking forward to seeing how it progresses.
I think the issue with #pleroma was just not really understanding the resources needed to build vs run, so it might be worth revisiting that or #akkoma maybe, to experiment.
The weirdness of course being that you can’t really swap out backends easily since the federation basically locks other instances to this particular instance running -this particular software- which still confounds me.