What I find strange in #ActivityPub and #Fediverse that there is no way to put a note to follow request. Like "I want more posts in language_name in my feed and I liked the cat videos you repost".
It gives cases when someone concerned that they did not understood why someone follows them.
@Abyssnauta Graphics are FREAKING AMAZING! Game play is fun so far, but I'm only just an hour or so into the game. Haven't really done much beyond the opening stuff.
@qbi Für mich ist das Besondere, dass ich Hashtags folgen kann - und das würde ich ihnen auch empfehlen. Bestes Werkzeug für eine bunte Timeline voller Entdeckungen auch kleiner Accounts!
@J12t Yes, that's certainly one use-case for the outbox... to "catch up" on things you missed, on a per-user basis.
But as far as I am concerned they're separate APIs that pull from a common data source.
For example, reading the ActivityPub spec, one could draw the conclusion that the outbox is an ordered list of activities, likely read as-is from the database.. but that's not strictly defined, so it's possible to dynamically create outbox items on-demand based on user history stored elsewhere.
That would mean less duplication of content (and the syncing that is required), fewer bugs, etc... but the cost is the collection then has to be dynamically constructed.
@julian It's mostly append-only, easy to cache ...
For FediTest, we have come to the conclusion that simple pass/fail isn't going to cut it. We need a more gradual rating, and the current state is 1) fail -- against the spec and likely go cause interop problems 2) soft fail -- against the spec but probably harmless from an interop perspective 3) degrade -- e.g. everything turns into a Note and 4) pass. Not sure this is an exhaustive list ... your empty outbox would get a pass, I think.
I still don't understand how fedi instances work between each other, how can instances even block each other?? How can you find an instance that doesn't block others? How hard is it to host your own? So many questions!
Wie lustig. Bereits seit dem 20.04.2016 werden alle meine Beiträge aus dem #Fediverse zusätzlich auf einem #WordPress gespiegelt. Den ursprünglichen #Friendica Server gibt es heute nicht mehr. Der war irgendwann zu klein und ist auf eine größere Maschine umgezogen.
Die Idee dazu war ganz einfach: Sollte etwas ganz, ganz schreckliches mit dem Server passieren, dann habe ich immer noch eine 1:1 Kopie meiner öffentlichen Beiträge, die ich hier erstellt habe 😎
Randnotiz: Das Blog ist damit älter als #Mastodon 🤪.
Molly White is one of the most thoughtful writers and thinkers on the web today. In addition to being a high functioning crypto critic, @molly0xfff is a believer and practitioner in crafting the next era of the web.
Molly believes that human connections are an inextricable part of the web and sees a bright future ahead as those connections move from walled gardens to the open web.
Check out this fantastic conversation with her on the latest episode of #DotSocial on our #PeerTube instance or wherever you get your #podcasts.
Great to hear @molly0xfff's thoughts on not just the fediverse but lots of #dweb and #indieweb technology.
The points about UX are so right, been thinking about this a lot.
Portability, attribution and ownership are also key
Thank you @mike and the @Flipboard team for producing these #dotsocial podcasts
Good morning and happy FRIDAY #Fediverse. We’ve made through another week.
Let’s take a moment for our #KoffeeWithKyle chat and see what we all have planned for today.
I’m currently at my neurologist appt. After that I have the usual work thing. Already have a couple of support issues from yesterday from when I was out. The later today just some school work and chillin. Not sure about the weekend yet.
@cliffwade No updated other than what I posted from yesterday. Just waiting on Hyundai here to diagnose the issue to Hyundai corp can officially start the process to get new engine.
@HailsandAles Trying out "Crystal" from Passage...they're definitely no longer a doom band at all (though this was my first listening to them.) Light, whispy, pianos and orchestrations, something you'd probably hear in a hot yoga studio.
World heavyweight champions Tyson Fury 34-0-1 (24 KOs) and Oleksandr Usyk (21-0, 14 KOs) meet to unify the division in a huge blockbuster fight at the Kingdom Arena in Riyadh, Saudi Arabia on Saturday, May 18. ....
On Saturday night, boxing will crown an undisputed heavyweight champion of the world for the first time in 25 years when Tyson Fury takes on Oleksandr Usyk. . (Copy & Paste This Website on you browser to watch LIVE. Thankyou) ....
On Saturday night, boxing will crown an undisputed heavyweight champion of the world for the first time in 25 years when Tyson Fury takes on Oleksandr Usyk. . (Copy & Paste This Website on you browser to watch LIVE. Thankyou) ....
On Saturday night, boxing will crown an undisputed heavyweight champion of the world for the first time in 25 years when Tyson Fury takes on Oleksandr Usyk. . (Copy & Paste This Website on you browser to watch LIVE. Thankyou) .https://www.moosejawtoday.com/classifieds/community-events-and-announcements/community-events/1874823...
Part of my frustration with #ActivityPub and one of the things I find baffling giving everything else in it: the lack of tools for backpressure.
Backpressure is fundamental in building reliable distributed systems (c.f., Notes on Distributed Systems for Young Bloods). From a C2S perspective I get why it wouldn't need to be specified, but from a S2S federated protocol perspective its absence is frustrating.
All that it says is to take care not to overwhelm others and a bit on rate limits
But I also want state convergence. No matter what, different hosts are going to wind up with different views of the state of the graph. Why are there no mechanisms to detect that and enable convergence?
I want a mechanism to determine if two party's view of a collection are equivalent. I want to be able to query if an object is contained in a collection without enumerating the whole collection. I want a mechanism to request re-delivery or maybe failed delivery notifications.
For what it's worth, these are all goals that would align well with the interests of a broad set of implementors. I make a little noise now and again about the SWICG forum task force, but directly addressing some of these concerns would definitely be on our radar.
Current focus is on aligning on a common object type for higher level collections (the context), but I'm thinking that Collection (ordered, ideally) would be the best fit and also allow for future use cases like you mentioned earlier.
You have the ideas, we might be able to supply the coordination...
