> I'm switching to Android for good. (Good = at least 2 calendar years)
wow, such a commitment. Not only it's as said only one customer but it is a customer who thinks "for good" is just skipping one phone. Which means she/he usually buys phone every single year.
What a bold and committed move. It's astonishing...
Will this allow kagi to be used on the forced search widget at the bottom of the screen of pixel phones ?
Because the blog mention that Google will be forced to propose kagi in the default search engine list given 5k installs, but even with it installed I cannot set kagi as my search engine on that widget.
On the contrary if I install duckduckgo or bing, I can choose one of them to replace Google in that widget.
EDIT: android itself talks about the 5k limit for the "choice screen" during initial setup [0], but there is no mention of how the list is populated afterwards
> Will this allow kagi to be used on the forced search widget at the bottom of the screen of pixel phones ?
I understand that currently the app does not replace it, but once Kagi has more than 5000 Android installs and we submit a request to be included in choice screen, and given that privilege it would do.
I've looked at it before. Looking at the system I'm writing this comment on, my dotfiles from my repo are ~/.config/alacritty/alacritty.toml, ~/.config/nushell/{config.nu,env.nu}, ~/.tmux.conf, and ~/.gitconfig. I'm not sure if I just use far fewer dotfiles than average, and I know this is a matter of personal taste, but it's just not obvious to me why I'd want to add a tool to symlink five things once. Moreover, most of the jobs I've had give me a Macbook to work on rather than Linux, so that also would require me to either manually install `stow` or move getting homebrew set up to _before _setting_ up my dotfiles, which seems a bit backwards to me given that my my shell config is where I store any configuration for stuff like that.
I'm starting to wonder if I just have a very vanilla dotfile workflow compared to what some other people use. This would surprise me a bit, given how I tend to go overboard in custom configuration for most things, but it definitely feels like my experience isn't enough for me to understand why specialized tooling for dotfiles is needed.
I have a work mac, work linux, and home mac. I want the same terminal-based development environment on all of them, but each requires just a little bit of customization.
For example, the .gitconfig for work is different from home (e.g. my username/email). Ditto for my .ssh/config and my shell aliases.
I also use Nix to manage all my tools, and the home-manager configuration is slightly different between mac & linux due to platform support.
I've gone through a few iterations of home-built solutions, including extending homeshick[1], before discovering YADM which implemented everything I had done but better.
I started to use barrier a few days ago, and one problem arose almost immediately: the lack of support for AltGr key, which a lot of non us keyboards rely on for special characters. In my case, I can't type a # or @ using barrier, making it barely usable...
That's why since yesterday on my French AZERTY typing a ` results in "`. Thanks a lot slack! Another reason that proves and allows me to keep saying that Slack is just a bad copy of IRC that's able to display useless gifs and consumes 1 to 2GB of ram for nothing :]
I'm myself a self taught electronic hobbyist who followed the same path you did I guess (eevblog and such). I'm nowhere that good at the moment and you sir are an inspiration to what can be achieved with dedication !
Thank you for making such a project and for putting it online for the world to see. Your friends were right ;)
If you haven't already you should definitely add your project to hackaday.io (the community driven part of hackaday).
wow, such a commitment. Not only it's as said only one customer but it is a customer who thinks "for good" is just skipping one phone. Which means she/he usually buys phone every single year.
What a bold and committed move. It's astonishing...