veleiro has quit [Read error: Connection reset by peer]
Dotz0cat has joined #nixos-chat
veleiro has joined #nixos-chat
kalbasit has joined #nixos-chat
waleee-cl has quit [Quit: Connection closed for inactivity]
Dotz0cat_ has joined #nixos-chat
Dotz0cat has quit [Ping timeout: 246 seconds]
kalbasit has quit [Remote host closed the connection]
cole-h has quit [Ping timeout: 264 seconds]
<lovesegfault>
Goddamn why is it so hard to encounter a lapras in pokemon sword
<lovesegfault>
been here fishing for like an hour
<lovesegfault>
What a PITA
supersandro2000 has quit [Ping timeout: 264 seconds]
veleiro has quit [Read error: Connection reset by peer]
<V>
veleiro: even i3 has a script for saving/loading layouts, I don't think you'll have any issues with sway?
veleiro has joined #nixos-chat
<V>
if you want to find out how to do something with sway, you might have better luck searching for "how to do X with i3" because its IPC mechanism is mostly compatible and i3 has far more resources made for it
supersandro2000 has joined #nixos-chat
veleiro has quit [Read error: Connection reset by peer]
veleiro has joined #nixos-chat
veleiro has quit [Read error: Connection reset by peer]
<eyJhb>
sphalerite: It is basically the same I am at. It is expensive and it costs "time" :D
<eyJhb>
Maybe over the summer
ky0ko has quit [Remote host closed the connection]
tilpner_ has joined #nixos-chat
tilpner has quit [Ping timeout: 264 seconds]
tilpner_ is now known as tilpner
<philipp[m]>
Whoa! AVM is really decent about supporting their older devices. My fritzbox 7490 from 2013 just got a firmware update that enabled WPA3.
<supersandro2000>
my old one fried...
ky0ko has joined #nixos-chat
srk has quit [Ping timeout: 240 seconds]
srk has joined #nixos-chat
waleee-cl has joined #nixos-chat
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-chat
__monty__ has joined #nixos-chat
immae[m] has left #nixos-chat ["WeeChat 2.9"]
waleee-cl has quit [Quit: Connection closed for inactivity]
Deknos has joined #nixos-chat
lunc has joined #nixos-chat
waleee-cl has joined #nixos-chat
cole-h has joined #nixos-chat
cole-h has quit [Quit: Goodbye]
<viric>
I use syncthing (port 22000) and nixos linux tells me "refused connection: .... LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=62660 DF PROTO=TCP SPT=22000 DPT=0 WINDOW=65535 RES=0x00 SYN URGP=0"
<viric>
how is it messing with DPT=0?
cole-h has joined #nixos-chat
<tilpner>
viric: Local source address?
<cole-h>
Man, I really hate how, sometimes, the notifications dashboard just autorefreshes
<cole-h>
I was about to go on a "mark as done" spree while keeping a few around, but it autorefreshed and now I marked something I didn't want to as "done"
<viric>
tilpner: it's ethernet, from the android syncthing to my eth0
<viric>
I thought I better don't disclose the MAC addresses :)
<{^_^}>
syncthing/syncthing#4278 (by vision57, 3 years ago, open): Port 0 listen address gets announced to discovery servers
<tilpner>
You did openFirewall = true;, right?
<tilpner>
Uhh, openDefaultPorts = true
<viric>
tilpner: I have firewall.allowedTCPPorts = [ ... 22000 ]
<tilpner>
(This is why I'm not in #nixos anymore, too many interesting problems!)
<viric>
and openDefaultPorts = true too, yes
<viric>
:)
<dadada_>
viric: A source port of 0 typically means that an ephemeral port should be used. How 0 ended up at the discovery server is a bit puzzeling though.
<cole-h>
viric: Also try adding `networking.firewall.allowedUDPPorts = [ 21027 ];`
<viric>
tilpner: nixos already works very well
<viric>
dadada_: I know
<cole-h>
I have TCP 22000 and UDP 21027 marked for syncthing, FWIW.
<tilpner>
That's already covered by the default ports though
<viric>
right
<cole-h>
o
<tilpner>
At least, if we're looking at/using a sufficiently similar nixpkgs
<viric>
syncthing connects fine, but I have those lines in dmesg every now and then
<viric>
tilpner: if the port 0 is announced.... maybe then the remote side simply attempts to connect to it
<tilpner>
Yes, but that would be stupid
<viric>
well that's a bug
<tilpner>
It does match my link above though
<viric>
well I took that from your link
<viric>
AH well I'm not specifying port 0 anywhere though
<tilpner>
Is #syncthing a thing?
<viric>
I asked there before here :)
<viric>
#nixos-chat is often most effective
<tilpner>
And they didn't know?
<viric>
silence
<tilpner>
Ahh, typical
<__monty__>
viric: Please stop abusing -chat for ontopic questions.
<tilpner>
It's not that ontopic, if we assume it's a bug
<viric>
:D
<__monty__>
Bugs are pretty ontopic in #nixos if you ask me.
<__monty__>
Yep. There's a reason I keep an eye on this channel and not #nixos all the time.
<infinisil>
I agree with __monty__
<viric>
I don't see any related with nixos or nixpkgs
<viric>
(it)
<viric>
it was a networking question, which has to do with computers in which one of them runs nixos...
<__monty__>
Ontopic until proven innocent.
<viric>
¬_¬
<viric>
It's not the 1st time I see that kind of hostility here when judging topic-ness... it's disturbing.
<__monty__>
It's not the first time I see people trying to abuse -chat as a way to get faster support either. Which is even more disturbing.
<viric>
I came to #nixos-chat because of topic-ness claims on #nixos... I think I do good judgement on what is nixos related and what not. And I was asking about DPT=0 here and syncthing, which I judge has nothing to do with nixos
<__monty__>
Ok, you are forgiven.
<infinisil>
I don't think #nixos-chat should be used as the fallback for everything that doesn't fit into #nixos
<viric>
infinisil: I didn't want either, but I was told to go here if things were not nix* questions
<__monty__>
What I saw was a lot of talk about nixos options for something that's not a nixos question though.
<infinisil>
There are many other irc channels better fit for getting support
<infinisil>
This is like a coffee break room
<viric>
ok, so my network question was neither for #nixos and #nixos-chat?
<viric>
pf
<infinisil>
Where you have random little chats, not getting support for all kinds of things
<__monty__>
Still sounds like a #nixos question to me. It's a question about syncthing not working with a nixos host specifically.
<viric>
tell me where should I go
<infinisil>
#nixos, or if it turns out not to he a nixos problem, to wherever syncthing tells people to get support from
<viric>
I'll go silent. I'm annoyed
<viric>
this is getting authoritarian
lunc has joined #nixos-chat
<infinisil>
Or #linux, any channel meant for support that kinda fits
<philipp[m]>
Look: A lot of people here devote a lot of free time to this project. So much that burn out is an actual problem. At least let those people have a community here to relax and don't bother them.
<infinisil>
viric: Imagine if everybody came here for their random problems
<adisbladis>
viric: This is not authoritarian, people are nudging you towards a better solution to your problem.
<adisbladis>
No one in a position of power is doing anything here
<adisbladis>
philipp[m]++
<{^_^}>
philipp[m]'s karma got increased to 1
viric has left #nixos-chat [#nixos-chat]
<eyJhb>
#nixos is also a endless hole of questions. A better documentation would aid greatly in many questions in there ...
cosimone has joined #nixos-chat
lunc has quit [Ping timeout: 264 seconds]
<eyJhb>
Also.. MANY Markdown to HTML/whatever converters lack a clear distinction between title headers, e.g. # vs ## vs ###, once you nest too much you cannot really tell anymore.
ixxie has quit [Quit: Lost terminal]
bridge[evilred] has joined #nixos-chat
srk has quit [Read error: Connection reset by peer]
srk has joined #nixos-chat
cosimone has quit [Quit: cosimone]
<worldofpeace>
eyJhb: pandoc?
<LinuxHackerman>
eyJhb: probably not much different if you just use <h1> <h2> … in HTML
sphalerite has quit [Quit: WeeChat 2.6]
sphalerite has joined #nixos-chat
<eyJhb>
worldofpeace: Only if numering is enabled for each subsection :/
<eyJhb>
LinuxHackerman: yeah, that is the exact issue. But I think HTML is much worse, as it is about the same size...
<gchristensen>
one thing that I find really upsetting about asciidoc is how all the title prefix characters have no specific meaning, and meaning is added based on the order they're used in the document
<eyJhb>
https://i.imgur.com/VaLOt0R.png , the top 3. is main header, wha is ##, dif is ##, ken ### I think. I am at #### at a:
<eyJhb>
gchristensen: ==?
<LinuxHackerman>
eyJhb: add some stylesheets :)
<eyJhb>
Might be a good idea. Atm. I would MUCH rather look at the raw .md, than the rendered version.
<eyJhb>
Even as is, I don't really like the Wiki syntax, or the asciidocs of == title ==... And using == feels like I am going against the norm
<gchristensen>
itisn't the visual thing I care about, it is that the meaning is ... there is none
<gchristensen>
you have to read the document top to bottom to figure out what means what header level
<eyJhb>
Agreed, that does not make any sense. Just redaing it is a pain.
rajivr has quit [Quit: Connection closed for inactivity]
lunc has joined #nixos-chat
<abathur>
communicating hierarchy in an unnested/left-aligned document is a tricky design problem beyond a few levels
<abathur>
it gets a little easier if you're willing to split the document up over many ~page-equivalents; note that most print books (and ebooks laid out using the same idioms) work around this problem by using distinct separator pages for the top few levels of the hierarchy--title page for the book/volume, part pages if parts are used, and a distinct chapter-introduction for beginning each chapter
<abathur>
I do like being able to nest in the source in RST, though it does have the downside of huge diffs anytime you rework hierarchy
<abathur>
I suspect people would hate it, but I guess you could get similar hierarchical clarity in markdown if you lint/test to ban multi-section documents; require each file to be a single section, use either one global ToC or per-directory ToCs to structure them into the document (synthesize header levels then), require the ToC and directory structures to match
<jtojnar>
wow, since when does gcc include OSC-8 links to docs in the error messages?
<bbigras>
Do many of you people have raspberry Pi 4 running nixos? Is it worth it for a tiny server at home for fun?
<samueldr>
it's an YMMV situation with the raspberry pi foundation products
<samueldr>
mainly because we try to stick to mainline, by default, so currently there is a specially-built image for the raspberry pi 4 to help users set themselves up from nothing
<samueldr>
the only "supported" board with NixOS on ARM (for what it's worth) is the 3B (not 3B+)
<cole-h>
gchristensen: Since you're not going to refresh your GPG key, are you just using vault for passwords management?
<gchristensen>
dunno :
<gchristensen>
:?
<gchristensen>
thus far I just put faked-system-time 1609455600 in .gnupg/gpg.conf
<cole-h>
hehe
<cole-h>
I wonder if age has a pass equivalent yet.
<cole-h>
Looks like gopass has age support.
<gchristensen>
maybe vault would be fine, actually, using its kv support
<gchristensen>
and the tools that integrate with `pass` have sucha trivial integration that making a `pass` shim would be ~trivial
<cole-h>
The only downside is that it doesn't look like vault has a way to link otp and kv. I know it has an otp provider, but the "separation" (mounts, I think they're called) makes it a little awkward
<gchristensen>
ah
<gchristensen>
I don't use pass for otp anyway, I feel pretty strongly that the otp thing should be separate from the password
<cole-h>
I see
<cole-h>
What do you use, then? Vault, or an app?
<cole-h>
I have an app that I try to keep ~in sync with my password store. I just feel better using password store because I can at least back that up easier (`rsync -av ~/.password-store /djsakljdklas`)