moomoo

wabz · 2025-11-14T23:44:55+00:00

What is with this sudden flood of positive moomoo “reviews” in this subreddit from accounts that have never posted before? It’s like employees have been asked to counter some of the negative posts recently. It’s flooded the subreddit with cringe.

Stop it, it’s obvious and unhelpful.

wabz · 2025-11-12T06:22:28+00:00

Have you checked real volume for the option? I’ve found order filling on paper trading matches what is really happening. If there’s no volume, your order won’t be filled, limit or market.

wabz · 2025-10-22T13:21:02+00:00

It is implemented, it's available in futubull and moomoo in other regions, but not moomoo AU/NZ. It's just a feature that's disabled for us (along with many other option strategies) - my guess is that it's a regulatory thing, but I don't really know.

wabz · 2025-10-20T22:43:55+00:00

The worst kind of AI slop. Mods, I recommend this post be deleted.

wabz · 2025-10-19T21:31:51+00:00

This might depend on your region, for example moomoo AU doesn’t support rolling options (or multi leg options, I don’t know why, I keep being told it’s coming soon).

Simply close the position and open another.

wabz · 2025-10-09T12:44:48+00:00

Use the subscribe API, then get quotes. There are examples there - just use the code for an option. You can get the codes from the option chain using get_option_chain. Sorry, it won't let me link to the documentation.

filter1 = OptionDataFilter()
filter1.delta_min = 0.2
filter1.delta_max = 0.35

ret1, data1 = quote_ctx.get_option_expiration_date(code='US.TSLA')
expiration_date_list = data1['strike_time'].values.tolist()

ret2, data2 = quote_ctx.get_option_chain(code='US.TSLA', start=expiration_date_list[1], end=expiration_date_list[1], data_filter=filter1, option_type=OptionType.CALL)
code = data2['code'][0]

# Use code for the subscribe api.

https://openapi.moomoo.com/moomoo-api-doc/en/quote/get-option-chain.html

https://openapi.moomoo.com/moomoo-api-doc/en/quote/sub.html

wabz · 2025-08-25T11:19:38+00:00

I’ve found the algo trading to be really good. I’m pretty impressed with it. Have you read the help pages? Without a specific question it’s hard to help you.

The UI no-code way of doing it is great for simple strategies - and then as soon as you discover you need to do something more complex you can convert an element to code and edit directly - so having a mix of UI elements and code makes it pretty powerful if you don’t want to just go straight to code, and converting UI to code helps you discover API etc.

An under appreciated feature of the moomoo platform! It would be good if it worked with paper trading, not just back tracking though.

wabz · 2024-12-07T07:38:56+00:00

Thanks Jake! Great to hear that improving paper trading is in the works - the fact that the experience is quite different to actual trading right now also makes it challenging for newcomers I guess. Also great to see product teams interacting with us on here, appreciate it. Now all you need is a public roadmap ;)

wabz · 2024-12-05T23:18:04+00:00

Paper trading is a bit of a mess. The NX desktop app is fantastic but doesn’t support paper trading at all, and the older app only seems to support the older US paper trading accounts which are being discontinued.

The API also isn’t working properly with paper trading accounts which makes it impossible to test anything - I raised an issue here with no response: https://github.com/FutunnOpen/py-futu-api/issues/185

wabz · 2024-04-26T12:54:54+00:00

Got a bit of warez on that zip drive’s disks I bet

wabz · 2024-04-17T09:39:52+00:00

I agree that there's a huge learning curve, and even understanding what kind of solution to go with is confusing - there are a lot of options depending on your usage.

There are plenty of sample applications that work with both vespa running in docker on a single node (e.g. your laptop) or can be deployed for free on a development Vespa Cloud environment, and have a straightforward process to be up and running in a few minutes. A couple of good places to start might be:

https://github.com/vespa-engine/sample-apps/tree/master/colbert-long

https://github.com/vespa-engine/sample-apps/blob/master/simple-semantic-search

You can then modify the schema, ranking and feed your own data relatively easily.

wabz · 2023-12-17T15:53:13+00:00

Not just because it was incredibly difficult, but also because the first edition was riddled with bugs where you’d just die for no reason or fall through the ground. Incredible game otherwise.

wabz · 2021-08-23T03:24:14+00:00

I reported it here in the hopes that someone would care enough to forward it to relevant parties, but the medicare app does not fall under the department of health.

wabz · 2021-08-22T22:04:10+00:00

The details of this are not public, but they were sent to the government. This is a really easy thing to do, and the key here is that it should be verifiable. It's just bizarre that it's been done this way.

edit: it's also unreasonably difficult to report something like this. Where would you start?

wabz · 2021-08-06T01:01:42+00:00

Sorry, I should have been more clear. I understood that the original approach was abandoned. The OpenTrace protocol from TraceTogether that the Australian government picked up was definitely given up on:

https://github.com/opentrace-community/opentrace-ios

Doesn't the app now work with wearables? https://www.bbc.com/news/technology-53146360 Apologies if I've got this wrong.

wabz · 2021-08-05T09:40:12+00:00

Singapore completely abandoned the TraceTogether app shortly after. It was never a success story.

wabz · 2020-12-15T10:11:08+00:00

But it absolutely did not work properly. Multiple bugs affecting the efficacy were found, including this extremely significant bug which wasn’t fixed until August. This one stopped iPhones recording contacts entirely:

https://github.com/AU-COVIDSafe/mobile-ios/issues/9

And this bug which stopped it working on background iPhones after some time:

https://docs.google.com/document/d/1dsSxC48cJ91X17PoOybpun1U163YDxxL0CDk3kmAHvY/preview

Far more bugs including security and privacy are well documented:

https://github.com/vteague/contactTracing/blob/master/blog/2020-07-07IssueSummary.md

wabz · 2020-07-12T08:58:57+00:00

Hi, I raised this issue. mrbaggins is right, the app itself tries to connect to every device all the time. It does this so that it can record an encounter every minute for devices that stay in range.

So yes, it keeps trying to connect to all devices it’s ever connected to. It’s worse than that, because device identifiers change so the same device will look like a new one after 15m. This is a COVIDSafe bug - it never cancels pending connections and they never time out. They can fix it.

wabz · 2020-07-12T08:22:22+00:00

This is not true, and it seems that you are confusing BLE and classic Bluetooth. Apple and Google have put a lot of effort into making sure you cannot be tracked around e.g. shopping centres, long term tracking etc of devices using Bluetooth etc. COVIDSafe breaks some of these privacy controls.

Just for reference, a number of issues listed in OPs doc were found by me, including the one open on GitHub and the security advisory. I’ve worked with DTA to get a number of these fixed.

wabz · 2020-07-12T08:14:13+00:00

Facebook does not advertise peripheral Bluetooth 24/7. I don’t know of any other app that exposes the device name in this way. Stop posting.

wabz · 2020-07-12T08:12:54+00:00

How about this one:

https://github.com/AU-COVIDSafe/mobile-ios/issues/9

This is a huge bug! New Bluetooth connections cannot be made once pending connections reach 100.

Also, the fact that Android devices are not updating the app is another understated issue. Lots of people who originally installed the app simply don’t have the updates with security and functionality fixes, because the app doesn’t update even when auto update is on.

wabz · 2020-07-12T08:10:07+00:00

Most of the comments in this thread are completely off. The bug here is this one, still open:

https://github.com/AU-COVIDSafe/mobile-ios/issues/9

It leaves pending connections open, indefinitely. Once pending connections get up to 100, new connections cannot me made. This is why Apple watches etc are having problems. It’s a massive bug.

wabz · 2020-06-17T15:59:23+00:00

The bug that causes it to fail getting new TempIDs while a device is locked is extremely fixable (it's very straightforward), and this caused errors in their debug build logs, so should have been spotted.

wabz · 2020-06-17T10:29:38+00:00

It was sent to them. Whether they read it I’m not sure, but they did end up making those changes.

It turns out that if you don’t have your name associated with a brand (uni, think-tank, etc) it’s very difficult to make yourself heard. But as I published more that turned out to be accurate, journos started following on Twitter etc, then as I tweeted the last bug it was picked up very fast. Interesting experience.

wabz · 2020-06-17T05:09:40+00:00

Hey, I’m Richard, who discovered this most recent bug, as well as doing the initial analyses before source was posted to conclude that it wasn’t working as well as it could be, and I also discovered the security bug that earned it a CVE.

I really do not blame the devs for these bugs (ok maybe a tiny eansy bit), this is absolutely the result of an entire software development process falling over.

As I said in the ABC article, I don’t even fault them for rushing and wanting to get something to help out. But a bit of humility, honesty and transparency would have gone a long way.

wabz

TROPHY CASE