Question for everyone…

Recently I got GeekRoom.Tech fully operational and federating properly. However, before full success, I ran into a lot of issues and at one point had the domain as www.GeekRoom.Tech.

As you can see (here)[https://grafana.lem.rocks/d/edf3gjrxxnocgd/federation-health-activities-behind?orgId=1&var-instance=All&var-remote_instance=geekroom.tech&var-remote_instance=www.geekroom.tech&var-remote_software=All] the www version of the instance still has a bunch of instances trying to publish to it.

What is the best way to resolve that? I assume that those instances are actively trying to push activities but are constantly failing, potentially eating up bandwidth for them.

Hello all, I’m looking to get some icons and header images setup for the GeekRoom.Tech instance and its associated communities.

Would you be willing to create community images and banner images? It’ll help identify the communities when individuals want to post to these communities and helps create a community brand.

If you have some ideas of images or want to donate some images that would help the communities stand out, please feel free to link higher quality images to a comment and I’ll check them out.

Thank you in advance for anyone willing to help contribute!

Images needed: HomeLab icon and banner DataHoarder icon and banner FAQs icon and banner GeekRoomMeta icon and banner New Here icon and banner

I’ve got a site icon, but no banner. If you have other options for those images, I’d be happy to put something up there too!

Administration, moderation, and federation policy for GeekRoom.Tech

This post aims to lay out the rules and principles for how administrators, moderators, and users of GeekRoom.Tech should behave while use the GeekRoom.Tech name, address, and reputation. This is a set of formal rules that all users, admins, and mods must abide by.

Instance rules

This instance (like most others) has a set of rules which are always visible on the sidebar of the front page. All users of this instance are expected to follow these rules in all of their activities, including:

• Community moderation
• Posting
• Commenting

⚠️ Our rules apply even when you’re posting in a community on another instance. For example, this means that you’re not allowed to post advertisement spam using your GeekRoom.Tech account on any other instance (even if that other instance has no rules).

Each community hosted on GeekRoom.Tech is free to have additional rules in addition to our instance wide rules, but instance rules supercede any community rules and must always be enforced.

---

Responsibilities

Admins

• Ensure that there are no communities on GeekRoom.Tech which break GeekRoom.Tech rules
• Ban GeekRoom.Tech users who break our rules on other instances
• Ban users who consistently break rules across multiple communities
• Purge illegal content from GeekRoom.Tech

Moderators

• Ensure that posts and comments in their communities don’t break rules
• Ban users from their communities for consistently breaking rules
• Ensure that they only provide accurate and clear reasons for mod actions

Users

• Downvote low quality content
• Report rule violations
• Behave in a respectable manner

⚠️ Admins are not responsible for censoring content from other instances.

In exceptional cases (illegal or extremely disturbing content), admins will step in and purge the content from GeekRoom.Tech servers, but in general it is understood that our instance rules do not apply to external users on other instances, and censoring and curating external instances for our users is not a general goal for GeekRoom.Tech admins.

Federation Policy

You can see our federation policy here.

What should I do if I see content I don’t like on another instance?

• If it’s low quality content, you should always down vote ⬇️
• If you think it breaks local rules for the community or instance, then report it and local admins/mods will deal with it
  • Your reports will also reach GeekRoom.Tech admins, so if it’s about illegal content, then we can purge it from GeekRoom.Tech servers
• If it’s just some user being a prick, then you can block that specific user (GeekRoom.Tech admins will not take action in case of external users posting on external communities)
• If it’s a community dedicated to being awful in some way, then you can block that specific community

GeekRoom.Tech Federation Policy

As GeekRoom.Tech is a new lemmy instance, we have not seen any de-federation drama yet, but I want to make a point to address the policy of federation and de-federation in one place, prior to any drama that may eventually happen.

I am the head admin of GeekRoom.Tech. I have opened this instance to be a safe haven for all individuals that have a passion for technology, technology-related topics, and even those that just need a safe space to migrate from other websites such as Reddit without fear of shareholders forcing changes due to the need to make company profits.

This policy seeks to address how GeekRoom.Tech approaches de-federation and how we will handle discussions about de-federating from specific instances.

GeekRoom.Tech Statement of Federation

GeekRoom.Tech administration will treat de-federation as an absolute last resort and will not use it as a general purpose method of curating content for GeekRoom.Tech users. Administration will continue to federate with any willing instance.

Pros of federation

• Federation is the strongest feature of Lemmy, Mastodon, Kbin, Mbin, and similar instances. While there is often confusion about what the "Fediverse" and what "federation" is and what it means for individual people trying to migrate or start anew, federation offers significant decentralization over sites like Facebook, Reddit, X, Instagram, and similar.
• If a single instance goes down, it does not meaningfully affect the rest of the Fediverse. Users are able to choose to sign up for a new account on another instance, subscribe to their favorite communities again, and continue almost like nothing happened.
• The maximum impact that a single instance administration team can have is limited to their own instance. An admin of an instance can only ban users from their own instance, they cannot have a significant impact on any other instance, besides de-federating from another instance, again, limiting their impact to their own instance. We can ban our own users from our instance, we can ban remote users from our instance, but those actions would only impact our own instance.
• Federation offers significant privacy compared to centralized sites like Reddit and Facebook, because personalized details such as IP addresses or e-mail accounts are not shared between instances. If a user is extremely privacy-conscious and does not want to put trust in existing instances, they are more than welcome to self host their own instance.
• Lemmy and similar types of instances are essentially the infrastructure of the Fediverse. Each branch of infrastructure offers multiple opportunities to get involved in communities.

Cons of de-federation

• Every time an instance de-federates from the Fediverse, then it drives users to find other instances which may cause a higher level of centralization.
• Lemmy and similar types of instances are essentially the infrastructure of the Fediverse. Each branch of infrastructure offers multiple opportunities to get involved in communities, however, the larger the instances become, the more centralized that particular branch becomes. This does unfortunately negate the positives of federation and can cause an impact for a larger number of users.
• Collateral damage can be significant. If we de-federate from another instance at the demand of one, a dozen, or maybe even a few hundred users (when we get there), then all of those users that weren't involved in any drama or discussion will also be affected.
• It is incredibly easy for malicious actors to abuse this. If someone goes on to another instance and starts posting spam or generally malicious content and then approaches the admins of the instance with "evidence" of why that other instance should be de-federated, then it's easy to be manipulated and make admins think they have no other choice than to de-federate from that other instance.
• When instances de-federate from others, it means that users may end up requiring multiple accounts in order to be able to participate in discussions between instances, causing a very fragmented experience for them.

Alternatives to de-federation?

There are options that moderators and administrators of instances have, such as banning a user from a community and even from entire instances. If an entire community is used for hate, spam, or similar then those entire communities can be removed. Most issues can be resolved by simply communicating with other instance owners and either issuing bans for specific users or discussing how to handle those misbehaving users.

If GeekRoom.Tech de-federates over every single misbehaving user, we would likely not be federated with any other instances, which is something we seek to avoid.

Most individual clients have the option to block individual users and entire communities without involving instance admins. This leaves most of the decision up to the end-user rather than requesting involvement from admins.

When is de-federation the only option?

This is not a set-in-stone rule, but if an instance is abusing the Lemmy infrastrucutre by generating spam, posting illegal content - deliberately or not - then we may decide that de-federation is the appropriate last resort.

Conclusion

Most of what is written here is subjective, and for that I can only apologize. I will do my best to operate GeekRoom.Tech with the highest level of professionalism, maturity, and decisiveness to deliver the best experience for users across GeekRoom.Tech and throughout the Fediverse.

If you have questions or concerns, please feel free to share your thoughts in the comments so that we can have a public discussion on how federation and de-federation can be approached.

Hello! Just wanted to introduce myself a bit.

I’m a system administrator during the day working with some PITA IBM products, Linux, and related projects as smaller duties.

I’m an avid HomeLabber trying to expand my own skill set but also provide a way for people to engage and have meaningful conversations. During my free time I’m usually tinkering with existing self hosted services or trying to setup new ones to enhance my family’s experience or to make life easier in some fashion.

I have a passion for basically everything technology and learning as much as I can. I realize that as I get older, I’m not picking up on things as fast as I would previously, but I’m going to attribute that to attempting to introduce significantly more complex systems that require more effort, critical thinking, and time to implement.

Two of my most recent successes in my self hosting journey have been getting this Lemmy instance up and running, and also getting VLANs fully functioning in my home network. I have too many pieces to a puzzle that caused most people to be unable to help me successfully.. it took me just about a year of off and on again searching through forums, asking AI and critical thinking on how to get VLANs working properly in my homelab. Well… home production … since there are family members and myself using these things in the regular.

Edit: as I read this post back I found a bunch of errors. iOS autocorrect has screwed me so many times, it’s frustrating. Why iOS doesn’t know “Lemmy” after I’ve saved it as a word so many times is baffling.

Borrowing from @[email protected]'s post and @[email protected]'s post:

For anyone interested, here’s the Lemmy markdown configuration. As you can see, Lemmy’s website UI supports the full commonmark spec (tutorial / official spec), plus a bunch of extensions. I don’t think anyone’s fully documented these yet, so I’ll try doing so below. Apologies in advance to mobile users, this is probably gonna get ugly (see included image links for how it should look):

• URL autolinking (plaintext URLs automatically turn into links, as recognized by Lemmy... but some may not be autorecognized due to new domain extensions)
• Manually linking URL: [name of link](https://actual.link/) → name of link
• Lemmy autolinking:
  • NOTE: No link will be inserted if the viewer is browsing an instance where the resource is not yet known/blocked
  • Communities: [[email protected]](/c/[email protected]) → [email protected] (link ref: /c/[email protected])
    • Kbin-style is also supported: /m/[email protected] → /m/[email protected]
  • Users: /u/[email protected] → /u/[email protected] (link ref: /u/[email protected])
• Typography substitutions:
  • (c) → ©
  • (tm) → ™
  • (r) → ®
  • +-→ → ±
  • ... → …
  • --- → —
  • -- → –
  • ???? (>= 4x) → ???
  • !!!! (>= 4x) → !!!
  • horizontal rule (line between paragraphs) --- →

---

• **bold** → bold

• *italics* OR _italics_ → italics

• # Headings → # Headings (1 # for level1 heading, up to 5 #'s; must be at start of new line) [requires space between the #'s and the text]

• [Link text](https://link.com/) → Link text

• Github-flavor Markdown extensions:

  • Tables
  • Strikethrough: ~~example~~ → ~~example~~

• Subscript/Superscript:

  • Sub: example~sub~ → example~sub~
  • Super: example^super^ → example^super^

• Footnotes:

  • Inline part: example[^notename or a number] → example[^1]
  • Bottom part: [^1]: My reference (must be placed at VERY end of post to work.)

• Ruby Text: {example base text|example ruby text} → {example base text|example ruby text}

  • “Ruby” is an html-ism for special pronunciation aids which frequently appear within young person’s media where the language includes non-phonetic characters (e.g.: Chinese characters)
  • Japanese Furigana example: {凄|すご}い！→ 凄い！

• Spoilers:

    
visible text
    hidden part example
    

visible text

hidden part example

• Code blocks:

`inline code` → inline code

code block:

 ```
 println(“Hello World!”)
 println("Line 2")
 ```

becomes

println(“Hello World!”)
println("Line 2")

OR

4 spaces at beginning of each line to be included in the code block becomes

this is a code block
line 2

---

Code Block Syntax Highlighting!

When after using the three backticks to start a code block, specify the language.

Rust:

    ``` rust
    // This is the main function
    fn main() {
        // Print text to the console
        println!("Hello World!");
    }
    ```

becomes:

// This is the main function
fn main() {
    // Print text to the console
    println!("Hello World!");
}

No language specified, defaults to "C" language:

// This is the main function
fn main() {
    // Print text to the console
    println!("Hello World!");
}

Text:

    ``` text
    // This is the main function
    fn main() {
        // Print text to the console
        println!("Hello World!");
    }
    ```

becomes:

// This is the main function
fn main() {
    // Print text to the console
    println!("Hello World!");
}

Python:

    ``` python
    // This is the main function
    fn main() {
        // Print text to the console
        println!("Hello World!");
    }
    ```

becomes:

// This is the main function
fn main() {
    // Print text to the console
    println!("Hello World!");
}

---

Finally:

If I want to write a character that will normally be interpreted as any of the above, I can escape the character with a backslash → \ ... So you can write something like \^this → ^this

[^1]: To make this footnote, I used the formatting defined above, preceding this text with "[^1]:"

Hello! I want to personally welcome you to GeekRoom.Tech. I seek to make this Lemmy instance a fantastic place for anyone and everyone that enjoys technologies of many different kinds.

GeekRoom.Tech is meant to provide a safe haven for individuals to have discussions without fear of censorship and fear of being banned for asking what others believe to be silly questions.

Everyone starts somewhere in their technology journey. I want to be sure that everyone is respectful in their discussions and understands that others may not have the easiest time understanding advanced topics as easily as you.

If you have any questions, please reach out to myself or any other mods or admins for assistance. We seek to enrich your brains and find ways to help you achieve your technological goals!

Email Contact: [email protected]

Mastodon: @[email protected]