joshhsoj1902

joshhsoj1902 , 20 days ago

I fail to follow how a competitor can pop up if the main users it's attracting are ones that don't want to view ads or pay for subscriptions.

joshhsoj1902 , 20 days ago

The protocol isn't the hard part. It's the monetizing that is. Creators aren't looking to provide content for free, especially if they are also now paying for hosting costs.

Ad spots (like Google does) work well because they can inject an up to date ad into an old video. In something like the fedeverse today a creators only option would be ads baked into the video, but they would only get paid for that up front which isn't ideal...

joshhsoj1902 , 20 days ago (edited 19 days ago)

Sponsors pay more upfront. If creators are only using sponsors than their whole back catalogue is basically valueless. If it costs a creator 2-10 cents a month to host a video (based off S3 pricing), but they only made 1000$ on it upfront when the video was made, overtime the back catalogue becomes a pretty significant financial burden if it's not being monetized

Also it's worth keeping in mind that many people are also using tools to autoskip sponsor spots, and the only leverage creators have for being paid by sponsors are viewership numbers.

Patreon is irrelevant, that's just like Nebula, floatplane etc, it's essentially a subscription based alternative to YouTube.

Discoverability is pointless if the people discovering you aren't going to financial contribute. It's the age old "why don't you work for me for free, the exposure I provide will make it worth your time", that hasn't been true before and likely isn't here. Creators aren't looking to work for free (at least not the ones creating the high quality content we're used to today)

joshhsoj1902 , 2 months ago

If they could somehow make this data available to search engines. Maybe we can start being able to google random problems and actually find solutions again.

joshhsoj1902 , 5 months ago

This isn't completely true, but it is the current standard.

A website can detect and block many user/password attempts from the same IP and block IPs that are suspicious.

Websites can detect elivated login fails across many IPs are react accordingly (It may be reasonable to block all logins for a time if they detect an attack like this)

I'm sure there are other strategies, I don't know how often they are actually employed, but I wish companies would start taking this sort of attack more seriously (even if it's not at all hacking)