@mistermonster you'll be glad to know that I have made the first steps towards federation between #brutalinks / #littrme instances working: following another instance.

Well, it was a sad weekend for me. #littrme was on hacker news and I had no idea until just now.

The increased traffic crashed the website and I was oblivious as to why. Sigh. It wasn't even the increased load that was the problem but my sloppy deployment of untested concurrent code. :(

A short update on what's been happening with #brutalinks (nee #littrme), the federated link aggregator, and #fedbox, the generic #activitypub service.

Spoliers: it was mostly refactoring around having to load data from multiple services.

https://littr.me/~marius/74aa79e5-a062-4062-a768-079b2b7c143d

A long time incoming, the first update about #federation on #fedbox the generic #activitypub service and #littrme the federated link aggregator.

Also it didn't occur to me until now that these 4 months of hiatus regarding updates might or might not be related to me making my way through "The Wandering Inn" books 1-7. Sigh...

https://littr.me/~marius/ef38981b-f682-45eb-b94a-916085c00ec9

I haven't posted any updates in a while about #fedbox, the generic #activitypub service, or #littrme the minimalist federated link aggregator.

Today I'm happy to report that federation integration tests are running well for a restricted number of activity types.

Hopefully later this month, I'll have a more comprehensive update detailing what happened in the past couple of months.

I've been mostly quiet regarding #fedbox and #littrme development lately, and that was because I was focusing on a TUI interface for administering a FedBOX instance.

I'm making progress slower than I wanted to but it's still progress. :)

Past month has been mostly dedicated to storage format improvements in the #fedbox (the generic #ActivityPub service). I've been making progress to storing activitypub objects in a sqlite database, but there are still things to be done about the custom #c2s querying fedbox uses.

Some other small improvements to #littrme's moderation capabilities and local caching.

For details see the complete post:
https://littr.me/~marius/b8f5f92a-e795-48ac-99dd-57b09d803fdd

Aggregated again some details about what I've been doing in the #go-ap project and it's test applications: #fedbox, the generic #activitypub service, and #littrme, the brutal link aggregator and discussion platform.

Mostly I've been working on creating a sqlite storage for ActivityPub documents. It's not done yet, but the end is in sight.

https://littr.me/~marius/3b17f252-0cd8-4342-a28c-d73ab762b927

Un peu dans l'esprit de Lemmy, HackerNews, Lobsters,
il y a Littr me.
https://littr.me/
#Activitypub #LittrMe

Some details about what's been happening over the holidays in #fedbox, the generic #activitypub service, and #littrme, the link aggregator and discussion platform.

https://littr.me/~marius/0ffccc31-5415-4415-a0f7-b06a071a31c6

A new release for #littrme the social link aggregator based on #ActivityPub. This was mostly related to speed improvements, as you can see from the release notes: https://brutalinks.tech/~marius/4d465d95-7e08-4d77-8ead-871d59d91e4b

Some improvements to littr.me's moderation log. Currently only shows moderation requests from users (blocks, reports) with a basic filter based on the type of item you want to see: users, submissions or comments. In the next iteration the log will also display mod actions that are linked to these moderation requests. Also planned there are adding mod requests on domains, tags, and instances.

#littrme #update

Working on #littrme.

Today I added the basis for a moderation log page. This is missing a big chunk in #fedbox, as it doesn't support Flag/Block activities yet. Also I haven't finalized the flow for reporting items in littrme.

I am also doing preliminary work on enabling invitations sending, which will constitute the main method of registration on the instances.

#activitypub #activitypubdev

I haven't posted about #fedbox or #littrme in a while.

This unexpected long vacation that we're all having right now, allowed me to finally finish a big feature, which was keyset activity collection client side loading.

It's a bit of a mouthful, and currently the performance is not very good, but our #activitypub #c2s code can load an actor's inbox/outbox and display it's objects transparently using different logic based on the Activity's type or the Object's type.

Whew!

@xosem @hyperlight@sunbeam.city @prismo there's always #littrme :))

A little bit more serious of an update about #littrme, I'm working on better collection loading for the main tabs. In order to do this, I fell down a rabbit hole of improvements for #fedbox. First of them, which is almost complete, is to use keyset pagination instead of limit-offset one.

Woohoo, someone submitted the first spam post on #littrme. I think this means we have finally hit the main stream. :))

A pet peeve regarding the conformance to the #ActivityPub spec for #go-ap the Go packages, which form the basic of #fedbox the generic activitypub service and #littrme the brutalist link aggregator, was that the NaturalLanguage properties of Objects weren't marshaled under the correct name according to the spec if they contained an actual map of "country-code" - "value", values.

I am in the process of fixing this, though there are some corner cases that I'm not sure how to handle.

Added recipients listing in private messages on #littrme. The addressing mechanism is a bit iffy at the moment, but for a day and a half of work, I think it works pretty well.

#ActivityPub #C2S

Woohooo!!! Private messages on #littrme:

https://littr.me/~marius/eb6e82da-5d30-4c7d-bb8c-c1a527bea29a

#activitypub #c2s