lucien

joined 1 year ago
[–] [email protected] 1 points 1 year ago (2 children)

Good God. On beehaw I had to block every furry community separately. Talk about annoying.

 

A lawyer almost certainly told execs that this was an illegal attempt to misclassify employees. I think we're getting to a place where if people do things even though a lawyer tells them it's illegal, they are personally liable (jointly with the org itself) for the decision even in the context of a limited liability organization. And if the lawyer is incompetent enough to tell them that it's legal, they need to be disbarred and potentially liable for the damages.

[–] [email protected] 3 points 1 year ago

Very much aware of that.

[–] [email protected] 2 points 1 year ago

That's great lol

[–] [email protected] 16 points 1 year ago

2k people in expensive San Francisco office space. Willing to bet that the % of them dedicated to improving user experience was quite low in comparison to those trying to figure out how to squeeze money out of it.

[–] [email protected] 2 points 1 year ago

It wouldnt really be full P2P: I'd expect moderated communities to act as a funnel which everyone interacts with each other through. I wasn't really considering the hypothetical micro instances to be like a normal server, since even when federated its unlikely that they would consume as much federation bandwidth as a large instance. Most people wouldn't run a community, simply because they don't want to moderate it.

Realistically, the abuse problems you mention can already currently happen if someone wants to. It's easier to make an account on an existing server with a fresh email, spam a bit, and get banned than it is to register a new domain ($) and federate before doing the same. I think social networks would have a lot less spam if every time you wanted to send an abusive message, you had to spend $10 to burn a domain name.

Most of the content would still live on larger servers, so you end up moderating in the same place. Not much difference between banning an abusive user on your instance and banning an abusive single-user instance.

[–] [email protected] 7 points 1 year ago

Kinda being pedantic. It's a comment on a post about web3, responding to someone talking about a blockchain currency. Frankly, unless it's unclear enough that someone might come along and ask "what does cryptography have to do with blockchain?", I'm not sure why you feel the need to correct my usage of the word.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

Let's say they add some proprietary features. That's basically the difference between kbin and lemmy - they both support enough of the basic feature set required that anything they add on top of it is just "nice to have", not something which would prevent a lemmy user from switching to kbin if every lemmy instance gets shut down.

[–] [email protected] 12 points 1 year ago (3 children)

Plenty of creators have solved that already through platforms like patreon. It turns out that ad-supported content only works if advertisers want to advertise on your content, and large segments of media aren't "advertiser friendly".

No crypto required.

[–] [email protected] 220 points 1 year ago (17 children)

Hah, web 2.0 was all about the explosion of user-generated content. Corps and cryptonerds wanted to make web 3.0 about making money, but the web has always been about the content, not its monetization. In trying to monetize the content, they're alienating people and forcing them off the platforms they defaulted to.

Humans like to create and share content, no matter how easy or difficult it is to monetize. If the people who want to monetize humanity's collective output make it harder to create, then hopefully the result is that people move off the ad-supported platforms and replace them with something that doesn't rely on centralization with lots of capital to stay afloat.

If nothing else, the way that youtube has made it impossible for segments of the creative community to monetize their content and forced them rely on platforms such as patreon has made it more and more clear that ad-generated revenue is a dead end. You can't force people to view advertising unless you hold their content hostage, and for the first time in history, they can't buy out the means of production.

[–] [email protected] 0 points 1 year ago (1 children)

So let's say we want to scale up to several million users - what would that look like?

[–] [email protected] 4 points 1 year ago (1 children)

So you're saying that there's a sweet spot between the number of servers being federated and the number of users per server. I wonder what the optimal network distribution would look like.

 

What would happen if instead of users swarming existing servers when a fediverse service was put in the spotlight, each user spun up their own micro-instance and tried to federate with existing servers?

There's always the odd person who decides to host a personal fediverse service in their homelab for themselves, but would the fediverse work if that was actually the primary mode of interaction? Or would it fail in a similar way to now where the servers which receive the most federation requests need to scale up?

Presumably the failure modes for federation are easier to scale than browser requests since it's an async process.

 

Mine cried when the little boy in "The Giving Tree" took the tree's branches, and had me re-read the first few pages where he plays with the tree multiple times instead of finishing the book.

view more: next ›