If you're strictly taking about the Zero, I'd agree with you, but with the One they're entering a new market. I mean, kind of people who like to mess around with Linux and do hacker-y network-y things are also generally the kind of people who would prefer to use a keyboard, the kind who would love the extra hardware grunt to speed up tools like hashcat.
And of course, the One will be cheaper than a full-fledged x86 handheld, but if you're willing to spend a bit more, you can do so so much more - it becomes a more practical device.
From the FlipCTL description, I'm surmising the intended use case is this as a cyberdeck aka using it for external tasks, vs. hacking on it at home with your actual keyboard. For example you make a config for X task at home and perform X task on the go. I do not see any indication that this is meant to be a primary device
I'm not saying it's meant to be a primary device. I'm simply saying that just adding a keyboard adds a huge quality of life improvement, and the bigger size allows you to pack in more power whilst still being pocketable and portable.
Remember the "easy money" scene from Terminator 2[1]? Ever since I watched that as a kid, that form-factor has been my dream cyberdeck. As I grew older, I went on to own the HTC TyTN and the Nokia N900 - and loved them to bits - but I always felt constrained because of the ARM architecture and low specs. Like, you couldn't realistically brute-force any decent complexity passwords back then, and I bet the neither can the Flipper One with today's passwords.
After being bitten by the various limitations of compact ARM devices, I wanted to get my hands on one of those OQO pocket PCs that ran a full-fledged Windows XP, but never managed to try out. Also missed out on the Sony VAIO P-series. So when the first GPD Pocket came out, I jumped on to it straight away even though it was from some random unheard of company at the time. And I loved it, and haven't looked back since then. I finally had a decent, proper computer in my pocket.
So for me, a keyboard would be a bare minimum on a cyberdeck, and if it's got oodles of RAM and compute, that's even better. And the newer GPDs have also been able to play AAA games on the go, like Cyberpunk 2077, and I think that is super cool.
I did not watch Terminator 2 as it came out before I was born
I find it hard to disagree with you though - I like what the flipper team is doing but I think yeah I would be hard pressed to find a use for a device that doesnt have a keyboard when I have my phone already handy
> gh config set telemetry false
> ! warning: 'telemetry' is not a known configuration key
What's strange is if you check your `~/.config/gh/config.yml` it will put `telemetry: disabled` in there. But it will put anything in that `config.yml` lol.
> gh config set this-is-some-random-bullshit aww-shucks
> ! warning: 'this-is-some-random-bullshit' is not a known configuration key
I maintain the formatter for Dart, so a lot of my job involves maintaining the issue tracker for the formatter.
I use this feature all the time. Users get Markdown wrong, give titles to issues that don't make any sense, have typos, etc. Being able to edit issues helps me keep the issue tracker easier to understand and navigate for maintainers and users.
Every feature can be used. That doesn't mean every feature should not exist. The fact that the edit history is still visible means it's next to impossible to abuse the feature. It works fine.
Markdown is pretty tricky for new users to figure out, so quite often, users will just paste big snippets of code without formatting them, which is nearly unreadable. I'll usually edit these posts to add ```backticks``` around any code.
This is particularly useful when editing the top-level comment of a popular issue to specify the current status. Or when a peer opened a placeholder issue and you fill it up. Etc.
If you actually use GitHub as a social network of sorts, there are many reasons to do edit comments. All the edits are visible anyway. You're on Git-Hub, you can already edit everything you have write access to.
That also means that some users will be pressured to censor illegal speech no? If you live under e.g. a regime that disallows or discourages criticism, now suddenly the onus is on you to do something about those comments because you have the ability to. If you couldn't edit the comments it's not your fault.
Either way I think it's a pretty stupid feature the way it's implemented; it should show the edit more clearly or indicate that the comment has been written by multiple people (like StackOverflow does), especially if edits change more than e.g. 10% of the original comment.
I get the feeling that most people commenting here have only surface level experience with deploying k8s applications. I don't care for helm myself but it's less bad than a lot of other approaches like hand rolling manifests with tools like envsubst and sed.
Kustomize also seems like hell when a deployment reaches a certain level of complexity.
Yep, definitely something to look into when its more feature complete.
Although, not to trash my own project too much, but there are a few nice self-hosted options already that probably already does a lot more than my tool, if self-hosted is what you want, for example logdy.
reply