@iMeddlesFor now it's single device, but we're working on multi-device support. Our approach is to handle sync through the relay rather than backups. Each phone would run its own server independently and receive activities from the relay, which could also store lightweight sync data like read positions.@apps

another question is if Webmention's WebAPI allows at least 10kb of POST (so far unspecified amount?), it could fit 2000 unicode characters (or 10000 ASCII) message itself, without requiring the message to be published on 3rd server. playing alternative of #nostr relay. Or Nostr relays one day start working with webmentions. meanwhile nostr relays been moving towards self publishing of web pages via decentralized hosting nostr protocol NIP.

@raphael both servers I built using GoActivityPub have support for Dynamic OAuth2 client creation (RFC7591 and RFC8414) and by using the Client ID Metadata Document draft if you plan to support one and/or the other.

@paul Welcome back!

@aj Someone shared some media with me about "poisoning the algorithm" by not clicking on ragebait for days or weeks until the systems stop supplying it and shift to healthier fare and I just had to laugh, because the description of the goal was a description of the corner of the fediverse that I'm exposed to.People are out there spending days "poisoning the algorithm" just go get what we get on Mastodon on day 1!

@fluffy> what could be done using a more IndieWeb approach. atom or mf2 for publishing, WebSub+WebMention for push, bearer tokens exchanged via TicketAuth for private accessKnock yourself out. Let a thousand flowers bloom! ; )

@lexinovaWe can't change how Mastodon presents those settings, but we had a page explaining how the service works and how to opt out per platform. We'll communicate even more clearly if the service comes back.Worth noting that this opt-in by default setting also allows Google to index fediverse profiles, except they don't check for consent at all. This is a much bigger issue that goes way beyond our project, which actually tries to do things the right way.

@malte@radikal.social <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f631.png?v=3f6bb89c221" title="" /> what!! Hopefully our free ActivityPub plugin native integration will help change some minds Thanks for sharing!

@apps As experienced client devs, I assume you have the infrastructure for OAuth already in place? I'd rather go to your website and authenticate my Mastodon account there than have a hashtag in my bio... the Tootfinder hashtag kinda annoys me every time I see it. That aside, I believe Mastodon is going to introduce some kind of profile signal for willingness to appear in starter packs, might be worth additionally keeping an eye on whatever happens there. https://github.com/mastodon/featured_collections

@breathOfLife@infosec.exchange#Friendica should still support multiple protocols.@dansup@pixelfed.social

@smallcircles @bifurcation I think MIMI is a different application of MLS. I'm sure it's fine as additional reading but the content model and underlying transport are different.

@DerEntspannende @jansenspott ja, das ist Legacy, aber ich wollte das nicht einfach für alle ändern, ohne zu fragen! Aber du hast recht, es sollte einfacher sein auf den Standard zu wechseln, ohne erst die Advanced settings öffnen zu müssen!Wollte es bissle verstecken, dass es nicht jeder einschaltet, hab aber das ausschalten außer Acht gelassen! Fix kommt! Danke fürs Feedback!

@Varpie @box464 @ivan If you look at https://forgefed.org it chose to implement as:Offer in the context of "software development" toplevel domain (or perhaps "code forges" application domain).Here we may say that it is alright to do so, if its use adheres the informatively specified functionality of "offering one object to another" in that general sense.Yet I think I'd model this quite differently, and mapping to ActivityStreams is more a disadvantage than anything else. The spec has to describe the combinatorial logic of what to do when receiving as:Offer and needs a 'smart pre-processor' to determine the use case and bounded context.

@steve i would probably think my outbox was broken or malicious or not doing compliant^1 activitypub.^1: depends on a conformance profile to be meaningfully defined, but "publish what i POSTed" seems to be a reasonable enough expectation in the minimal case...