• 1 Post
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle


  • Expecting every different platform to all move in lockstep is not feasible so a situation where some support downvotes but some do not is going to have to be part of the process. Even if it was just kbin to kbin initially, that’d still be an improvement.

    Yea, that is what i was thinking. I myself am working on some ActivityPub stuff and while compat is important to me, i also plan on potentially exposing new features in this manner. If other software wants to federate with it, cool, if not, whatevs. It’s data propagation, as with everything in ActivityPub it’s optional that consumers use it as desired.







  • I’m (as a dev experimenting with the fedi) more interested in the features each platform adds to the fedi and ensuring we have consistency. Which is probably included in what you said, i’m just being explicit.

    Ie regardless of if it’s an upvote or a star, hypothetically it should have a similar effect in all platforms that federate with that value. If it modulates score in an algorithm, it should “mean” the same thing to the fediverse so that it has similar outcomes in all platforms. A silly but extreme example of this failing would be one site upvotes and downvotes meaning opposite things on two implementations - it would be chaos hah.

    I hope (but don’t yet know until my implementation is further along) that Like and Boost are functionally different. I also hope no ones implementation is conflating them.

    Either way interesting times and i’m excited to see where we take it :)




  • I’m on mastodon.art and donate $1/m, same story. It’s only a handful of people that donate (hundreds, but still - much smaller than the thousands of users) and we cover the bill.

    Though, this is also why i’m experimenting with custom Fediverse instance software that prioritizes low cost operation. I think Fedi would be better off if it wasn’t a huge lift to figure out hosting. There’s enough challenges in hosting instances, it would be nice to reduce as many as possible.


  • So you’re running a local DB and backing up the external drive? Neat. What about static storage? Images/videos/etc? How are you handling backup?

    I’m interested in this space because i’m writing an experimental ActivityPub client and one of my goals is to make it “as cheap as possible” to run a micro-instance. I plan on exploiting a single directory, sqlite and file storage, that users can just rsync or backup however they wish. Cheap is tough hah.





  • Seems kinda wonky. I’m working on writing my own flavor of an ActivityPub client. Is there somewhere you know of that this is being discussed, developed, etc? Iirc ActivityPub itself doesn’t define this, right? I figure what we’re talking about here is just the data model some apps have created within the ActivityPub spec - and by keeping it consistent apps can federate with each other. I’m curious on advancement of that model to introduce new concepts and features but retain some compatibility.