News for hackers. Stuff that matters.
Re:Blue Sky: Can Twitter be owned by its users? by thrashh on Wednesday April 12, 2023 @02:39AM (#35535823)
I don’t understand how this is going to take off if no one is going to make money from this.

A server can’t really charge its users. I and most people would probably not pay to help support a server. Twitter works because most people who actually interact on it don’t pay.

And the source of Twitter’s woes is honestly because it has never made money.

Also, requiring a domain name to have an alias? So this service is just going to be a community of sysadmins and web developers?

Re:Blue Sky: Can Twitter be owned by its users? by ly3xqhl8g9 on Wednesday April 12, 2023 @02:51AM (#35535892)
The simplest/best way I could think of is for users to be paid for their messages. You post something insightful, funny, worthy of attention, other users decide to pay you 0.00whatever USD. The problem then becomes that we haven't actually solved micro and nano-transactions in these 30-something years of HTTP over TCP connections [1].

[1] RFC 8905 - The 'payto' URI Scheme for Payments, https://www.rfc-editor.org/rfc/rfc8905.html

Re:Blue Sky: Can Twitter be owned by its users? by diordiderot on Wednesday April 12, 2023 @02:53AM (#35535898)
> Also, requiring a domain name to have an alias? So this service is just going to be a community of sysadmins and web developers

e.g. mastodon

Re:Blue Sky: Can Twitter be owned by its users? by bohm on Wednesday April 12, 2023 @02:59AM (#35535927)
there's no requirement to get your own domain name. when you sign up you automatically get a yourname.bsky.social domain.
Re:Blue Sky: Can Twitter be owned by its users? by jrm4 on Wednesday April 12, 2023 @01:31PM (#35543474)
Um, ever heard of email?
Re:Blue Sky: Can Twitter be owned by its users? by ryan29 on Wednesday April 12, 2023 @07:50PM (#35548785)
> I don’t understand how this is going to take off if no one is going to make money from this.

I'd pay something for it. The way the author describes it I would have a 'Small-World' server. I'd be willing to pay $5-10 per month to connect that to a 'Big-World' server. After that I'd expect the costs to scale with the size of my 'Small-World' server. As long as that's based on resource consumption rather than some kind of per-user scheme I think it would work fairly well.

The biggest issue for me would be setting up and maintaining a server. I don't really want to do that and a hosted service for it probably skews towards costs that are more than I'd be willing to pay just to be connected to the network.