@ernest I see you posting more and more about community management and server/service maintenance than coding on the project.

How do you deal with doing both: a maintainer for a project and a community manager ?

I was trying to push people interested in #BrutaLinks in starting their own instances instead of using mine, and seeing how nobody took me up on that, it feels like it's the losing strategy. :D

I keep being on a roll today. I discovered the mystery of why #BrutaLinks doesn't show follows coming from Mastodon.

It actually does, but because they don't have a published date they are ordered at the end of the inbox, so I had to go all the way to the end of the listing to find them. Sigh...

Another one to put on top of the pile of #mastoquirks

One of the small things I managed to do while sick this week was to add support for <link rel=alternate type="application/activity+json"> for all the pages where this makes sense.

So now the instance and the individual users are directly discoverable on Mastodon instances by entering the URL in the search box. (Accepting the follows is not functional at the moment... oops)

Ex instance: https://brutalinks.tech/

Ex user: https://brutalinks.tech/~marius

#BrutaLinks #GoActivityPub #FedBOX #ActivityPub

One of the small things I managed to do while sick this week was to add support for <link rel=alternate type="application/activity+json"> for all the pages where this makes sense.

So now the instance and the individual users are directly discoverable on Mastodon instances by entering the URL in the search box. (Accepting the follows is not functional at the moment... oops)

Ex instance: https://brutalinks.tech/

Ex user: https://brutalinks.tech/~marius

#BrutaLinks #GoActivityPub #FedBOX

@weirdwriter could you look at #brutalinks also? I always wondered if I got reply threading right for screen readrs but never managed to properly test. Example thread: https://brutalinks.tech/~ild/e469b98e-4b48-48a8-86e5-6c61ebd9aff8

@mainsac none that you can login with Mastodon but you can subscribe from it.

Current contender are #Lemmy and #Kbin and #brutalinks

For people invested in the migration from #reddit. Here's some details about #BrutaLinks one of the projects I'm working on, which is a reddit-like discussion platform, built on top of #ActivityPub.

It didn't benefit form the attention and funding that lemmy got, so probably it's overall less polished and performant, but some love from the community would do it good.

https://brutalinks.tech/~ild/e469b98e-4b48-48a8-86e5-6c61ebd9aff8

The daily grind of fixing bugs and small iterative work took me by surprise today, when I finally had a look at how #BrutaLinks and #FedBOX integrate with Mastodon, (which used to be "not very well") and I finally have a working webfinger resolver that covers actors for both projects.

So if you're searching for the accounts on https://brutalinks.tech, you can actually find them now.

There are still bugs, but, I'm happy for small blessings. :)

@Tim_Eagon @kreig another option, is one of the projects I work on, called #BrutaLinks.

For people that haven't been following me:

#FedBOX is a generic ActivityPub service with client to server support

#BrutaLinks is a link aggregator and discussion platform similar to old Reddit and Lobsters

I haven't talked about #BrutaLinks and #FedBOX in quite a while, as I was focusing on a different #ActivityPub project.

Today I fixed some long-standing bugs thanks to some interest from a long time user that stumbled upon some of the problems. 🙇

@erlend don't forget #brutalinks: https://brutalinks.tech

@christianselig @ivory @LemmyDev @ernest

@maegul you've described to the letter my goals in developing #brutalinks: https://github.com/mariusor/go-littr#about

@helge @silverpill

@J12t I have the server side (on #FedBOX) and client side on the link aggregator that uses it as a backend, called #brutalinks

But sadly I didn't interop with other clients/servers for either of them.

The main challenges that I can think of:

1/ when a user wants to login using a new client to the server it should be dynamically created on the server.
2/ discoverability of OAuth2 endpoints for each actor - this is handled somewhat by the AP spec.

> At its core I suspect some form of Server-Server handshake will be required.

@hrefna this can be as easy as opt-in follows requests between the servers, which are requested/accepted from the administrative panels of the respective instances.

I am using this mechanism for federating between #brutalinks instances.

@hrefna this is the way I plan to implement federation in my projects. The discussion platform #brutalinks requires explicit following other instances by admins in order for their posts to get pulled into the local timeline.

I achieved this by having every instance have a corresponding activitypub actor, and the "federated" part is done by explicitly follow/accept-ing from other instance actors.

> We need a proper ActivityPub Server first

@helge funny you should say that. I'm working on #fedbox - a generic ActivityPub server written in Go: https://github.com/go-ap/fedbox

It's not ready for general usage yet, though it serves (hah) as a backend for a couple of other projects: #brutalinks - a link aggregator and discussion platform, and some bots that use it's client to server capabilities.

Started back some work on #Brutalinks and #FedBOX. Fixed some bugs, added some minor functionality. So far so good.

Began a big chunk of work for the Go-ActivityPub library by stripping the custom storage backends from #FedBOX to their own separate packages that can be used independently.

This will allow me to reach a compromise with regards to being compatible with Mastodon: I previously resisted the idea of having a local webfinger route on #FedBOX, but now I'll be able to have a separate binary that only does that and will be available from both it and #brutalinks by calling into the same storage logic.

@lil5 this is #brutalinks a go server side application (there's very little JS there) modeled after old reddit and lobste.rs.

It uses the ActivityPub client to server API (with some specific extensions) to communicate with another go application, called #fedbox - which is a generic #ActivityPub server.

If you want to see it in action check https://littr.me

Caveat, they are not Mastodon compatible (yet).