IDA is analysing the input file...
You may start to explore the input file right now.
PySide has not been widely tested on Python >= 3.14; IDA cannot guarantee that it will function as expected.
 INFO: provider_type column already exists, skipping migration
 DEBUG: reasoning_effort column already exists, skipping migration
 INFO: LiteLLM columns already exist, skipping migration
 DEBUG: timeout column already exists, skipping migration
 DEBUG: command column already exists on mcp_providers
 DEBUG: args column already exists on mcp_providers
 DEBUG: env column already exists on mcp_providers
 DEBUG: cwd column already exists on mcp_providers
 INFO: Successfully created oauth_credentials table
 INFO: Provider type name migration: no providers needed updating
 INFO: bypass_proxy column already exists, skipping migration
 ERROR: Failed to init Explain tab: cannot import name 'QObject' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init Query tab: cannot import name 'QDateTime' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init Actions tab: cannot import name 'QObject' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init Semantic Graph tab: cannot import name 'QPointF' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init SymGraph tab: cannot import name 'QObject' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init RAG tab: cannot import name 'QObject' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 ERROR: Failed to init Settings tab: cannot import name 'QObject' from 'src.qt_compat' (C:\Users\Administrator\AppData\Roaming\Hex-Rays\IDA Pro\plugins\IDAssist\src\qt_compat.py)
 DEBUG: Resolved binary hash from stored IDB input SHA-256
 INFO: Binary context initialized (hash: cf7a6211902596c9...)
 INFO: IDAssist panel created with all tabs

Why These Changes Matter

Meshtastic has always been about open communication and the free exchange of data across a wide network of nodes. The ability to share GPS locations and other telemetry data via MQTT servers has been a cornerstone of the system’s functionality. However, with the new restrictions in place, the default MQTT server is no longer as versatile as it once was.

Under the zero-hop policy, the system’s capacity to relay information across multiple nodes has been severely limited. This, combined with the decision to restrict access to telemetry data, has made the default server less effective for users who previously depended on it for essential data. While it was initially believed that these restrictions would prevent users from subscribing to the general msh/# channel, which covers all data, it turns out that users can still subscribe to specific channels such as msh/DE/2/e/LongFast/ or msh/CZ/2/map/. Although this does limit the range of data available, it still allows for targeted listening.

Additionally, it is important to note that, as of now, the transmission of neighbour information or other data beyond a user's own data is no longer available. This change prevents users from conducting terrain analysis and utilizing telemetry for broader network management.

The Solution: Transition to Private Servers

Given these changes, it’s clear that the community must adapt by switching to private MQTT servers. By transitioning to private servers, users can regain control over their data and maintain the functionality that drew them to Meshtastic in the first place. This move also empowers the community to preserve the flexibility and openness that are core to the Meshtastic philosophy.

Final Thoughts

While the decisions by the administrators may have been made with the best intentions, the reality is that they have limited the utility of the default server. For those who value the ability to freely share and access telemetry data, switching to a private MQTT server is not just an option—it’s a necessity. Even though the ability to listen to broad channels has been restricted, the option to subscribe to specific channels still offers some functionality. As the community adapts to these changes, it’s important to stay informed and proactive in finding solutions that meet our collective needs.

Meshtastic alternative MQTT servers:

• Address: mqtt.meshnet.nl
• Username: boreft
• Password: meshboreft
• Website: meshnet.nl/nederland-map.html
• Primary target: Netherlands

• Address: mqtt.meshtastic.liamcottle.net
• Username: uplink
• Password: uplink
• Website: meshtastic.liamcottle.net
• Primary target: Global

• Address: loranet.pl
• Username: no username
• Password: no password
• Website: loranet.pl
• Primary target: Poland

1. I have cuda 12.1 installed
2. "nvcc --version" still returns 11.5 version
3. "which nvcc" command points to /usr/bin/nvcc
4. python -c "import torch; print(torch.version.cuda)" returns 12.1