Sam_uk

joined 1 year ago
sorted by: new top controversial old
NSFW content in the sidebar random posts in c/[email protected]
[–] [email protected] 1 points 1 year ago

@mystphyre AFAIK this is a known issue that the developers have been looking at in the last few days. Hope to have a fix soon

Mastodon Usage Soaring as Twitter Rebranding Leads to User Exodus: CEO Eugen Rochko in c/[email protected]
[–] [email protected] 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

[email protected]

Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? in c/[email protected]
Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? in c/[email protected]
[–] [email protected] 1 points 1 year ago (1 children)

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

@JonEFive

Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? in c/[email protected]
[–] [email protected] 2 points 1 year ago (2 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

Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? in c/[email protected]
[–] [email protected] 2 points 1 year ago (4 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.

Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? in c/[email protected]
[–] [email protected] 1 points 1 year ago (6 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.

1
Who should 'own' magazines? Federated infrastructure but user sovereignty: a “third way” between federated and P2P networks? (kbin.social)
 

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

1
kbin.world (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?

Any Nostr ppl here? in c/[email protected]
[–] [email protected] 1 points 1 year ago (1 children)

Reminds me of this essay https://nexus.blacksky.network/zine/00000001/confederal-protocols I think Nostr get's much of that right.

@JoeClu

Any Nostr ppl here? in c/[email protected]
[–] [email protected] 2 points 1 year ago (2 children)

@JoeClu I think the protocol gets a lot right. It's just a shame all the users are alt-right.

1
I needed a world-news aggregator to help me get off that other site so I made one (kbin.social)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
0 comments fedilink
 

You may be able sign up directly on !worldnews

You could subscribe the main magazine on
Kbin.social or Lemmy.world

It's fed by a bot, but human submissions welcome too. If a human makes a post the bot stops posting for one hour.

Comments and upvotes will improve it.

0
Anxiety and anger over Fukushima nuclear waste plan - BBC News (www.bbc.co.uk)
 

Japan wants to release Fukushima's waste water into the ocean - and a lot of people are not happy.

2
Kbin.social passes 50K users (fedidb.org)
 

Two weeks after 30K users we reach 50K
https://kbin.social/m/kbinMeta/t/35479/Kbin-social-passes-30k-Monthly-Active-Users

2
Kbin.social passes 30k Monthly Active Users (kbin.social)
 

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