When it's running in server mode it provides a similar UI too when it's a client, except now you can browse the snapshots/policies of each client that uses it.
Not quite full management but yeah, good for home use.
VerifiablyMrWonka
joined 2 years ago
My vote goes to Kopia.
In order to catch up with a massive queue backlog a temporary hold on delivery to domains that are being problematic has been setup. Those other domains aren’t responding to kbin.social’s requests properly and so our own queues are getting backed up.
It’ll all be back to normal soon. Once the queues are sensible we can reenable domains as they start becoming responsive to us.
A good PWA is almost indistinguishable from a native app.
On Android, where they've bothered to implement the apis for it you've got access to all the same stuff (camera, location, Bluetooth etc)
Apple has less, which is ironic because originally the iOS platform was only going to be PWAs. I guess discovering they could take a 30% cut of all money taken changed their mind.
I recommend you take a look at https://elk.zone as an example of an excellent PWA (be sure to actually install it and use it that way)
Boosted and upvoted because I think you're right. 😀
This isn't the case though? Upvotes (aka favourites everywhere else) are what affect the "algorithm" the functionality thats broken is Karma tracking.
Of course a bad actor can set up their own instance and just create thousands of fake bot accounts and do the same.
A competent admin would then just defederate from them. Easy. But now throw in that all kbin instances look like bot fests and what do you do? Maybe what lemmy.ml have done and just block kbin useragents at the firewall.
Having an aggregate account that just sends totals could work, but then vote brigading just became even easier. What's that aggregate bot? Did you just send a vote ratio of 300:1.9k for this comment? Lovely.
It's a very hard problem to solve and I'm not sure it's doable. The only thing keeping ActivityPub together is the fact that it's so transparent and bad actors are easily spotted and blocked. As soon as you muddy the waters the primary benefactor is the bad person.
So what happens with 300 people downvote a post and 500 upvote it? For that to work you'd need an 'account' per post/vote/user combination. Now your instance has 1000's of bot accounts that are now indistinguishable from bad vote manipulation.
This is bug. It's fixed in dev. Shortly before the great migration started a change was made to bring kbin in line with lemmy but the bit that calculated the "karma" was missed and so it still uses boosts.
Not that I agree with the concept of karma.
Oh, no no. It was that I blocked one person and there were only 6 other comments left (all fine) :D
Blocking a person seems to remove any comment tree they're a branch in (i.e. their posts and all responses to those posts)
Ha, I blocked the worst offender in the comments here, refreshed the page and now there are like... 6.
Not true.
Both Lemmy and KBin map the same activitypub activities to the same upvote and downvote actions.