this post was submitted on 04 Feb 2024
7 points (100.0% liked)

Learning Rust and Lemmy

391 readers
1 users here now

Welcome

A collaborative space for people to work together on learning Rust, learning about the Lemmy code base, discussing whatever confusions or difficulties we're having in these endeavours, and solving problems, including, hopefully, some contributions back to the Lemmy code base.

Rules TL;DR: Be nice, constructive, and focus on learning and working together on understanding Rust and Lemmy.


Running Projects


Policies and Purposes

  1. This is a place to learn and work together.
  2. Questions and curiosity is welcome and encouraged.
  3. This isn't a technical support community. Those with technical knowledge and experienced aren't obliged to help, though such is very welcome. This is closer to a library of study groups than stackoverflow. Though, forming a repository of useful information would be a good side effect.
  4. This isn't an issue tracker for Lemmy (or Rust) or a place for suggestions. Instead, it's where the nature of an issue, what possible solutions might exist and how they could be or were implemented can be discussed, or, where the means by which a particular suggestion could be implemented is discussed.

See also:

Rules

  1. Lemmy.ml rule 2 applies strongly: "Be respectful, even when disagreeing. Everyone should feel welcome" (see Dessalines's post). This is a constructive space.
  2. Don't demean, intimidate or do anything that isn't constructive and encouraging to anyone trying to learn or understand. People should feel free to ask questions, be curious, and fill their gaps knowledge and understanding.
  3. Posts and comments should be (more or less) within scope (on which see Policies and Purposes above).
  4. See the Lemmy Code of Conduct
  5. Where applicable, rules should be interpreted in light of the Policies and Purposes.

Relevant links and Related Communities


Thumbnail and banner generated by ChatGPT.

founded 9 months ago
MODERATORS
 

Running Test Instances

The question has come up of running a test instance under a domain such that it could federate with other instances over the internet.

See, eg, MxRemy's comment and the thread that follows: https://lemmy.ml/comment/7984848

We don't want to pollute the network

The issue is that we might "pollute" the federation network with our instances that won't do much and are likely to be short-lived or intermittent. If you don't know, managing how a lemmy instance reacts to other instances that have gone silent or failed to reply/receive a request is a thing. AFAIU, the general idea is you don't want to give up on an instance ... timeouts and downtimes happen ... but how do you know when to actually just give up? Most lemmy instances are likely still pinging instances/domains that went dark ages ago.

Our own closed/local federation

A work around though could be to run our test instances in "allowlist federation" mode. IE, they only federate with specified domains.

See the docs on this: https://join-lemmy.org/docs/administration/federation_getting_started.html?highlight=allowlist#federation


Should there be interest in this ... we could have a simple list of domains here (linked in the sidebar too) from people running their test instance and eager to poke and prod federation. When you setup your own test instance, you can then just run in allowlist mode and copy the list from here.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

See a core dev’s (nutomic ) comment on federating with their test instances being fine: https://lemmy.ml/comment/7986532