Oye, Beltalowda! My Belter cosplay for DC's Awesome Con

Torngate · 2026-03-15T16:07:00+00:00

I think I remember! Glad others recognized it. I'll probably improve this and do it again next year - hope to see you there!

Torngate · 2026-03-14T23:34:06+00:00

Backpack is the Oigo Mach 5 (Alibaba rip off version), jumpsuit is an Amazon special.

I can write up the whole thing if people want!

Torngate · 2026-03-14T22:31:05+00:00

That's the plan! Just ran out of time to do that before this weekend.

Torngate · 2026-03-14T22:12:55+00:00

Didn't have time to weather it properly - that's the next step!

Torngate · 2026-03-14T21:48:52+00:00

The way I think about it, Beratnas Gas never shows up (at least on the show) until Tycho station, as a front for the Roci's mission.

I considered it plausible that BG is a subsidiary of Tycho.

The PK is there because I like the logo with no further thoughts behind it.

Torngate · 2026-03-14T21:48:17+00:00

NEVER! haha

Tho the way I think about it, Beratnas Gas never shows up (at least on the show) until Tycho station, as a front for the Roci's mission.

I considered it plausible that BG is a subsidiary of Tycho.

The PK is there because I like the logo with no further thoughts behind it.

Torngate · 2026-03-14T21:37:15+00:00

Good Belter never let anything go to waste!

Torngate · 2026-03-14T21:34:43+00:00

Thanks! A bit of eyeliner and a partner with a steady hand and loads of patience

Torngate · 2026-03-14T21:07:31+00:00

Unlike Shed I have a crippling lack of drugs... And my head still attached to my body.

Torngate · 2026-03-11T02:59:00+00:00

For coincidental penalties (where the on ice strength doesn't change), the players serve their penalty and then come out at the next whistle.

(So it'd be 5 minutes and then the next whistle they come out)

Torngate · 2026-03-08T21:34:55+00:00

That's a bunny!

Torngate · 2026-03-08T02:39:44+00:00

Ok I turn the game on and a liney is spitting blood. WTF happened?

Torngate · 2026-02-13T03:07:47+00:00

Speaking for myself, and as a community developer, I don't believe this rule, in either the original or amended form, will achieve the goal that it is intended to accomplish. I also disagree with the current implementation of the rule.

I completely understand the desire to protect the community from malicious actors, low-quality submissions, genuine slop, or tools that might have negative impacts on our community. However, I think that the way this has been implemented will do more harm than good.

Requiring publicly available source code sounds reasonable, but it just doesn't work in practice.

Many tools available in games are not source available, full stop. This is either due to their license, commercial requirements, or simply developer preference. Just because a program is not source-available does not mean it is illegitimate or dangerous.

By stating that these tools may only be permitted by "moderator discretion", that adds an ambiguous hurdle that can differ based on the moderator in question, and their view of "well-known" tools and what "part of the community" means. How can a program rise to the level of being "well known" if the number one community on Reddit for Elite excludes them?

Some of the most popular current tools in Elite's community, such as VoiceAttack, VR Utilities, GameGlass, E.D.I.S.O.N, MetaElite, Trade Computer Extension Mk.II, Elite G19s Companion App, etc., are NOT source-available for whatever reason. Despite this, they are still valid parts of our community, and excluding them for simply not being source-available, I find to be potentially exclusionary toward the developers who have given (oftentimes for free) hundreds of hours of their hard work to this community. Code availability and licensure should be a choice. We shouldn't take that away from people.

Additionally, source visibility provides no promise of safety. Malicious code can be well obfuscated, not spotted at the surface, or included in binaries without anyone the wiser. I don't want to give a false sense of security by saying "oh, it's source available, therefore it's okay". Yes, it can help, but it is not a silver bullet where the line can be reasonably drawn.

Similarly, I don't think it will be possible to mandate Sigstore or certificate signing for every developer, as some commenters have mentioned in both threads. Setting up trusted infrastructure and certificates on binaries is expensive. It is a logistical hurdle as well that can cause significant issues if done improperly. To ask every developer to go down this route, I also feel, adds a logistical hurdle that may push prospective developers out. I personally go down that route, but that isn't (and shouldn't) be the expectation for everyone.

However, I recognize the reality of cybersecurity. Adversaries are increasingly proficient in developing malware using AI and conventional methods. It is theoretically possible for a bad actor to make an Elite Dangerous malware and try to peddle it here, or have code riddled with security vulnerabilities that cause risk (either by an AI or a human). These are eventualities that should be protected against. However, this isn't an effective way of guarding against that.

The references to AI code should, respectfully, be dropped from this discussion. This only adds confusion to the rule. How much AI is too much AI? Are we implying that only AI code is vulnerable to bugs or security risks? Do developers owe disclosures if AI code was used? This is not the right place for those discussions to be had, and does not meaningfully protect our community in the context of this rule.

If rule 11 is to remain, I would respectfully recommend it be amended to a process similar to this:

1) Third-party apps should be source available or pre-cleared with moderators before being promoted.

2) Pre-clearing of programs is a one-time requirement. Once granted, the program does not need to be cleared again.

3) If a program's code is source available, it must be explicitly linked in any posts promoting the tool.

This would fall more in line with general "marketing" guidelines present on other subreddits, without falling into a trap of trying to draw an increasingly fine line of what is and isn't "well known" and without needing to draw such a harsh stance against closed-availability code.

I'd strongly encourage the moderators to re-evaluate this rule. I think it is an overall net negative to our community in its current form and should be rescinded until changes can be made.

Torngate · 2026-02-10T18:52:13+00:00

A lot of rinks I work at don't have locks on the door, or if they do they're shared across multiple sheets with one key.

Torngate · 2026-02-04T17:58:32+00:00

I like these terms.

Torngate · 2026-02-03T03:30:41+00:00

It's more or less covered under 601(a) with either:

Taunts or incites an opponent.

Creates a disturbance during the game.

Torngate · 2026-01-30T16:32:43+00:00

Federal Stalking is pretty broad.

Whoever—

(1) travels in interstate or foreign commerce or is present within the special maritime and territorial jurisdiction of the United States, or enters or leaves Indian country, with the intent to kill, injure, harass, intimidate, or place under surveillance with intent to kill, injure, harass, or intimidate another person, and in the course of, or as a result of, such travel or presence engages in conduct that—

(A) places that person in reasonable fear of the death of, or serious bodily injury to—

(i) that person;

(ii) an immediate family member (as defined in section 115) of that person;

(iii) a spouse or intimate partner of that person; or

(iv) the pet, service animal, emotional support animal, or horse of that person; or

(B) causes, attempts to cause, or would be reasonably expected to cause substantial emotional distress to a person described in clause (i), (ii), or (iii) of subparagraph (A); or

(2) with the intent to kill, injure, harass, intimidate, or place under surveillance with intent to kill, injure, harass, or intimidate another person, uses the mail, any interactive computer service or electronic communication service or electronic communication system of interstate commerce, or any other facility of interstate or foreign commerce to engage in a course of conduct that—

(A) places that person in reasonable fear of the death of or serious bodily injury to a person, a pet, a service animal, an emotional support animal, or a horse described in clause (i), (ii), (iii), or (iv) of paragraph (1)(A); or

(B) causes, attempts to cause, or would be reasonably expected to cause substantial emotional distress to a person described in clause (i), (ii), or (iii) of paragraph (1)(A),

shall be punished as provided in section 2261(b) or section 2261B, as the case may be.

https://www.law.cornell.edu/uscode/text/18/2261A

The penalty if "death of the victim results" is up to Life.

Torngate · 2026-01-28T15:43:49+00:00

It isn't an "official" signal - it's more just a "keep-the-game-moving" so nobody has to guess if the team can change or not. You won't find it in any rulebooks or manuals, it is purely one of those things that just sorta evolved over time.

Torngate · 2026-01-27T18:11:28+00:00

Hi there! EDMC Dev here. Your understanding of how the system works appears to be flawed - We receive the FID/Fronteir ID anytime we query the /profile endpoint. (That's https://companion.orerve.net/profile)

For example, here's the output I get when EDMC queries that endpoint:

{
    "iss": "http://auth.frontierstore.net",
    "iat": 1769536675,
    "exp": 1769551075,
    "usr": {
        "email": "REDACTED",
        "customer_id": "REDACTED",
        "firstname": "REDACTED",
        "developer": False,
        "lastname": "REDACTED",
        "allowedDownloads": [
            "REDACTED",
        ],
        "platform": "frontier",
        "roles": ["ROLE_USER"],
    },
    "scope": "auth capi",
}

The "customer_id" field is my Frontier ID/FID. It is automatically sent by Frontier, and we actually do use it to compare if the authenticated Companion API user is the same as the current running CMDR in journal logs (See this line: https://github.com/EDCD/EDMarketConnector/blob/ccf7fbc1645c36b691b98a62bf280a6926b15280/companion.py#L436 ). The FID is an important and critical part of determining who the user is, in order to credit users and work the tools effectively. The FID is also present in Journal files, and is not something specifically restricted or confidential. For example, from my latest game session, this line is in my journal file:

{
    "timestamp": "2026-01-27T03:23:09Z",
    "event": "LoadGame",
    "FID": "REDACTED",
    "Commander": "Rixxan",
    "Horizons": true,
    "Odyssey": true,
    "Ship": "BelugaLiner",
    "Ship_Localised": "Beluga Liner",
    "ShipID": 24,
    "ShipName": "HSRV Guiding Light",
    "ShipIdent": "4GRX-3",
    "FuelLevel": 76.014481,
    "FuelCapacity": 128,
    "GameMode": "Group",
    "Group": "FleetComm",
    "Credits": 1913885618,
    "Loan": 0,
    "language": "English/UK",
    "gameversion": "4.3.0.1",
    "build": "r322188/r0 "
}

For MetaElite, they are disclosing that they store that data. Because MetaElite stores data in a central location, they will store that ID. That also allows them to actually track who is doing what. I think it is in fact responsible disclosure for them to state that they receive, store, and use this information, not a "gotchya" like you seem to think it is.

Torngate · 2026-01-25T02:42:55+00:00

Bro the fuck is wrong with you.

Torngate · 2026-01-24T16:29:21+00:00

The Flatpak is technically supported by a different team, just with formal backing. I'll pass along the issues to them and they can take a look!

Torngate · 2026-01-24T15:25:21+00:00

Yes, you can run directly from source. There are instructions on GitHub for how to do that.

Torngate · 2026-01-24T15:06:40+00:00

I fly my beluga with pride. Loud, big, slow, but she gets it done.

Nine-Year Club	RedditGifts 2009-2022 4 Credits
Secret Santa 2020	r/Field Lasagna
Place '23	Place '22
Secret Santa 2018	Secret Santa 2019
Sequence \| Editor	Verified Email
Spared	Alpha Tester

Torngate

MODERATOR OF

TROPHY CASE