Thanks! And no worries, I understand. You donât want to maintain a fork of that beast, trust me :)
Seems I have to devote some time in the future to swapping out Mastodon with a fediverse server designed for a single person. I believe there are a couple of projects in that area.
Itâs ridiculous to host something designed to hold a million people for just one person. Itâs like living in a skyscraper by yourself: not good for you, not good for the environment, or for anyone :)
Still, I don't think that the public APIs rate limit should be removed. That would open the door to all sorts of attacks or abuses.
But I agree that rate limits should not affect regular usage of the web interface. For me, is more why does this happen/how to fix it and less on how to disable it.
About the single user software, 100%. I can think of so many way to make that software much simpler and less resource intensive.
I would like to see a one person microblog âserverâ for the #fediverse which I could install on my share webspace. As much easy as implementing WordPress and co.
Sadly, ActivityPub itself makes this difficult but itâs not impossible by any means. But itâs not what ActivityPub was designed for. (So we are somewhat trying to stuff a square peg into a round hole.)
The small web stuff, on the other hand, is being designed with specifically this use case in mind. (But isnât usable yet. Which means thereâs lots of value in exploring these solutions on the fediverse and getting folks thinking in this direction as soon as possible.)
This issue is to request the ability to change the rate limits using environment variables or using the UI (i.e., in the administration site settings). I host a personal, single-user Mastodon insta...
Rate limiting password retries is a security property. Rate limiting message sending (beyond what would remove automated flooding) is a property of designing a system for 1-800,000 people (which means designing for 800,000 people instead of for instances of 1).
IMHO the mistake is separating server from client. p2p software, that encompasses both server and client features, enables true decentralization without running into such walls and complexity
Unfortunately p2p systems have their own challenges. Namely: findability and availability. Solving both of those reliably usually entails centralised servers of some type (eg., for signaling, fallback, etc.) So the idea behind a small web architecture is: if we will likely need servers for the foreseeable future, why not make it so that everyone has their own. So youâre topologically decentralising that aspect. And it also simplifies a huge amount of stuff all across the stack.
Aral Balkan
in reply to Aral Balkan • • •Aral Balkan
in reply to Aral Balkan • • •Masto.host
in reply to Aral Balkan • • •There are no other rate limits applied on my end.
So, I can't really do much on my end without forking and changing the Mastodon code. Sorry :|
Search · rate limit · mastodon/mastodon
GitHubAral Balkan
in reply to Masto.host • • •Seems I have to devote some time in the future to swapping out Mastodon with a fediverse server designed for a single person. I believe there are a couple of projects in that area.
Itâs ridiculous to host something designed to hold a million people for just one person. Itâs like living in a skyscraper by yourself: not good for you, not good for the environment, or for anyone :)
Masto.host
in reply to Aral Balkan • • •Still, I don't think that the public APIs rate limit should be removed. That would open the door to all sorts of attacks or abuses.
But I agree that rate limits should not affect regular usage of the web interface. For me, is more why does this happen/how to fix it and less on how to disable it.
About the single user software, 100%. I can think of so many way to make that software much simpler and less resource intensive.
CC @c3po
Robert Lender
in reply to Masto.host • • •Aral Balkan
in reply to Robert Lender • • •The small web stuff, on the other hand, is being designed with specifically this use case in mind. (But isnât usable yet. Which means thereâs lots of value in exploring these solutions on the fediverse and getting folks thinking in this direction as soon as possible.)
đđđđđđđ
in reply to Aral Balkan • • •Eugen Rochko
in reply to Aral Balkan • • •Aral Balkan
in reply to Eugen Rochko • • •Donât get me wrong, Iâm hugely thankful for Mastodon. Without it we wouldnât have the fediverse. But the level of centralisation is a problem.
Youâre designing for 800,000 in one place (because thatâs what you have to moderate â a task I do not envy you), not 800,000 separate instances.
This is the Achilles' heel of Mastodon/the fediverse.
And, again, Iâm hugely grateful it exists.
FiXato
in reply to Aral Balkan • • •@Gargron
Allow administrators to configure rate limits · Issue #15832 · mastodon/mastodon
GitHubDavid Chartier
in reply to Aral Balkan • • •Aral Balkan
in reply to David Chartier • • •Aral Balkan
Unknown parent • • •LPS
in reply to Aral Balkan • • •fatboy :mxlinux: :debian:
in reply to Aral Balkan • • •Amit Gawande
in reply to Aral Balkan • • •Aral Balkan
in reply to Amit Gawande • • •Aral Balkan
Unknown parent • • •Alexandre Oliva
in reply to Aral Balkan • • •Aral Balkan
in reply to Alexandre Oliva • • •