You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Languages: we're planning 12, what are we missing?
#53
That list isn't final and it isn't ranked. It's where we're starting.
On timing, right now all the text lives inside the interface code. Before anyone can translate anything, it has to be pulled out into proper translation files. That's the real work and it isn't in the next release or likely the one after. Once it's done, adding a language will be quick, and that's the part the community can carry far better than we can.
2 questions.
Is your language missing from that list? Tell us and we'll look at adding it. Better to know now, while the groundwork is still being designed, than to add it on later.
Would you be willing to translate? If you'd take a language, say so here. We'll come back to you when there's something to work with.
No commitment either way. Even just telling us which language you'd use it in is useful.
One thing we'll rule out now,because it tends to come up whenever translations do: there won't be an in-app way to report or submit translation fixes. Corrections go through GitHub. That's better for it anyway, since changes get reviewed, everyone can see them, and the person who made them gets the credit.
The reason is bigger than translations though. Nothing in this app phones home, and nothing is going to. No telemetry, no usage counts, no crash reporting, no anonymous statistics. LAN Orangutan watches your network and reports to you. It doesn't report on you, to us or to anyone else.
Update checking is where that gets tested. People ask for it, and it's a fair thing to want. For now it's on you to check, and the easiest way is the Watch button at the top of this repo: choose Custom, tick Releases, and GitHub emails you when we publish one. If you installed through Homebrew or Scoop, brew upgrade and scoop update already handle it, and Docker on :latest picks it up on the next pull.
Which makes the point better than we could. All of those tell you about a new version without us learning anything about you, because that's the package manager's job and not ours. Whatever we build in eventually has to clear the same bar.
The numbers would be nice to have. We're grateful for everyone running this and it would be good to know how many that is. But anything we built to find out would be something that watches you, and once that exists it can be misused or leaked, etc.
So to be plain about it: we will not build telemetry into LAN Orangutan. Not anonymized, not opt-in, not "just the version number". Not in this release, not in a later one, and not if the project gets big enough that it starts to look tempting. If you ever catch this app making a connection you didn't ask for, that's a bug, and we want to hear about it asap.
To wrap up, if there's a language you want that isn't in those 12, say so here and we'll look at it. Also, if you've got something else entirely, a feature, an annoyance, an idea, we want that too. Open an issue or start a discussion.
The one thing worth knowing before you do: LAN Orangutan isn't trying to be the most powerful scanner out there and that's the point. It's built to be the simplest and fastest one to reach for. There are excellent, deeply capable tools in this space and they're the right choice when you need everything they offer. This is for the other times, when you just want to see your network now. So if an idea would add real complexity or setup for the user, it's probably not a fit. But we’d still rather hear about it.
The rule we hold ourselves to is that there's no manual and there isn't going to be one. If a feature needs explaining, that's a bug then and not a feature, and we change the tool instead of writing the explanation. That holds no matter how far this goes or how advanced it gets. Please keep holding us to it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Thanks to @maurognx, who offered to help with a Portuguese translation this week. Good prompt to put the plan out in the open.
Translations are coming. We're mirroring what we already do in LAN Sheriff: a language dropdown in the header, with 12 to start.
English, Arabic, Bengali, Chinese, French, German, Hebrew, Hindi, Japanese, Portuguese, Russian and Spanish.
That list isn't final and it isn't ranked. It's where we're starting.
On timing, right now all the text lives inside the interface code. Before anyone can translate anything, it has to be pulled out into proper translation files. That's the real work and it isn't in the next release or likely the one after. Once it's done, adding a language will be quick, and that's the part the community can carry far better than we can.
2 questions.
Is your language missing from that list? Tell us and we'll look at adding it. Better to know now, while the groundwork is still being designed, than to add it on later.
Would you be willing to translate? If you'd take a language, say so here. We'll come back to you when there's something to work with.
No commitment either way. Even just telling us which language you'd use it in is useful.
One thing we'll rule out now,because it tends to come up whenever translations do: there won't be an in-app way to report or submit translation fixes. Corrections go through GitHub. That's better for it anyway, since changes get reviewed, everyone can see them, and the person who made them gets the credit.
The reason is bigger than translations though. Nothing in this app phones home, and nothing is going to. No telemetry, no usage counts, no crash reporting, no anonymous statistics. LAN Orangutan watches your network and reports to you. It doesn't report on you, to us or to anyone else.
Update checking is where that gets tested. People ask for it, and it's a fair thing to want. For now it's on you to check, and the easiest way is the Watch button at the top of this repo: choose Custom, tick Releases, and GitHub emails you when we publish one. If you installed through Homebrew or Scoop,
brew upgradeandscoop updatealready handle it, and Docker on:latestpicks it up on the next pull.Which makes the point better than we could. All of those tell you about a new version without us learning anything about you, because that's the package manager's job and not ours. Whatever we build in eventually has to clear the same bar.
The numbers would be nice to have. We're grateful for everyone running this and it would be good to know how many that is. But anything we built to find out would be something that watches you, and once that exists it can be misused or leaked, etc.
So to be plain about it: we will not build telemetry into LAN Orangutan. Not anonymized, not opt-in, not "just the version number". Not in this release, not in a later one, and not if the project gets big enough that it starts to look tempting. If you ever catch this app making a connection you didn't ask for, that's a bug, and we want to hear about it asap.
To wrap up, if there's a language you want that isn't in those 12, say so here and we'll look at it. Also, if you've got something else entirely, a feature, an annoyance, an idea, we want that too. Open an issue or start a discussion.
The one thing worth knowing before you do: LAN Orangutan isn't trying to be the most powerful scanner out there and that's the point. It's built to be the simplest and fastest one to reach for. There are excellent, deeply capable tools in this space and they're the right choice when you need everything they offer. This is for the other times, when you just want to see your network now. So if an idea would add real complexity or setup for the user, it's probably not a fit. But we’d still rather hear about it.
The rule we hold ourselves to is that there's no manual and there isn't going to be one. If a feature needs explaining, that's a bug then and not a feature, and we change the tool instead of writing the explanation. That holds no matter how far this goes or how advanced it gets. Please keep holding us to it.
All reactions