@warc

I have written my opinions on content warnings as a twenty page essay https://shelraphen.com/on-content-warnings/

@vision more info, including info for non-akkoma instance ops, over here

@KaydeArcane I get that reaction from a lot of people lmao, even people that do actually use blender daily

@KaydeArcane I personally tend to just use blender’s video editor, it tends to be Good Enough for simple tasks like that and I already have it downloaded since I use blender anyways

@nora @vision rn it’s pretty much just “try every akkoma in the spreadsheet, it should work for most of them”

@mae it should keep working just fine, it uses the relay account to follow stuff, and I told ppl to whitelist it

update on the whole relay situation: I got an MRF policy (setup instructions for akkoma ops inside) that should limit/eliminate abuse of relay accounts to approximate federated timelines. if you, as an instance op, were using an account to follow relays, you will have to make a new account named relay_follower and use that instead; also forbid using relay as a username (if possible, otherwise you can probably create an account with that name to reserve it) if on a gotosocial instance

if you’re on an akkoma instance or otherwise not following relays with an account, make sure that the relay_follower username is reserved or otherwise unavailable to users; akkoma lets you define reserved nicknames in the instance settings

@vision update: should be sorted, I got an mrf policy going, update your akkomas from the gitlab or just drop this file in the correct location and then add Pleroma.Web.ActivityPub.MRF.FollowWhitelistPolicy as a policy; I recommend setting the values as suggested (["relay"], ["relay", "relay_follower"])

if an admin is following an instance’s relay account, they’ll have to use relay_follower as the local account name (or relay if available, I guess, but I don’t recommend doing that because possible future expansion)

@froggebip @testadmin ight, things are Working

can someone follow @testadmin rq? I’m testing something

@kuchaibee I personally like husky and fedilab on android, husky is mostly for pleroma/akkoma, but it might work for this, and fedilab is for several instance types

@froggebip @viv yea, that’s another reason why I told ppl to use a separate account: most ppl don’t want their home timeline blasted with a firehose feed

@viv they could, yeah, but rn we don’t have a better solution tbh; that’s also why I told ppl to make a separate account for this

@Sacchihikaru @kda also found a partial solution for GTS

another PSA, this time for GTS ops: you can actually subscribe to the recently enabled relays on the Akkoma instances, and while it doesn’t directly help with outgoing federation, it will definitely help with incoming federation. here’s how:

• create a new user on the instance just for the relay subscriptions (you technically could do it with your main user, but that’d basically bring a firehose feed to your home feed)
• follow relay@instance.tld on the Akkoma instances which have the relay enabled
• you’re done! the relay accounts you followed should be boosting every public post on the target instances, which should federate said posts to your own instance

more #relaytesting

#relaytesting 2: more testing

@ebu I’m pretty sure you need to change the content type mode… somewhere, idk where it is in gts frontends, I use akkoma

@vision @froggebip (I love the fact that it’s a thing)