That is because the problem is not solved yet. Again “We have to solve the money problem!”

That means it is nowhere near being solved. It will be solved when FSF staff ( from donations ) will have a life worthy of envy. And any fediverse admin too. And any libre software developer too.

I think that we need to have a panic making notification when some instance is below a comfortable ( of it’s operator ) level of money. So that people could direct their money into stopping the panic. Basically I want automatic sense of urgency when and where it’s needed. FSF does it well. When they are low on money they just make a progress bar on every page they operate, with a link to a donation page. It works amazingly for them, because it immediately creates a sort of soft panic about the health of the FSF.

Anybody who is on something like #fsf on IRC, or who helps to organize the Libre Planet. Or people who buy computers from the Ministry of Truth. Aka people that are as serious about this ( if not more serious ) than Richard Stallman.

We failed the instance operators if they need to lie about money. What we need to insure is that those people can both run the instance and live a live worth of envy from the money provided by the supporters. Meaning any money above the costs is good money. Any money below the margin of live worthy of envy is not enough money. The line is not at being able to pay for hosting. The line is at live worthy of envy.

no one accounts for the labor of the admins and moderators

These need to be part of the report. We have to fund not just hardware, but good life ( worthy of envy ) of those people. If their lives aren’t worthy of envy now, the fediverse isn’t healthy and we need to donate more.

lol

We need to make it easy to check the financial health of an instance. And things like costs and money made from donations should be visible, and rendered as progress bars or charts. So people would know when and to whom to donate.

I know a pretty substantial amount of those people. But most likely they will not object to it. They will just see that the option is not there and move on. They are kind of already used to not seeing an option. Many of them don’t even look for it, or even think there could be one. Only maybe FSF has donation options for those people.

Most likely the assets are viewed a handful of times in one day and never seen again… but you’ll pay to store it forever!

This is exactly the thing that should optimized immediately. Store relevant content. Delete after it is not relevant. Fetch it back if it is relevant again.

The expense of running busy servers is too much to expect of anyone

We have to think about that a lot of people on the fediverse today ( and that number only grow the more people join ) that are normies. They expect it work the same exact way anything else works. And they won’t know or care to know any of the underlying technical things about it.

I talked to Jerry and here is my interview: https://blenderdumbass.org/articles/clarifying_costs_of_running_the_fediverse_with_jerry_from_infosec.exchange

I asked Jerry about everything. Here is the interview:

https://blenderdumbass.org/articles/clarifying_costs_of_running_the_fediverse_with_jerry_from_infosec.exchange

I asked Jerry Questions and here is an interview: https://blenderdumbass.org/articles/clarifying_costs_of_running_the_fediverse_with_jerry_from_infosec.exchange

Storage Duplication is I think not necessarily an issue of ActivityPub, it’s an issue of implementation of it. Because all posts can technically live on their respective servers. And rendered directly or almost directly. Like it can be copied over for the time it is relevant, and then discarded to be available only from the original server.

You are misunderstanding the main idea behind the whole system. It is fork-able. So people can always change things they personally find they don’t like about it. You can not have anything where everybody has to do. Because those who don’t agree have all the technological and legal right to ignore you and do what they want instead. And this is the point with libre platforms ( or libre software in general ).

Whatever solution we find needs to take this fundamental thing into consideration.

I think he mentioned he run 3 96-core servers for that instance to be running. Or something.

So the question is, what the hell should we do about this? How do we solve this? How do we even approach to solving it? Should I setup a forum page, somewhere, or a chat, where people can discuss everything and start approaching something? Or are we simply doomed?

try spoofing a user-agent or torifying it maybe

This doesn’t have any link to code. And all the other buttons say that the docs are not implemented yet.

Seems like somebody mentioned the account on the fediverse that started a chain reaction of various instances requesting a bunch of stuff. Which made it to Mastodon.social too. It still doesn’t work though.

The server is written in python and the idea is to make it deploy-able without needing to install anything extra. So I’m trying to implement my own activity pub.