• 3 votes
    To add to this, I'd like to have theme library sync ^^
  • 1 vote
    Can reproduce Version 2026.09.100, Beta 3, Channel Beta, Build 2530, Android 17 (arm64), Device Google Pixel 7a, Locale de-DE, Push fcm, Flutter 3.47.5, Dart 3.13.4
  • 1 vote
    Can no longer reproduce works as expected Version 1.0.0, Beta 68, Channel Beta, Build 2489, Android 17 (arm64), Device Google Pixel 7a, Locale de-DE, Push fcm, Flutter 3.47.5, Dart 3.13.4
  • 1 vote
    I went ahead and searched for a lookup table, for Katakana, online.
    フラクサー
    This seems to be "Fluxer".
  • 1 vote
    Can reproduce CR: Version 1.0.0, Beta 38, Channel Beta, Build 2199, Android 17 (arm64), Device Google Pixel 7a, Locale de-DE, Push fcm, Flutter 3.44.7, Dart 3.12.2
  • 1 vote
    Can reproduce CR: Version 1.0.0, Beta 38, Channel Beta, Build 2199, Android 17 (arm64), Device Google Pixel 7a, Locale de-DE, Push fcm, Flutter 3.44.7, Dart 3.12.2
  • 1 vote
    Can reproduce CR: Version 1.0.0, Beta 38, Channel Beta, Build 2199, Android 17 (arm64), Device Google Pixel 7a, Locale de-DE, Push fcm, Flutter 3.44.7, Dart 3.12.2
  • 1 vote
    I can see this being useful for message replies. Make them show the message at the time of the reply. (Maybe make it so the server returns only a slice of the original message, in case the replied message contains sensitive info that would otherwise not be preserved by an edit history.)
  • 1 vote
    Have you ran git grep fluxer-users in the repo? I found the Cargo.toml immediately. It's here: /fluxer_users/Cargo.toml. And judging by /fluxer_users/Dockerfile, /fluxer_users should be the source of the fluxer-users binary.
  • 1 vote
    cannot replicate shortcodes are sent as shortcodes, unicode emoji are sent as unicode emoji
  • 1 vote
    I believe you are misunderstanding what the string in parentheses represents. Audio In/Out is handled by a dedicated sound chip, in your (and my) case that is a sound chip on the motherboard. The "MAC address" you mentioned is a typical PCI ID you'd see on any other PC. Your sound chip has a PCI ID assigned to it. The IDs you see here are comprised of a Vendor ID and a Device ID, separated by a colon. A sound chip may have multiple audio inputs and outputs, but they all belong to the same sound chip, all inheriting the same PCI ID. P.S.: MAC addresses are a networking thing. They live in OSI/ISO layer 2, aka the Data Link Layer. If you want to look into currently assigned PCI IDs, click here.