# Other Meetings & Cohorts

## Other Cohorts

See [The Jackalopes](/MAUvhAEPRTWq1c781tF7Vw) (currently on pause)

## Misc Meetings & Notes

note: not inclusive of all meetings that happen but generally will try to keep this updated

### January 12 (wednesday) - general desktop meeting

* discussion about merge approach for base_bc branch
* decision to use cmake in c++ app
* if we structure things well, we can make the development in the different sections completly independent, which is ideal for multiple vertical teams working on the app concurrently
* decision to use google fruit https://github.com/google/fruit
* decision to use conan https://conan.io/
* decision to use clang-tidy https://clang.llvm.org/extra/clang-tidy/
* post meeting: clang-formatter
* post meeting: c++ 20

### January 3 (monday) - Meeting about waku v2 & message reliability & communities

* https://github.com/status-im/status-go/pull/2438 needs to be reviewed and merged, status-react needs a PR for this
* 3 stages defined for waku v2, we for stage 2 mobile needs to support lightpush & filter protocol, for stage 3, discovery v5 nees to be finalized but this is not a showstopper
* some mailservers have storage issues, we need to investigate & inform jakub
* status-go needs improvements to cycle buggy mailsevers, add them to a temporary black list
* the code currently used to cycle mailservers is done in nim using the task runner which can be buggy & hard to undestand, we'll move this to status-go, this will also avoid having to re-implement this in c++
* since message fetchign seems to work better now we'll look into increasing the fetching to 30 days
* defined timeline for dogfooding waku v2 + communities + message reliability, we'll have 7 dogfooding phases, each adding more people, roadmap can be found [here](https://hackmd.io/@status-desktop/B1MlJV5nd/%2F6RlqxxMdT4yLLejAAMDtCQ)
* c++ prototype will begin, starting with a simple base that can do login, using same qml, and backend same n-tier architecture as refactored desktop.
* other code identified as candidates to move to status-go: stickers, contract interactions, mailserver cycling, account generation

### September 16 (Tuesday) - Meeting about Message Syncing

* The history node does the return a number of messages it has for a certain time period so we can in theory implement a sync loading bar with a % of what is synced
* In terms of optimizations, the syncing already works from most recent to oldest
* There is something we need to improve in Desktop since it takes so long for the synced messages to show, we should be able to debug this better after introducing better tooling in the node management tab

### July 27 (Tuesday) - Meeting about Activity Center

* Some unsupported features in the Activity Center are actualy functionality not supported in status-go, in some cases in purposes
* mentions/replys will display in the activity center, but only for 1 on 1 chats, group chats & communities, not expected to work with public chats due to spam concerns
* we decided to remove the contact requests from the activity center as it causes too much issues due to lack of clarity of how it should behave under various circunstances, it seems to also not be part of the designs nor supported in mobile.

### July 8 (Thursday) - Random notes

* we should write down a list of statements that should be true or hold up, as part of the rfp
* discussions about merging the Qt update PR
* discussions about using SortFilterProxyModel

### July 7 (Wednesday) - Upcoming UI Meeting

* discussion about user list, online state
* update status Q [Roadmap & Progress](/Z07U8jgPT4GoFE_0ZnFG6w) to include links to figma
* discussion about changes to unread messages and mentions in the UI

### July 7 (Wednesday) - Random notes

* Spec for online status [here](https://github.com/status-im/status-desktop/issues/2811#issuecomment-875884301)
* For the task of increasing the default message loading from 24 hours to something longer we found that this causes message loading to be quite slow, this change also only works for new accounts, we're investigating how mobile implemented this as it was reported it was quite fast even for long periods of time, it's quite possible that this was mistakely tested on existing accounts without the new limit, thus it was not actually loading that much history.

### July 6 (Tuesday) - Random notes

- Our workflows and issue priorizations are now documented on the [Workflows](/MVIfVN0yQdOyhYJP0LLLKQ) page
- Andrei got the project to run within Qt Creator on windows https://www.youtube.com/watch?v=qQaOa0KooLs

### Jun 29 (Tuesday) - Random notes

- we still can't replicate status-desktop#2758, we asked the user for more details
- Michael keeps getting notifications that Jonathan accepted his status request, it seems this is sent everything Jonathan logins, we need to analyze whenever this is a desirable behaviour or not, and implications w.r.t to privacy. On the other hand it could be used for the online status feature. This would probably need changes in status-go.
- status-desktop#1505 now that some concurrency issues are solved, this might be possible to implement
- the zero total balance count issue in master was fixed by Jonathan in PR#2761
- random waku notes: waku v1 can have the bloom filter configured, waku v2 can support enabling or disabling relay mode, but also a) store and provide historical messages to other nodes, b) provide filtered messages to filter nodes, the subset of peers it sends messages to is also tweakable.

### June 28 (Monday) - Communities Sync

phase 2a status - desktop related
- discussion on status-react#12016 / status-desktop#2338 , we were trying to implement the fetch 24 hours OR X messages, but this feature has been changed to just be fetching X amount of time. implementing X messages in status-go is difficult, from this meeting we moved 2338 to be on hold and will address this in status-desktop#2774
- mentions have been implemented in Desktop quite a while ago, in nim, meanwhile they were implemented in status-go and we don't use that API yet, it's low priority given the mentions just work, at some point we'll update to use the status-go mentions API. Meanwhile it's possible this functionality might differ between mobile and desktop.
- edit messages done on desktop and status-go by richard, core team took over due to another releated PR, we're waiting for that work to be merged so the desktop PR can be merged
- syncing messages - Sam working on this in status-go
- search - we started the work on this with status-desktop#2771 (epic for this is status-desktop#2342)
- discussion on delete messages, we need to create a new task for this (status-desktop#2775)

phase 2b scoping - desktop related, some notes
- spellcheck - currently being done already status-desktop#2347 (Rabbits Cohort working on this)
- Channel Member list - current being worked on (early version) status-desktop#2772 (epic status-desktop#2348), early version, the 'full' feature will need a spec first
- Desktop search enchancements - currently being worked on with status-desktop#2771 (epic for this is status-desktop#2342)
- User status indicator - currently being worked on (early version) status-desktop#2772 (epic status-desktop#2348), early version, the 'full' feature will need a spec first
- Desktop opt-in auto update - Nearly done, under review status-desktop#2729
- "Option to sort channels by recently visited (instead of by Category)" - We implemented this in desktop and status-go before. status-desktop#1832 / status-desktop#1925 / status-go#2158 (note: after Speaking to John about this, it seems this was referring to *visited* not *joined*)
- Desktop Audio messages - We implemented this feature before but ran into issues (status-desktop#1947), we'll relook into this in a month or so with new team members that might have a better insight into this