Editorial Policy

1. Who this policy binds

METARUBY is published by KATAR DİJİTAL MEDYA HİZMETLERİ ANONİM ŞİRKETİ, Trade registry number 968192-0, registered at Firuzağa Mah. Müeyyedzade Cad. No:188 Kat:1 Daire:2 Gaziosmanpaşa İstanbul Türkiye. This policy applies to everything published on metaruby.org, including articles, explanatory pages and any future contributed material.

2. What we publish

Original technical writing about information security, aimed at people who want to understand a mechanism rather than be handed a conclusion. In practice that means explanatory guides, analyses of how a class of attack is constructed, and plain descriptions of how a documented system behaves.

Our coverage includes the security of Web3 and wallet interfaces. We treat this as a social-engineering and user-interface subject, because that is where the losses come from, and we treat it strictly as education.

3. What we never publish

These are standing constraints on the publication, not preferences that shift with a new writer or a new commercial opportunity:

• Financial, investment, legal, accounting or tax advice, in any form.
• Price predictions, yield or APY comparisons, trading signals, or any recommendation to buy, sell or hold an asset.
• Affiliate links, referral codes, sponsored articles or paid reviews. Paid placement exists only in the marked slot described in section 7, never inside an article.
• Promotion of, or referral to, exchanges, wallets, token sales, airdrops, staking, swaps or any other transaction — in our writing and in the sponsorship slot alike.
• Any control that asks a reader to connect a wallet, sign a message, approve a transaction, transfer a token or make a payment.
• Instructions to install a browser extension or application, run a file, or begin a remote-support session.
• Claims of guaranteed protection, absolute security, or recovery of lost assets, and any offer of a recovery service.
• Any statement implying that we are, represent, or are endorsed by a vendor whose product we describe.
• Manufactured urgency, fear-based framing, or invented statistics used to make a point land harder.

4. Sourcing standard

Technical claims are established from primary material: the relevant specification, the vendor's own published documentation, or an advisory from a named public institution. Secondary coverage — other people's articles about a subject — may indicate that something is worth investigating, but it is not treated as evidence of what is true.

Every article carries a numbered bibliography, and each significant technical assertion in the body points to an entry in it. Where a claim cannot be traced to a source of that kind, it is removed rather than hedged. Figures, dates and quantities are used only when a cited source supports them; we do not use approximate statistics for rhetorical effect.

Quotation is kept short and attributed. We do not reproduce substantial passages from other publications, and we do not rewrite another article and present it as original work.

5. Accuracy, review and dates

Before publication, each article is checked so that every factual assertion has a matching reference, every external link resolves, and the draft has been read once more specifically for overstatement. Guarantees, absolutes and implied promises are the failure mode we look for hardest.

Each article displays the date it was published and the date it was last reviewed. A substantive change — a corrected fact, a revised recommendation, a materially updated section — updates the review date and is described on the page. Fixing a typographical error does not, and we do not re-date an article to make old material look new.

6. Corrections and the right of reply

If something here is wrong, we want to know. Write to editorial@metaruby.org with the page address and the sentence in question.

• Factual errors are corrected on the page. Anything that changes the meaning is noted visibly rather than fixed silently.
• Organisations we name may respond. Where a response corrects the record, the correction is made; where it disputes an interpretation we stand behind, we will say so and cite the source we relied on.
• Withdrawal is reserved for material that cannot be corrected. A withdrawn article is replaced by a note explaining why, at the same address, rather than deleted.

We aim to acknowledge correction reports within five business days.

7. Funding, sponsorship and advertising

METARUBY is funded by its operating company and may also carry sponsorship.

Any advertising on this site is limited to a single slot per page, placed below the content and above the footer, and labelled Sponsored. There is never more than one, and there is no other paid placement anywhere on this site. The slot may be occupied, unsold or switched off entirely at any time; the rules below apply whenever it is shown, and nothing else about this policy depends on whether it is.

7.1 What sponsorship does not buy

A sponsor pays for that space and nothing else. Specifically, sponsorship never buys:

• coverage, or a mention, in any article;
• influence over the wording, framing, conclusion or timing of anything we publish;
• the removal, softening or delay of an article, including one about the sponsor;
• sight of an article before it is published;
• any link inside editorial text, or any link that passes ranking credit.

Nobody who sells the slot has any say over what is written, and no writer is told who occupies it. If a sponsor asks for any of the above, the sponsorship ends rather than the article changing.

7.2 What we will not accept

The slot is closed to whole categories, not judged case by case:

• exchanges, wallets, tokens, token sales, airdrops, staking, yield products, trading services or any other financial product;
• asset-recovery services of any kind;
• anything that would ask a reader to connect a wallet, sign, approve, transfer or pay;
• any advertiser that is the subject of a current article, so that no reader has to wonder whether the two are connected;
• anything we would not be willing to name in this policy.

7.3 How it is served

The slot is plain text served from this domain. There is no advertising network, no third-party script, no tracking pixel, no cookie and no measurement of any kind, so a sponsor learns nothing about you — not that you visited, not what you read, not that you were shown the slot. Sponsors are billed for a period, not for impressions or clicks, because counting either would mean tracking readers.

Sponsor links carry rel="sponsored nofollow", so paid placement transfers no search ranking credit.

7.4 When the slot is unsold or absent

An unsold slot says so rather than being hidden: we would rather show that part of this site is for sale than disguise it. The slot can also be switched off completely, in which case no advertising appears anywhere. Neither state changes anything in this policy, which describes the limits on advertising rather than the presence of it.

What would require a change here is a change to those limits — a second slot, placement inside articles, an advertising network, or any of the categories in 7.2 becoming acceptable. Any of that is written into this section and About in the same release as the change, never after it.

8. Conflicts of interest

Anyone writing for METARUBY must disclose any material interest in an organisation or product covered by their article. Where a conflict exists and the article still has value, the interest is disclosed on the page. Where disclosure would not be enough, the article is not published.

Sponsorship is treated as exactly this kind of conflict. An organisation that is the subject of a current article cannot buy the slot, and an organisation occupying the slot does not become a subject we avoid either. Where the two would collide, the sponsorship is declined — never the article adjusted.

9. Naming third parties and using trademarks

We name products, companies and services where naming them is necessary to describe documented behaviour accurately. All trademarks and product names belong to their respective owners, and their use here is descriptive and nominative only.

Naming a product is never an endorsement, a criticism of the vendor's integrity, or a claim of any relationship with it. METARUBY is editorially independent. It is not affiliated with, authorized by, supported by, or endorsed by any company, product or service named in its articles. Where we describe a vendor's behaviour, we cite that vendor's own documentation so the description can be checked at source.

10. External links

Links in our writing point directly to the primary source, never through a redirector, a tracker, a shortener or an affiliate wrapper. We link to a vendor's own documentation where that documentation is the evidence for a claim; such links are informational and are not a recommendation to use, install or purchase anything.

The one exception is the sponsorship slot in section 7, which is advertising rather than writing. That link is commercial, is labelled as such, sits outside the content and carries rel="sponsored nofollow". No link inside an article is ever paid for.

We do not link to tools that ask a reader to connect a wallet or authorise a transaction, even where such tools are widely used, because that pattern is indistinguishable from the attack it is meant to remedy.

11. Reader safety

No page on this site will ever ask you for a password, recovery phrase, private key, one-time code or any other secret. We will never contact you first about a wallet or account problem, never offer to recover assets, and never ask you to install software or start a screen-sharing session.

Anything that appears to be METARUBY and does one of those things is an impersonation. Please report it to security@metaruby.org.

12. Changes to this policy

Changes take effect when published on this page, and the effective date above is updated. Because this policy describes what we do rather than what we intend, a change here means the practice has changed too.

13. Contact

Editorial matters and corrections: editorial@metaruby.org. Anything else: contact@metaruby.org, or use the contact page.