Notices by silverpill (silverpill@mitra.social), page 26

@tadano

>db problem

you mean the media cache size issue that we discussed before?

@pernia @yonle @p yeah, the more the merrier

>But realizing how monolithic it was is really not a worth of time.

I think it can be broken into components. Very few people tried that, so most implementations are monolithic.

My own work is focused on decoupling identity, storage and transport. See FEP-ae97 for details (I'm also working on a Rust library for AP implementers)

https://codeberg.org/bovine/bovine is another attempt (the approach is very different from mine)

@julian @js This wiki page contains some additional information: https://www.w3.org/wiki/ActivityPub/Primer/Streams

It says developers should use extension properties instead, and I agree with that.

@mikedev Some developers need labels that are independent entities. Actors will use these (pre-defined) labels to categorize objects, including objects created by other actors.

Hashtags are usually ephemeral and are added by authors themselves.

For example Lemmy is working on a tag system but they don't want to use hashtags https://github.com/LemmyNet/rfcs/blob/main/0004-post-tags.md

@privacyguides Cool. Good to see you're working together with @sgp and co

@Tadano @tadano You can do that too, but it is not necessary to run it manually.

This command runs when you start mitra and then every hour. Did it not run?

@tadano Mitra will remove unneeded files automatically

@tadano Yes, probably. If that is too much you can adjust data retention settings: https://codeberg.org/silverpill/mitra/src/commit/4befde1b4b41d598f260eb04620fd2c961354263/config.example.yaml#L67-L71

On my instance I keep remote posts only for 5 days:

@mikedev @thisismissem I think content labels should be different from hashtags on the protocol level, but in UI they can be unified.

@thisismissem @santisbon Lemmy is implementing "post tags" which are similar to content labels: https://github.com/LemmyNet/rfcs/blob/main/0004-post-tags.md. Perhaps you could collaborate? They seem to be interested in such FEP too: https://github.com/LemmyNet/rfcs/pull/4#discussion_r1679203468

cc @julian

@frogzone Added this feature in 2.26.0

cc @nimda

@julian For FEP-ef61 you will likely need to refactor much more than ID generation. This can be done (@mikedev and I did it), and might even be worth the effort, because this FEP not only solves the problem you've described, but also takes ActivityPub to the whole new level.

@julian FEP-ef61 makes everything domain-independent, including posts.

as:Move will only move followers, but it can work when source is offline too (FEP-7628 pull mode).

@knt I decided to add the --log-level parameter to mitractl (will be included in 2.26.0 release). The default level is still INFO, but will be changed to WARN in 3.0.0

RUST_LOG is intended to be used during development, I'd like to keep it unofficial / undocumented

@frogzone I think it can be done entirely on the client side.

Have you tried Phanpy? I've heard it has a similar feature

@julian @trwnh It is also implemented in Streams. I think implementation list would be useful: https://codeberg.org/fediverse/fep/pulls/375

(my server can parse fb2a attachments, but it doesn't create them yet)

@pfefferle

>Added: Support for FEP-fb2a

👀

@yuzuki I assume Cloudflare was the only solution they knew and other options were not considered at all. What would you recommend?

@yuzuki They enabled Cloudflare after a DDoS attack where requests were coming from Tor exit nodes.

@steve @smallcircles @zicklag Yet people somehow created hundreds of ActivityPub applications. If anything, it is over-specified. Inbox, outbox and ActivityStreams are the foundation, everything else should be in FEPs describing specific use cases