i18n: locale aware content collections [beta]#2643
Open
redsh4de wants to merge 7 commits intomonero-project:betafrom
Open
i18n: locale aware content collections [beta]#2643redsh4de wants to merge 7 commits intomonero-project:betafrom
redsh4de wants to merge 7 commits intomonero-project:betafrom
Conversation
|
redsh4de
force-pushed
the
feat/beta/localize-site-links
branch
from
d1419d0 to
a6d7b10
Compare
redsh4de
force-pushed
the
feat/beta/localize-site-links
branch
from
a6d7b10 to
4f4ad69
Compare
plowsof
reviewed
Apr 28, 2026
| @@ -11,7 +11,7 @@ The Monero Project differs from many, if not most, projects in the cryptospace b | |||
|
|
|||
| As with most things in life, there are pros and cons to the aforementioned approach, with one of the greater strengths being everyone (generally) knows who's in charge of what, leading to ease of communication, and clarity for newcomers on where to direct questions or contributions of their own. A disadvantage to this method is it is a form of centralization, with the question of whether or not the project would survive should the foundation shut down for any reason. | |||
|
|
|||
| The Monero Project has chosen a different approach to contribution, namely making all of it 'external'. While there is a [Core Team](https://getmonero.org/team) in place, they are, at best, an informally affiliated group who have proven to have Monero's best interests in mind, and view their role as 'stewards' rather than CEOs or managers. This approach is powerful, in that it leads to minimal centralization, while still enabling the community to have a trusted group that can set a philosophy and direction for Monero, as well as, on a practical level, facilitate project critical transactions (Forum Funding System or FFS), mediate disputes, merge code, and be trusted with funds to be used on Project matters [(the general donation fund)](https://doante.getmonero.org). | |||
Collaborator
There was a problem hiding this comment.
old but interesting: https://www.getmonero.org/team must have got deprecated and "doante"
plowsof
reviewed
Apr 28, 2026
| First, in the beginning of the year, ASICs were detected on the network. The hashrate rose dramatically, until it was estimated that 80-90% of the network was specialized hardware, posing a significant danger to the security of the network. Monero's social covenant includes egalitarian mining, and the community pushed for [a modification to the proof-of-work algorithm](/2018/02/11/PoW-change-and-key-reuse.html) which could not run on the ASIC hardware. The PoW modification was implemented in the scheduled April 2018 protocol upgrade, and successfully managed to boot existing ASICs off the network. A second PoW modification was implemented in the scheduled protocol upgrade of October as a precaution and deterrent. | ||
|
|
||
| Second, two critical vulnerabilities were discovered in the client. The [the multiple counting bug](https://www.getmonero.org/2018/09/05/a-post-mortum-of-the-multiple-counting-bug-2018-09-05.html) would have allowed an attacker to create a transaction in which the transaction public key was included multiple times, causing the client to erroneously return that more funds were received than were sent. By utilizing this particular bug, an attacker would have been able to steal funds from organizations in the Monero ecosystem. Fortunately, the bug was confined to the accounting functionality of the wallet software, and so the protocol and coin supply were not affected. The [burning bug](https://ww.getmonero.org/2018/09/25/a-post-mortum-of-the-burning-bug.html) caused the software to not display a warning when burned outputs were received, allowing an attacker to burn funds of any recipient who allowed withdrawals following deposits. If exploited, it would have allowed a determined attacker to burn the funds of an organization's wallet, while only costing themselves transaction fees. Similarly to the multiple counting bug, this bug also did not affect the protocol, and would not have allowed an attacker to alter the supply. Both bugs were dealt with swiftly and professionally by the developers, following the [vulnerability response process](https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md). It's imperative, however, that we learn from these events and seek improvements that could significantly mitigate the impact of similar bugs in the future. | ||
| Second, two critical vulnerabilities were discovered in the client. The [the multiple counting bug](/2018/09/05/a-post-mortum-of-the-multiple-counting-bug-2018-09-05.html) would have allowed an attacker to create a transaction in which the transaction public key was included multiple times, causing the client to erroneously return that more funds were received than were sent. By utilizing this particular bug, an attacker would have been able to steal funds from organizations in the Monero ecosystem. Fortunately, the bug was confined to the accounting functionality of the wallet software, and so the protocol and coin supply were not affected. The [burning bug](https://ww.getmonero.org/2018/09/25/a-post-mortum-of-the-burning-bug.html) caused the software to not display a warning when burned outputs were received, allowing an attacker to burn funds of any recipient who allowed withdrawals following deposits. If exploited, it would have allowed a determined attacker to burn the funds of an organization's wallet, while only costing themselves transaction fees. Similarly to the multiple counting bug, this bug also did not affect the protocol, and would not have allowed an attacker to alter the supply. Both bugs were dealt with swiftly and professionally by the developers, following the [vulnerability response process](https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md). It's imperative, however, that we learn from these events and seek improvements that could significantly mitigate the impact of similar bugs in the future. |
Collaborator
There was a problem hiding this comment.
old typo + script missed "ww"
plowsof
reviewed
Apr 28, 2026
| @@ -11,8 +11,8 @@ Norwegian is the 14th language available for getmonero.org, following English, S | |||
|
|
|||
| A big thanks to ChrisAvis and the [community crowdfunding](https://ccs.getmonero.org/) that made his work possible. Translators like him allow Monero to continue to reach a much larger audience. | |||
|
|
|||
| To browse the website in Norwegian, simply select `Norsk` from the language dropdown menu on the top right, or use this direct link: [https://www.getmonero.org/nb-no/index.html](https://www.getmonero.org/nb-no/index.html) | |||
| To browse the website in Norwegian, simply select `Norsk` from the language dropdown menu on the top right, or use this direct link: [https://www.getmonero.org/nb-no/index.html](/nb-no/index.html) | |||
Collaborator
There was a problem hiding this comment.
todo: sanity check this works
plowsof
reviewed
Apr 28, 2026
| @@ -3,7 +3,7 @@ title: "Monero GUI 0.18.4.7 'Fluorine Fermi' released" | |||
| summary: Release containing bug fixes. | |||
| tags: [releases] | |||
| author: selsta | |||
| image: ./assets/2022-07-19-monero-0.18.0.0-released/fluorine-fermi.png | |||
| image: ../assets/2022-07-19-monero-0.18.0.0-released/fluorine-fermi.png | |||
Collaborator
There was a problem hiding this comment.
why is this changed to ../?
Contributor
Author
There was a problem hiding this comment.
the assets folder is now one parent back relative to the file, due to the blogs being moved into the en subfolder
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This does a few things:
adds a build-time middleware that rewrites internal links into the active locale.
This means that if for example, a blog post contains a link like /downloads, it will be converted into /ar/downloads for Arabic, etc.
content collections (blog, legal) now can be localized as well. blog files moved to a
ensubdirectory to enable that, and links changed to relative links in the files. missing translations fallback to the default locale.more aggressive caching for moneropedia, build should be faster now
updated prepare script to trim all the content collections with the limit-posts flag - blog, legal and moneropedia