• 1 vote
    Update: Beta 12 (build 2816) fixed the mic in voice calls and the missing back button on the call screen. What's left: hanging up from the Quest's system call menu doesn't leave voice, and you can't scroll Settings with hand tracking.
  • 1 vote
    Update: did some digging with adb. The mic itself works fine on Quest (the Mic Test in settings picks up my voice), it only fails inside a voice call. Looks like it's caused by the CallKit / Android phone call integration the app uses for voice. Details in the VR Support thread on Fluxer Labs.
  • 1 vote
    Tested on Version 2026.10.100, Beta 9, Channel Beta, Build 767, Android 16 (arm64), Device Xiaomi 24091RPADG, Locale pt-PT, Push fcm, Flutter 3.47.7, Dart 3.13.5 Also happens on my android tablet. Attached video on h.265 (browsers dont support)
  • 2 votes
    tested on Version 2026.10.100, Beta 9, Channel Beta, Build 767, Android 16 (arm64), Device Xiaomi 24091RPADG, Locale pt-PT, Push fcm, Flutter 3.47.7, Dart 3.13.5 Issue also happens. Attached video on h265 (browser not compatible)
  • 1 vote
    Issue seems fixed on 'Version 2026.10.100, Beta 9, Channel Beta, Build 767, Android 16 (arm64), Device Xiaomi 24091RPADG, Locale pt-PT, Push fcm, Flutter 3.47.7, Dart 3.13.5'
  • 1 vote
    Issue persists on 'Version 2026.10.100, Beta 6, Channel Beta, Build 676, Android 16 (arm64), Device Xiaomi 24091RPADG, Locale pt-PT, Push fcm, Flutter 3.47.7, Dart 3.13.5'
  • 1 vote
    I don't know what solution is planned for users in Russia. But for now, you can workaround it with a vpn.
  • 1 vote
    Can you try while using a VPN? (if it works with the VPN it's probably censure\block) If you don't have one, you can try https://amnezia.org/free per example. (I've a friend in Moscow and that is what he uses.) If you are not able to connect even using VPN, then it might be other issue.
  • 2 votes
    Strongly want this. One addition alongside the onboarding guide: a rules-acceptance gate: require new members to read and accept the community rules before they get access (acceptance recorded, re-prompt on rule changes). Today we fake this with reaction-roles and manual channel permissions, which is fragile and can lock people out. Onboarding + a rules gate together would be the complete join flow. Edit: [ https://feedback.fluxer.com/p/3652/ ]
  • 1 vote
    actually I've tried in the desktop latest version and it doesn't happen.
  • 1 vote
    I understand that happens in the web browser version, not in the desktop app...Or is the desktop version kinda of a 'PWA\Web App' ?
  • 1 vote
    +1. The "sans interactions" angle makes sense to me, since there's no interactions system here to attach an EPHEMERAL flag to, so a plain flag plus a target user id feels like a more natural fit. Could be missing something on the internals though. Besides the privacy angle, these are really useful for bot feedback that shouldn't sit in the channel forever: "that command didn't work", "your upload failed", "only you can see this" confirmations, that kind of one-off reply to a single person. From a quick look, the schema side seems small (the server only allows a fixed set of message flags today), but the part I'm less sure about is the gateway having to deliver MESSAGE_CREATE only to the target user's sessions instead of the whole channel. No idea if that's the right way to do it, just what stood out to me. Either way, would love to see this land.
  • 1 vote
    +1, this would be really useful. Building on the original idea, a few things that would make it much more powerful:
    • Live online/member counts on the widget (like Discord's), not just a static badge, so it actually shows the community is active.
    • A Join button that opens an instant invite straight from the widget.
    • Please make it work on self-hosted instances too: embed served from the instance's own origin (e.g. https://<instance>/widget/<guild_id>), opt-in per guild in Server Settings, off by default for privacy.
    • A JSON endpoint alongside the iframe (e.g. /api/v1/guilds/<guild_id>/widget.json returning name, icon, presence/member counts and an instant invite) so people can build custom widgets, with CORS so external frontends can fetch it.
    Use case: I run a community on a self-hosted instance plus a separate public website, and I want a live "our community" / partner card there. Right now I fake it with a static banner and an invite link, but a live widget (counts + join) would convert far better and feel first-class. The shield + banner style options suggested here would be great too. (Hampus mentioned in Fluxer Labs that it's not on the current roadmap but could be considered if there's a discussion, so leaving this here to add support.)
  • 1 vote
    Version 2026.09.100, Beta 5, Channel Beta, Build 554, Android 13 (arm64), Device Xiaomi 21091116UG, Locale en-US, Push fcm, Flutter 3.47.5, Dart 3.13.4