i3
spotify-tui
Our great sponsors
i3 | spotify-tui | |
---|---|---|
200 | 62 | |
9,025 | 16,515 | |
1.4% | - | |
7.6 | 0.0 | |
5 days ago | 16 days ago | |
C | Rust | |
BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i3
-
Show HN: Chrome Reaper
While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:
-
Firefox 121 defaults to Wayland on Linux
> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).
Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393
It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."
It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.
But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.
The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
what machines have you used for development, and what do you prefer?
I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.
-
The future of /r/i3wm
Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.
- while in i3wm, krita dockers move downwards a bit each time they're spawned - how do I fix this?
- i3wm-like window switching for Windows
-
egui_overlay - A transparent Overlay window where you can only click the "egui parts"
for example, take i3. https://github.com/i3/i3/issues/4478
- How to start on a Linux desktop environment?
-
Machine for pentesting and general use?
For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it
spotify-tui
- Tell HN: My Favorite Tools
-
Picnic-TUI - Where Go and Groceries Create a Command-Line Feast
It was at this point I was getting a lot of joy out of writing command line applications. I had also just learnt of the existence of spotify-tui and wanted to explore more I could build such applications. So building interfaces for APIs felt like a good way to try this out.
-
Spotify's Desktop Experience Gets a Brand-New Look With Redesigned 'Your Library'and 'Now Playing' Views
If you are handy with a terminal, spotify-tui is my favorite Spotify controller I’ve ever used. No bullshit at all.
- I used an esp8266 to create a device to control Spotify
-
People who use the terminal all the time. What are you up to?
I switched to linux recently and iam loving it the speed and CLI tools that linux provides are amazing you can do anything imaginable in the terminal i use Spotify in the terminal navigate very very fast using auto-jump and its just easier than navigating all those uis and using the keyboard for everything is way faster and easier on your hand than the mouse and keyboard combination especially if you use a window manager
-
TUI for cyberdecks?
I dont know if it counts but I have used spotify tui on my pi400 a while ago link
- Show HN: Lofi, a Tiny Spotify Player
-
Spot (Native Spotify client for GNOME) seems unmaintained.
November 2019
-
Is it possible to send messages to other Kali Linux systems via the terminal?
For example, there's a couple reddit clients, YouTube viewers, Spotify clients and many many more.
-
Trying to make e ink device with Linux. Kind of lost
If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices there.
What are some alternatives?
sway - i3-compatible Wayland compositor
ncspot - Cross-platform ncurses Spotify client written in Rust, inspired by ncmpc and the likes.
awesome - awesome window manager
spotube - 🎧 Open source Spotify client that doesn't require Premium nor uses Electron! Available for both desktop & mobile!
bspwm - A tiling window manager based on binary space partitioning
nord - An arctic, north-bluish color palette.
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
dribbblish-dynamic-theme - A mod of Dribbblish theme for Spicetify with support for light/dark modes and album art based colors.
xmonad - The core of xmonad, a small but functional ICCCM-compliant tiling window manager
spotifyd - A spotify daemon
tmux - tmux source code
widevine-l3-guesser