-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Run in background on Linux #486
Comments
I second this feature request! It is not just useful for phones but also for desktop users as do not miss new messages so easily. Possible options could be a tray icon or using the background portal to integrate nicely with desktops like gnome shell. |
Here's a workaround for minimising to the tray in the meantime:
|
second using background portal |
This issue is stale because it has been open for 120 days with no activity. |
I would also like to run in tray and preferably start there with command line flag so I could integrate it to my sway config.d/ |
What would be needed to implement this? |
@tionis This package look like it could work good: https://pub.dev/packages/system_tray |
Hi, is there some information about this? I also want to see a tray icon on Linux desktop. |
Any progress? |
Nudging this a bit so it won't get "stale". I'd love to have this as well! |
+1 🙂 |
The information is that this is a feature request.
Obviously... no.
Please use the emoji reactions instead of causing everyone trying to follow this thread — in a meaningful way — a new notification, only to find out it is some saying "Yeah, me too" or something similar. More noise leads to these discussions becoming less useful and you don't get a feature very quickly if you spam people with completely unncessary notifications. If anything, it can annoy and discourage from looking at the issues. |
I'm very sorry! I'm rather new to GitHub so I didn't know it was rude to do so. A beginner question: I noticed that this repository uses a bot that marks an issue as "stale" and after a duration of inactivity, seems to close the issue / request, forever forgotten. I was afraid of that happening, so I felt like I had to "bump". Does reacting with emoji prevent that from happening? I usually avoid "bumping" in most other projects because I know the maintainers and contributors can come back to a feature request whenever they want because it's still open. Again, I'm sorry about my earlier reply, and also for this very reply that is very irrelevant to the project as well. Just trying to understand the process around here. |
Feature Description
Allow to run Fluffychat in background on Linux. This way it can also be used on Linux Phones.
Rationale
Better intergration with Linux phones.
Mockup
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: