That looks a lot like [1]. Do you have a minimal working example?

[1] https://github.com/tulir/whatsmeow/issues/287#issue-1466410628

Hello how do I process such large data in HistorySync, is it a good idea to inserting it into MongoDB?

or access data with the help of third parties such as

https://github.com/tidwall/gjson

If you already have the data you want, that means it's probably already stored in a SQLite database, which is the one suggested in the minimal working example provided in the repo's readme.

In other words, it seems to me that your question revolves around how to go about getting the data from the SQLite database into some other database of your choosing, which I'm afraid is something out of the scope of this repo.

In reply to @tulir:maunium.net
not really, just commenting

thanks for the suggestion

I couldn't find a way to find the group name. I'm able to get the unique group id but wants to know the name as well. Can anyone tell me?

Try func (*Client) GetGroupInfo. It returns (*types.GroupInfo, error), which struct contains GroupName.

Thanks @Paguiar735. It was a dumb question.

now, I add *events.HistorySync handler in my code, I do not understand these HistorySync_HistorySyncType means， in /binary/proto/def.pb.go

Unfortunately I'm not sure about the peculiarities of those arguments either.

However, whatsmeow/binary/proto/doc.go claims:

// Package proto contains the compiled protobuf structs from WhatsApp's protobuf schema.

Which can be corroborated at whatsmeow/binary/proto/extract.

In other words, that section of the project seems to be building upon the work of another repository: sigalor/whatsapp-web-reveng, which is where I believe you're more likely to find the answers you seek.

I just want to fetch the dialog list , but I do not know how to do

In reply to @wangw1:matrix.org
Can someone develop WhatsApp

In reply to @wangw1:matrix.org
Wanderer: Wanderer GitHubI would like to ask how the mautrix-whatsapp project works with whatsmeow

Collection issue for various panics that occur because users are dumb and log out immediately after logging in.

Moving to #295