Moodle
How Geek connects to Moodle.
Written for students and for school IT. In short: you sign in on your school’s own pages, Geek reads a small set of things, and your Moodle token and school data are stored only on your laptop. It works with any school whose Moodle allows the official Moodle app. Geek is independent and not affiliated with or endorsed by Moodle, Duo, Crowdmark or any school.
Your laptop
Geek’s sign-in window
Shows your school’s real pages. You can see which site you’re on at every step.
Your operating system’s keychain
Encrypts your Moodle token on your laptop. Geek only uses it to read.
Your school’s sign-in page
You type your password there and pass any two-step check, the same as on the web.
Your school’s Moodle
Issues the token through Moodle’s official mobile sign-in, back to Geek’s window.
Geek’s servers
Not involved. Geek runs no server your school data passes through, and nothing reaches Geek.
Signing in
You give Geek your school’s Moodle address, such as moodle.yourschool.edu. Geek first asks that site, without signing in, whether it allows app sign-in.
Then it signs in through the Moodle app’s own mobile service, the same official sign-in the Moodle app uses. Your school’s sign-in page opens inside Geek’s own window, on your laptop. When you finish, Moodle sends the token back as a sign-in link (the Moodle app’s moodlemobile:// link, which is Moodle’s default), and Geek catches that link inside its own window, so no other app gets it.
You type your password into your school’s own page and pass any two-step check there. Geek never asks for your password, doesn’t read the form, doesn’t inject anything into the page, and never stores your password.
Geek identifies itself honestly: its user agent says Geek and its version. It never pretends to be the Moodle app.
Where the token lives
When you finish signing in, Moodle hands a token back to Geek’s window. Geek checks it, then stores it encrypted by your operating system: the Keychain on a Mac, Windows’ own data protection on a PC.
The token never leaves your laptop. Geek has no server that receives it, and nothing on Geek’s side ever contacts your school. All Moodle traffic runs from your laptop, on your own connection.
What Geek reads
Geek uses the token to read only these. Every write function, such as submitting or posting, is refused in code before any request is sent:
- CoursesThe courses you’re enrolled in this term
- Course contentsThe sections, activities, pages, links and file names in each course, fetched again only when something changed
- Calendar and due datesTimeline events from a week ago to a month ahead
- Assignments and submission statusNot started, draft or submitted, for items due soon
- GradesCourse totals and graded items from the gradebook, including marks other tools put there
- AnnouncementsThe latest posts in each course’s announcements forum
- NotificationsYour Moodle notifications, read only
- Quiz times onlyWhen each quiz opens and closes, and whether you have an attempt in progress. Never the questions.
- Your account basicsYour Moodle user ID, the site’s version and which functions it allows, checked when you connect and once a day
- Calendar linkYour personal calendar export link, fetched once as a backup in case sign-in stops working
A function runs only if it is on Geek’s built-in read-only list and your school’s Moodle also offers it to mobile apps. Anything else is refused in code.
Geek’s built-in browser
Geek also has a built-in browser, the Computer, that opens your Moodle pages with the same sign-in. It runs on your laptop, inside Geek, like the sign-in window.
- A bot can read a Moodle page open there and take a screenshot of it.
- It can click, type or scroll only with your approval, given on a card for that one action or for that kind of action. Typing never gets “Always”. You can take over at any moment.
- Opening any other site, even another of your school’s own sites, asks you first. Sign-in pages are yours alone.
- The bot won’t type into password fields, it can’t open quiz attempt pages, and any form submission or background write it tries without your approval is cancelled.
How often
- At most one request per second, one sync at a time, with longer waits if Moodle is busy.
- A sync about every 30 minutes, with a little random spread, plus when you open Geek or ask for one.
- Files only when you open them. There is no background crawl of course files.
What Geek can’t do
Never
- Start, save or submit a quiz attempt
- Read your password or the sign-in form
- Type into password fields
- Pretend to be the Moodle app
- Crawl course files in the background
- Call a Moodle function that changes anything
Only with your approval
Clicks, typing, scrolling and choosing in the Computer. Each waits for an approval card (Allow once, Always allow for that kind of action, or Deny) unless an Always rule you set covers it. Typing never gets Always, and you can revoke any rule in Settings, Approvals.
Disconnecting
Disconnect in Geek’s settings deletes the token from your laptop and clears the sign-in window’s data.
The same token may also be used by the Moodle app on your phone, so Geek doesn’t revoke it on your school’s side by itself. A separate link opens your Moodle’s own page for signing out of the mobile apps, so you can do that yourself.
Crowdmark and other tools
Geek shows marks from tools like Crowdmark only if they appear in your Moodle gradebook. It never calls Crowdmark’s API or automates it. If you open a Crowdmark link in the Computer, only you can use that page; Geek’s agent tools are off there.
If sign-in doesn’t work
Some schools turn off Moodle app access, or sign in a way Geek can’t use yet. Then paste your Moodle calendar link instead: your due dates still show up on Home. It is stored encrypted on your laptop like the token, and fetched only from your laptop.
For school IT
- Sign-in. Geek uses the Moodle app’s own mobile service (
moodle_mobile_app, through your site’sadmin/tool/mobile/launch.php) in a window inside Geek. Your site returns the token as amoodlemobile://link, Moodle’s default (orgeekapp://, the scheme Geek asks for, if your site doesn’t force one), and Geek catches it inside that window. Geek registers neither link with the operating system, so no other app on the laptop receives the token. - Passwords. Geek never asks for, reads or stores a student’s password. Students type it into your own sign-in page, and any two-step check happens there too.
- User agent. Every request says it is Geek: the user agent is Electron’s default with Geek/ and the version at the end. Geek never sends the Moodle app’s user agent.
- Switches. Geek needs the same setting as the Moodle app: mobile web services on. If they are off, Geek can’t sign in, and students can use their calendar link instead. What Geek shows depends on which functions your site offers to the mobile service.
- Traffic. The token goes in the request body, never in a URL. Geek keeps to the read-only list and the pace above, and there is no Geek server in between: each student’s laptop talks to your Moodle directly.
Questions go to the founder. The quickest way is on GitHub: github.com/nigelose10 (opens in a new tab).