Sam_uk

joined 1 year ago
[–] Sam_uk@kbin.social 3 points 1 year ago

@Chozo I wonder if this bodes well for Kbin/Lemmy? Arguably their model is more about content than social relationships.

 
[–] Sam_uk@kbin.social 1 points 1 year ago (1 children)

I'm curious why this recent trend isn't visible in Google Trends? I watched the November exodus unfold in real time there. This time not a glimmer of activity

BlackRose@slrpnk.net

[–] Sam_uk@kbin.social 1 points 1 year ago

@poVoq yes this sounds sensible. I think the key is the user themselves having more control over their identity.

[–] Sam_uk@kbin.social 1 points 1 year ago
[–] Sam_uk@kbin.social 2 points 1 year ago (1 children)

@JonEFive I think the identity bit is the hard part, as you say most content will be federated/ cached in several locations for retrieval

[–] Sam_uk@kbin.social 1 points 1 year ago (4 children)

WebauthN maybe? Pretty niche right now, but the threadiverse is quite a techy crowd..

@JonEFive

[–] Sam_uk@kbin.social 2 points 1 year ago (5 children)

@JonEFive I've been wondering about separating the ID/auth from the app. Someone recently got Keycloak working and that has some possibilities for federation. Not sure if that really helps though. You still have to trust the keycloak admins

[–] Sam_uk@kbin.social 2 points 1 year ago (7 children)

@JonEFive I do run an instance that's just for me https://fledd.it (configured as a news aggregator) it was easy on elest.io. $10/ month is too much for most people though. I don't think this is the route to mass adoption.

[–] Sam_uk@kbin.social 1 points 1 year ago

@Ori I'm making the US regional, I forgot to add in a default for areas outside of the covered regions. It should work again now.

[–] Sam_uk@kbin.social 2 points 1 year ago (9 children)

@JonEFive Multi-magazines are certainly desirable and would to some extent mitigate the data loss caused by an individual server going dark.

I guess the larger issue is if your 'home' instance is the one that goes dark, taking your personal account with it. Maybe it's in fact user account portability that's most important to work on. Assuming that multi-magazines happen fairly soon.

 

At the moment the server owner effectively 'owns' magazines & communities. Is that the right balance of power? What happens when servers go offline, or server admins go rogue?

In a world where both users and magazines had public and private keys and magazine moderators had the tools to do off-site backups.

Could the magazine moderator then do an unassisted migration to a new place?

They revoke the key that gives the original server the right to host the magazine. They use the key to re-create it on a new server.

Somehow notify all the members the magazine of the new location. The users use their public keys to reclaim their identities and content.

Would that give mods too much power?

It all gets complicated fairly quickly! I think the Bluesky AT protocol is somewhat close to this model for user content, but doesn't really extend to 'community' scale content.

It falls short of a full confederal protocol

11
kbin.world (kbin.social)
submitted 1 year ago* (last edited 1 year ago) by Sam_uk@kbin.social to c/kbinMeta@kbin.social
 

I stuck a service on https://kbin.world that redirects you based on a IP lookup for your country. In descending order it tries to;

  • If there is a kbin instance for your country it redirects you there (Just Poland for now!)

  • If you have a feddit instance for your country it redirects you to the most appropriate magazine on that instance, within kbin.social eg Germany

  • If you have a large national community on another Lemmy instance it redirects you there, again within kbin.social (eg Brasil)

For the ones I haven't got around to it redirects you to kbin.social homepage

It could be broken down to regions too. As more national or regional kbin instances emerge I'll replace the existing feddit/other sites.

I did a bit of testing with Pingdom and it seems to work

In the process I noticed that New Zealand and Japan feddit instances won't load for some reason. Any idea why?

 

However, when reddit crapped the bed, by comparison, the threadiverse basically didn’t have an established culture. There was a handful of lemmy instances (we were one of them), but the only one of notable size was lemmy.ml. kbin didn’t even exist in any meaningful way until a couple of months before reddit died.

So, when reddit died, there was no established culture. Instead, people brought reddit culture with them, and reddit culture, because of lax admins, was much more tolerant of hate speech than microfedi. And so, people who are “reddit people” more than “fediverse people” set up lemmy and kbin instances, and brought those reddit norms with them.

So then, you get instances like blahaj and beehaw that are threadiverse instances, but have the “old school” microfedi approach to bigotry. We smash it down hard at the first hint of seeing it, but most of the instances we federate with don’t attack it so aggressively.

 

I didn't write it, but it seems good

 

I've been running a Kbin server on a service called elest.io for around a week.

Had a few teething troubles configuring caching, but that should work out of the box now.

If you can point & click on stuff in a semi-sensible manner then you could run your own instance for yourself, a specific community/sub.

I've configured mine as a news aggregator: https://fledd.it

You could subscribe to the main magazine here !worldnews

Elest.io do the install, configuration, encryption, backups, software updates, os upgrades, live monitoring, alerts, live migrations without downtime.

I'm not connected with them in any way other than as a customer.

 

Can you make a Kbin YouTube video?

It seems that lots of people will be searching, people like watching videos.

#kbinMeta

 

This project https://github.com/everything-gripe seems an interesting way to re-use the infinity Reddit app

Could anyone do the compatibility layer between the Kbin API and the everything API? https://github.com/orgs/everything-gripe/discussions/1

 

So this is a half formed idea that might be horrible, I thought I'd throw it out there for critique.

  • We have a problem on Kbin.social and probably other instances of under staffed moderation & admin teams.
  • Some large magazines have a single moderator
  • This will soon lead to *bad-shit appearing here
  • We will likely get de-federated at some point

A random selection of peers is good enough for juries. So how about we apply it here?

Every ~100th new user is made a site wide Admin (cannot delete only unpublish content, it remains visible in the backend to other mods)

Every ~100th new Magazine subscriber is similarly made a mod of that space.

A few would go powertripping, many would be inactive, but I think it might build the mod/admin team in a reasonable way.

We have to build the processes for powertripping/inactive admins anyway, so in a sense it's not extra work.

You'd build in some randomness, so the system was harder to game, it wouldn't literally be the 100th person. It might be the 80th, or 110th, but averaging out at ~100

 

It's still tiny numbers in the scheme of things, but also quite a big number for a site that had ~30 users this time last month.

Kbin stats https://kbin.fediverse.observer/dailystats

Lemmy + Kbin https://fedidb.org/current-events/threadiverse

Raw https://kbin.social/nodeinfo/2.0

view more: next ›