Relay usage is just a little bit too flexible at the moment. Long-term, we'll want to default to one or more high-quality, moderated relays, while still allowing user-configured relays (which we already do). For now, we will default to the main Kosmos relay as the only required read relay, and we're not requiring a specific write relay yet.
This way, content from the first known relay with 360+ content will always be loaded for now. More improvements, as well as a public, moderated Marco relay and Blossom server will follow in the future.
Relay usage is just a little bit too flexible at the moment. Long-term, we'll want to default to one or more high-quality, moderated relays, while still allowing user-configured relays (which we already do). For now, we will default to the main Kosmos relay as the only required read relay, and we're not requiring a specific write relay yet.
This way, content from the first known relay with 360+ content will always be loaded for now. More improvements, as well as a public, moderated Marco relay and Blossom server will follow in the future.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Relay usage is just a little bit too flexible at the moment. Long-term, we'll want to default to one or more high-quality, moderated relays, while still allowing user-configured relays (which we already do). For now, we will default to the main Kosmos relay as the only required read relay, and we're not requiring a specific write relay yet.
This way, content from the first known relay with 360+ content will always be loaded for now. More improvements, as well as a public, moderated Marco relay and Blossom server will follow in the future.