Might be true, honestly. I'm on NixOS using the proprietary drivers for my 3080 and 4090. No issues, took one line of configuration. I do have to stay on X11 unfortunately until Wayland supports the real drivers at least (though i hear that's being worked on, maybe already working?).

For all of NixOS' pain, it really does make some things awesome and simple.

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.

Is ActivityPub not open to arbitrary extensions? I thought it was a very loose spec and the only concrete spec is an agreement between instance types. But i've not looked at the protocol closely yet, despite developing around it hah.

Frankly i'd prefer all of it to be private, but there's merit to both sides.

re:drama-causing, i'm also removing downvotes from my instance in dev for the same reason. I do think some version of muting has value, though - but kinda feels like it should be a tool earned, similar to HackerNews (they have downvotes, but only after a certain amount of earned "karma").

Yup. I'm trying to design (trying! lol) my own little slice of Fedi with this same problem in mind. Social networks exploited some natural tendencies towards toxicity for engagement. We need (imo) some people to explore ways to mitigate that.

What's the difference to users of the two platforms, in your eyes? I'm not familiar with the workflows of either Instagram nor DA

I really like HackerNew's approach to this. There is a downvote button, but only older, higher reputation accounts get it. Tildes has something similar (ish), in the sense that accounts with reputation get different features.

It's something i want to experiment with some Fediverse software too. I think features like these can help shape community.

Good link. It'll be interesting to see where it goes. I think this really comes down to a question of "Does the Fediverse even have to capability of federating user actions without indicating what user did the action?"

Plus, if you can muster up some solution, is that solution then easily falsifiable? Ie could a server send thousands of automated fake downvotes that don't actually tie to a specific handle? How would a receiving server know that some anonymous vote is a real vote? etc

Challenging problems.

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 :)

That brings into question what downvotes are, then hah.

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.