Notices where this attachment appears
-
Embed this notice
@feld @mint a thousand cuts with very few additions that weren't added/invalidated by you later anyway, nothing upstream is/was interested in when brought up publicly/directly
would need to git clone and diff it out like the last few times i've done this when develop picks up pace again or a new feature i want releases
not sure people would be interested in nostr/outbox/relay scraping for instance
maybe software/similar mrf policies if they were cleaned up a bit?
https://256.lt/mrf/software_policy.ex this one still has a 8 month old bug/issue https://git.pleroma.social/pleroma/pleroma/-/issues/3211
https://256.lt/mrf/similar_policy.ex
-
Embed this notice
@kaia https://256.lt/mrf/similar_policy.ex
># needs build_cachex("spam", limit: 1024) in lib/pleroma/application.ex
># and {:ex_lsh, version: "~> 0.4"} in mix.exs
then
>sudo -Hu pleroma MIX_ENV=prod mix deps.get
>sudo -Hu pleroma MIX_ENV=prod mix ecto.migrate
>restart pleroma/akkoma
are you familiar with editing the source? I ask because i don't see you programming posting much