<joepie91>
jasongrossman: they've been getting raked over the coals in a few countries now over shitty password (manager) policies
<joepie91>
so, not too surprising to me :P
<joepie91>
they're also the only bank in NL, afaik, to continue using SMS auth codes instead of a card+PIN based ebanking auth mechanism
drakonis has joined #nixos-chat
* emily
has mostly heard good things about bunq in the context of .nl banks
lassulus_ has joined #nixos-chat
lassulus has quit [Ping timeout: 246 seconds]
lassulus_ is now known as lassulus
Ralith has quit [Ping timeout: 252 seconds]
sphalerit has quit [Ping timeout: 252 seconds]
<sir_guy_carleton>
joepie91: only one major bank here even has 2fa for online banking, iirc
jasongrossman has quit [Ping timeout: 244 seconds]
sphalerit has joined #nixos-chat
pie__ has joined #nixos-chat
Ralith has joined #nixos-chat
pie__ has quit [Remote host closed the connection]
pie__ has joined #nixos-chat
pie_ has quit [Ping timeout: 252 seconds]
Ralith has quit [Ping timeout: 250 seconds]
Ralith has joined #nixos-chat
Synthetica has quit [Quit: Connection closed for inactivity]
drakonis has quit [Ping timeout: 260 seconds]
pie__ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-chat
sir_guy_carleton has quit [Ping timeout: 252 seconds]
jackdk has quit [Ping timeout: 246 seconds]
<sphalerite>
joepie91: I've had that 2-emails thing before too, at least twice.
<srhb>
We have this weird half-shitty-half-OK national 2fa solution in DK that I think all e-banking solutions are required to use.
<srhb>
It's also an identity provider at the same time, I think that may be why it's required in fact. 2fa is just incidental.
<srhb>
(Ironically its name translates to "easy ID" -- and it's everything but.)
__monty__ has joined #nixos-chat
pie__ has joined #nixos-chat
<sphalerite>
srhb: I will haunt all you games.
<srhb>
:3
<srhb>
I don't mind
<srhb>
At least you had the sanity to pick a memorable name.
<srhb>
No one can ever remember my nick :P
<etu>
srhb: We save something like that it sounds like, it's called Bank-ID here. Used for a load of stuff.
<srhb>
etu: Yeah.. It's quite generic here, used for taxes and any kind of government interaction as well..
<srhb>
It has its flaws, but a standard is nice.
Taneb has joined #nixos-chat
sphalerit has quit [Ping timeout: 276 seconds]
sphalerit has joined #nixos-chat
<etu>
srhb: Yeah, same here. Too bad it's not open though.
<etu>
srhb: Closed source non-verified :(
<sphalerite>
srhb: I can :p
<sphalerite>
(remember your nick)
<sphalerite>
seeing your github profile and where the nick comes from helps I guess
<srhb>
Ah, yeah, I guess. ^_^
<sphalerite>
also people have lots of difficulty with mine, I've seen spharelite quite a few times
<srhb>
Sounds cute :P
<ekleog>
people who don't know to sph<tab> :p
<sphalerite>
ekleog: yep
<sphalerite>
oh also spacefrogg. Because some people's tab completion apparently isn't activity-aware
<srhb>
sphalerite: How do I get that, please? :P
<srhb>
sphalerite: Mine insists on completing sphalerit before sphalerite
<sphalerite>
idk, weechat seems to do it by default
<sphalerite>
but it doesn't matter whether you put sphalerit or sphalerite, I get highlights on either :)
<srhb>
sphalerite: Apparently not, I use weechat.
<srhb>
sphalerite: The real annoyance is that since there are two completions for sph, it doesnt autocomplete the ": " at the end.
<srhb>
sphalerite: So I have to either sph<tab>e<tab> or sph<tab>:<tab>
<sphalerite>
what about sph<tab><tab>?
<srhb>
sphalerite: The extra tab does nothing. Still two completions. guess I should look through my config..
<sphalerite>
I don't think I configured anything special for it to work
<srhb>
24 .conf files. X_X
<sphalerite>
#configisstateobviously
<sphalerite>
that's what I don't like about weechat
<srhb>
I really dislike weechat. I just dislike other clients more.
<ekleog>
^
<ekleog>
esp. handling of the lower-right of the bar where I type
<srhb>
Back when I had a working Emacs, erc was my favourite.
<ekleog>
there's always this one char that sometimes displays and sometimes doesn't and it's in weechat's memory anyway
<elvishjerricco>
I've really liked IRCCloud. I hate that I'm paying for a proprietary service. But it's literally the only IRC client I've found that's legitimately pleasant to use.
<__monty__>
Head good things about circe. Irssi serves me fine though.
<sphalerite>
ekleog: oh? I've never had that problem except when accessing it via mosh
<srhb>
circe is okay too.
<sphalerite>
ekleog: I think it's a mosh bug
<ekleog>
sphalerite: I first thought that was a mosh issue, but had it too with only ssh tmux, and recently had it too in local direct
<__monty__>
srhb: You prefer erc? Someone told me circe was more powerful.
<sphalerite>
ekleog: huh, weird
<srhb>
__monty__: That might be true, but erc was extremely simple to customize in elisp in my experience.
<ekleog>
(like, currently typing from a local weechat plugged to an IRC relay, that has happened today)
<ekleog>
but yeah, I started noticing the problem only recently, after switching to mosh most of the time
<sphalerite>
if in doubt, spam Ctrl-L :D
<ekleog>
yeah, didn't work while under mosh, need to try again next time it happens out of mosh
* ekleog
would like a sensible chat client so much
<ekleog>
but rust doesn't have good TUI libraries currently afaik, so now is not the good time to start writing one (a)
<__monty__>
ekleog: Have you checked out glirc? It's folding is an original approach to ignores.
<ekleog>
hmm… the Greater Long Island Running Club ? :D
<ekleog>
(I personally use weechat's /filter to ignore, sounds similar to folding)
* ekleog
can't find anything by the name of glirc
<Taneb>
ekleog: haskellPackages.glirc, invoke as glirc2
<ekleog>
hmm so maybe you can answer my questions: first, does it support folding netsplits into a single line?
<ekleog>
second, does it handle well being on ~200 rooms on ~10 different servers? (I read there's an IRCPASSWORD environment variable, doesn't make me hopeful, but…?)
<Taneb>
It folds consecutive joins and parts onto a single line
<Taneb>
I'm not in that many rooms so I can't tell you
<ekleog>
third and maybe most important, does it have the equivalent of go.py, which allows to fuzzy-match on buffer name to find a room to jump?
<ekleog>
(equivalent of /grep support would be nice too, but anyway recently my weechat logs are just too heavy and I just resort to detaching from the tmux and ripgrep'ing through the logs)
<Taneb>
It has /grep, as it happens
<ekleog>
oh and actually *the* most important question: what's the format of log files?
<Taneb>
I don't know about go.py or log files, I'm afraid
<ekleog>
oh 'k, well, thanks already :)
<Taneb>
:)
<ekleog>
hmm looks like there's a log-dir config option, can I bother you to tell me if you can find interesting stuff in there? :°
<Taneb>
I'm using the default config which I don't think saves logs?
<ekleog>
oh
<ekleog>
well, then nvm, I'll just open two issues, one to ask for the equivalent of go.py (can't find any mention of anything similar to it in the wiki) and one to ask for log format :)
* ekleog
increased by half the number of open issues of glirc :°
Jackneill has quit [Read error: Connection reset by peer]
Jackneill has joined #nixos-chat
bitmapper has joined #nixos-chat
bitmapper has quit [Read error: Connection reset by peer]
jasongrossman has joined #nixos-chat
Synthetica has joined #nixos-chat
Jackneill has quit [Quit: Leaving]
Jackneill has joined #nixos-chat
jD91mZM2 has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
Jackneill has quit [Client Quit]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
Jackneill has quit [Remote host closed the connection]
Jackneill has joined #nixos-chat
jasongrossman has quit [Ping timeout: 250 seconds]
drakonis has joined #nixos-chat
drakonis_ has quit [Ping timeout: 244 seconds]
drakonis has quit [Ping timeout: 252 seconds]
drakonis has joined #nixos-chat
drakonis has quit [Ping timeout: 245 seconds]
drakonis has joined #nixos-chat
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-chat
drakonis_ has joined #nixos-chat
drakonis has quit [Ping timeout: 250 seconds]
lassulus has quit [Ping timeout: 252 seconds]
lassulus has joined #nixos-chat
bitmapper has joined #nixos-chat
drakonis_ has quit [Ping timeout: 252 seconds]
drakonis_ has joined #nixos-chat
bitmapper has quit [Ping timeout: 250 seconds]
<emily>
colemickens: are you still running sway alpha on nixos?
gchristensen changed the topic of #nixos-chat to: NixOS but much less topical, everybody but joepie91 is allowed to be off topic.|| https://logs.nix.samueldr.com/nixos-chat
<emily>
joepie91: I've read the first third of that article numerous times
<emily>
joepie91: but unfortunately somehow doubt I will ever get to the rest of it
<emily>
which seems exactly appropriately ironic to me :p
<emily>
colemickens: is it working well for you? I tried to get your branch working but ended up lost in rebuilding everything because of a meson upgrade
<colemickens>
Yeah, the meson bits are annoying, it ends up rebuilding a ton of stuff since wlroots/sway touches systemd etc.
<colemickens>
Depending on how much you want it, etc, I do push my configs/stuff to a binary cache.
<colemickens>
It's why I wound up keeping it in a separate branch and just pulling in the sway package from it for now.
<colemickens>
I just got the wlroots/example apps working too. They don't all seem to be working correctly, but there's at least an idle-inhibitor, etc, that has been useful.
<emily>
colemickens: yeah, mostly trying to figure out whether sway is close enough to usable that I can dive in now, or whether I should just set up i3 and wait for the 1.0 release
<emily>
(the release version is unusable for me unfortunately)
jasongrossman has quit [Ping timeout: 276 seconds]
jasongrossman has joined #nixos-chat
drakonis_ has quit [Quit: Leaving]
drakonis_ has joined #nixos-chat
<clever>
emily: i got about 10% into the article, then got distracted by how my mouse wheel cant scroll the page, lol
<colemickens>
emily: fwiw, I found the stable release totally unusable and the 1.0-alpha to be quite usable.
<colemickens>
The only real problem I have now is that I am still getting a crash every once in a while when I reposition a bunch of windows with my mouse on a multi-mon setup.
<colemickens>
ymmv of course.
<colemickens>
(hidpi, in particular, is night/day much better in 1.0-alpha)
<emily>
colemickens: that's good to hear. I was having issues like "cursor movement over Xwayland windows is unusably choppy"
<emily>
right
<emily>
it seems like even the alpha version doesn't support disabling upscaling for Xwayland windows though? :/
<colemickens>
You are, unfortunately, correct.
<emily>
which seems like kind of the wrong default given that Firefox and Chromium both have no native Wayland support at present
<colemickens>
I had hoped it would change with wlroots, but the most recent issue I saw about it made it sound like a done deal.
<emily>
hm
<colemickens>
Yes, it's annoying. I'm using "fuzzyFox" right now and praying that the Wayland support improves quickly.
<emily>
I'm pretty sure it'd be a few lines patch to hardcode-fix
<colemickens>
If you turn on flatpak, the FirefoxNightly flatpak has Wayland support, but it's basically not usable.
<emily>
it's just because Xwayland doesn't know how to speak the scaling protocol I think?
<emily>
seems like you should be able to override the scaling setting per-window ideally...
<colemickens>
I'm not sure about that level of detail. I think that was part of the comment I'd read though, that the XWayland instance was shared and (currently?) only understood a single scaling factor.
<colemickens>
Let me see if I can drudge it up instead o likely poorly retelling it.
<emily>
...I can see that being the case. I don't think I should share my opinions on what that would imply about sway's code quality in that case
<emily>
colemickens: like. gnome on wayland already does this
<emily>
or at least it did, if you use an integral scaling factor
<simpson>
Xorg's code quality has been known to not be great, as a whole, mostly due to decades-old C.
<simpson>
And my opinions on sway's authors...are not polite.
<colemickens>
I would also prefer not scaling the XWayland instances. I don't really know if it's a big technical burden, or just an avenue that the author(s) doesn't want to go in.
<colemickens>
If you do end up patching it, I'm sure there'd be a number of interested people.