<GalaxyNova>
micro_O: Open the wiki for editing then!
<GalaxyNova>
I don't think there's a way to pull request wiki edits
micro_O has joined #kisslinux
<micro_O>
GalaxyNova sorry, just made it open to edits
<micro_O>
and you can PR against github wikis - they are just git repos themselves
<acheam>
micro_O: the current kisscommunity.org has no margins on mobile
<acheam>
Oh nvm
<micro_O>
Actually the current site looks great on mobile for me
<micro_O>
preview could be a bit nicer
<micro_O>
also i wonder, just for fun, if i should keep a snapshot of every version of the site up and hosted, so you could just click to the previous versions xD
GalaxyNova has quit [Read error: Connection reset by peer]
<acheam>
That'd be njce
<acheam>
And easily accomplishable with branches
<acheam>
Or tags
<acheam>
Tags better actually
<acheam>
Yeah idk why it looked bad on mobile earlier, maybe I was zoomed in or something
mahmutov has quit [Ping timeout: 248 seconds]
micro_O has quit [Ping timeout: 252 seconds]
GalaxyNova has joined #kisslinux
<testuser[m]>
Hi
<GalaxyNova>
hello
barpthewire_ has joined #kisslinux
barpthewire has quit [Ping timeout: 245 seconds]
illiliti has quit [Quit: leaving]
gtms has joined #kisslinux
<testuser[m]>
acheam: oh the 800gb usage on my server was inbound traffic, that would mean people sending data to my server right
<GalaxyNova>
800 gigabytes oh my god
<testuser[m]>
yea its weird
<testuser[m]>
now its using up 1gb every 30 min lol
<testuser[m]>
i need to keep it below 1tb before 30th
GalaxyNova has quit [Read error: Connection reset by peer]
<dilyn>
this is unrealistic because I can say 'no thanks' to the cookies popup and the 'no thanks' button for the newsletter sub is pigger than 1px
GalaxyNova has quit [Read error: Connection reset by peer]
micro_O has joined #kisslinux
micro_O has quit [Ping timeout: 250 seconds]
soliwilos has quit [Ping timeout: 244 seconds]
soliwilos has joined #kisslinux
micro_O has joined #kisslinux
progenyx has quit [Quit: progenyx]
micro_O has quit [Ping timeout: 250 seconds]
mbarbar has quit [Ping timeout: 256 seconds]
mbarbar has joined #kisslinux
<testuser[m]>
Ok i fixed it it was libreddit
<testuser[m]>
GalaxyNova what syntax highlighting does `most` do
<testuser[m]>
I read it has it in the description but see nothing in the man page
<testuser[m]>
Neither does it do any highlighting
<acheam>
testuser[m]: what services allowing upload do you have? What open ports?
micro_O has joined #kisslinux
<testuser[m]>
acheam: only 4-5 ports are open for stuff that im actually running, and nothing allows uploads
jedavies has quit [*.net *.split]
ElKowar has quit [*.net *.split]
yamchah2 has quit [*.net *.split]
acheam has quit [*.net *.split]
clemens3 has quit [*.net *.split]
<testuser[m]>
Data downloaded on the server counts as inbound aswell
<testuser[m]>
Usage was fine after stoppin libreddit
<testuser[m]>
I monitored process bandwidth usage and libreddit was the only thing using bandwidth
<testuser[m]>
Rest was 1-2 kbps
<testuser[m]>
I'll probably limit libreddit to a few hundred kbps instead of uncapped bandwidth, not sure where so many requests are comjng from in the first place
<testuser[m]>
Will check later
ElKowar has joined #kisslinux
jedavies has joined #kisslinux
clemens3 has joined #kisslinux
acheam has joined #kisslinux
yamchah2 has joined #kisslinux
<micro_O>
i wonder if its worth doing a semi-private libreddit
<micro_O>
like, 5 ips connected at full bandwidth, and a queue
<micro_O>
maybe too complex, compared to just 'this is limited to Xmbps, if you want more, run your own instance'
<micro_O>
also a guide on running a 'floating ip' instance
<testuser[m]>
You'd constantly need to whitelist ips tho since home ips are dynamic
<micro_O>
testuser[m] idea is more like "i have seen 9 ips connect in the last hour, refuse requests from any other ips for the next hour, then expire"
<micro_O>
home ip is unlikely to be so dynamic to be changing more than once a day unless you are really unlucky with rebooting/timing
<omanom>
you might be able to write a fail2ban filter to do that
<noocsharp>
anyone used zoom from inside junest before?
<micro_O>
ok, i was waxing and waning with his attitude, but his motivations and results are amazing
<micro_O>
especially the 'you should not be a second-class citizen developing on android, if all you have is an android phone'
<micro_O>
i think it would be dope if we moved from busybox to toybox in the default image
<micro_O>
though bentobox is such a great name
<micro_O>
has anyone setup cloud-init? dont see it in kiss-find, and was wondering if anyone is running KISS on a VPS
<testuser[m]>
What's clouds in it
<testuser[m]>
Cloud-init
<micro_O>
its a requirement if I want to make a custom image for a DigitalOcean droplet
<testuser[m]>
Oh
<micro_O>
seems to be an entrypoint so different cloud providers can inform the operating system that a) its running in some 'cloud' and b) i have no idea what else
<testuser[m]>
I use kiss on vultr and dilyn uses linode, other users idk
<micro_O>
vultr supports cloud-init, linode does not
<micro_O>
> Cloud images are operating system templates and every instance starts out as an identical clone of every other instance. It is the user data that gives every cloud instance its personality and cloud-init is the tool that applies user data to your instances automatically.
<micro_O>
thats actually a pretty reasonable description
<omanom>
its like ubuntu preseed files or the fedora/rhel kickstart files used by anaconda
<omanom>
a way to skip the normal manual installation questions
<kyxor>
the toybox maintainer/developer is so wholesome
mahmutov has joined #kisslinux
<kyxor>
it's easy to write some software/program, but the hardest part is to maintain it long term a polish everything out until it's perfect, optimize, remove the most lines of code you can ( including any kind of dependensies, 3rd party stuff, etc)
<kyxor>
To just get there, you have to spend tremendous amounts of brain power
<dilyn>
landley has invested a lot of brain power into this one class of programming projects for... basically twenty years now
<noocsharp>
somebody will probably fork eudev and keep developing it
<GalaxyNova>
Why was that change needed anyway?
<illiliti>
what change?
riteo has joined #kisslinux
<riteo>
hiiiiiiii!
<riteo>
I just noticed the website changed again! It looks really interesting now.
<GalaxyNova>
iilliliti: The eudev -> udev change in gentoo
<GalaxyNova>
riteo: Yeah!
<illiliti>
GalaxyNova: as far as i understand, it's hard to keep eudev in sync with upstream
<dilyn>
based on that PR, it would take longer than systemd has been in development to finally rewrite the whole thing in rust
<riteo>
>Expect more frequent updates from me about KISS in this new tidbits page.
<riteo>
YES
<riteo>
I *LOVE* reading about stuff in the making, expecially something so simple like kiss linux where you can't possibly see that much stuff to do left
<acheam>
the stuff to do is mostly packaging-related
<acheam>
which is always changing with new firefox releases, gtk updates, etc
<soliwilos>
GalaxyNova: Seemed like the maintainer of eudev lacks the time to maintain it, originally doing it because of the musl project in gentoo. Now with the openembedded patches they thought to just drop eudev I guess.
<GalaxyNova>
ah that's unfortunate
<acheam>
it looks like `kiss` itself's development has slowed again
<riteo>
acheam: well if by packaging you also mean documentation that's a very big and important thing
<GalaxyNova>
acheam: That's not bad in some ways
<acheam>
GalaxyNova: never said it was bad
<riteo>
acheam: oh, I hope git caching support made it before this slowdown
<riteo>
I mean, it can be bad if stuff was in the making and suddenly stopped
<GalaxyNova>
kiss now no longer hard depends on curl
<GalaxyNova>
IIRC
<acheam>
what I meant is that it looks like dylan implemented most of what he had in mind / was thinking of over his break
<riteo>
oh I see
<acheam>
for a while we had daily releases, now they've slowed to every week or two
<acheam>
(which is still very quick)
<riteo>
I'm still interested in generic repository updates (as soon as that comes in I'll port java to kiss, I need it to do that if I don't want to die AFAICT) and git caching
<riteo>
those are some pretty juicy features
<acheam>
for git caching why don't you just use a tarball snapshot
<acheam>
most git hosting providers offer it
<riteo>
well git packages need to redownload stuff everytime
<riteo>
instead they could just pull the latest commit or two
<acheam>
seems fragile
<acheam>
it would need to deal with branches, force pushed commits, etc
<riteo>
some minecraft plugins depend on being compiled on the latest commit and that's a big waste, especially for bing ones
<acheam>
what about yahoo ones?
<riteo>
lmao
<riteo>
I meant big
<travankor>
btw what happened to the c rewrite?
<acheam>
which one?
<riteo>
I think they meant k
<acheam>
dylan stopped developing k like a year ago
<travankor>
there's more than one?
<acheam>
noocsharp started one
<riteo>
well yes, unofficially of course
<travankor>
oh, cool
<travankor>
so k is officially dead
<acheam>
there is also piss, king, and some other ones
<travankor>
king is written in go
<acheam>
yeah
<acheam>
i was talking about rewrites in general
<acheam>
s/rewrites/reimplementations/g
<cotangent>
<acheam> i was talking about reimplementations in general
<travankor>
is piss another shell implementation?
<soliwilos>
It seemed like Dylan would still develop k/kiss in c, but differently. More of a modular approach if I recall correctly.
<acheam>
travankor: python
GalaxyNova has quit [Quit: Whoooooshh]
akira01 has joined #kisslinux
<riteo>
btw didn't Dylan plan to port kiss slowly to C?
<riteo>
was this completely put out of the question?
<travankor>
that's what i was asking :p
<dilyn>
he scrapped k and wants to do it in chunks now
<soliwilos>
Dylan brought it up in one of his posts after his return.
<dilyn>
implementing certain parts and having kiss use those things and defaulting to the script for the rest
<riteo>
oh so it's still a thing
<acheam>
but why?
<acheam>
hmm its a shame the old website blog posts are gone
<riteo>
yeah I agree
<riteo>
also I'm a bit confused too on why one would do this hybrid c thing
<acheam>
also a shame that he didn't revamp the generated-pages-tracked-by-git model of the repo
<riteo>
IIRC it was in order to do a slow progression to a c package manager
<riteo>
acheam: eh, if you mean that the built files were in the sources IMO that's a better choice
<riteo>
anyways having a c package manager is very elegant in a way but at the same time I feel like the POSIX shell package manager is one of the biggest strenght of this meta-distro
<acheam>
riteo: why though?
<riteo>
you can build them with a simple `make` IIRC
<riteo>
it's like bundling the compiled binary of a program alongside the source IMO
<acheam>
huh interesting, dylan renames kisslinux/community to dylanaraps/community
<acheam>
riteo: yeah so why is that better?
<riteo>
acheam: wait what are you talking about
<riteo>
the posix package manager part or the builded scripts in repo thing
<acheam>
no
<riteo>
s/scripts/webpages/
<cotangent>
<riteo> the posix package manager part or the builded webpages in repo thing
<acheam>
kisslinux/website shouldn't have generated HTML in it IMO
<riteo>
oh so we're on the same page with that
<acheam>
oh
<kyxor>
okay I found some kind of bug in busybox ash "/bin/ash: fg: can't set tty process group: Bad file descriptor"
<acheam>
what context is this in?
<acheam>
^z then fg?
<kyxor>
fg does not restore vi process
<acheam>
time for some git-bisect-run
<acheam>
because it would work fine for me when I ran ash
<kyxor>
yeah but I did some stuff with setting set -o options in the shell
<kyxor>
well killing vi does return to back to shell though, but repeat, same stuff...
<kyxor>
definitely not a vi problem though. ok
<kyxor>
Hmm so I did set +m which turns off monitor
<kyxor>
maybe this isn't a bug
<kyxor>
yeah set +m apparently turns off the job control, I did it by mistake :) never thought it would be like that
<acheam>
lol
<acheam>
in ksh, set +m disables ^z, so not sure why ash doesn
<kyxor>
no it does, it's just that it gives descriptor errors when the monitor is off
<kyxor>
when I see errors like that Immediately think something is bugged though, but this is just because busybox devs decided to save 1 line of code and not add an if statement
sammyette has joined #kisslinux
sammyette has left #kisslinux [#kisslinux]
micro_O has quit [Quit: micro_O]
gtms has quit [Remote host closed the connection]
m3g has quit [Remote host closed the connection]
<phoebos>
micro_O you can run whatever you want on a DO droplet without making a custom image :p
Uks2 has quit [Ping timeout: 240 seconds]
Uks2 has joined #kisslinux
Guest6162 has joined #kisslinux
ithuriel has joined #kisslinux
Guest6162 has quit [Client Quit]
ithuriel has quit [Ping timeout: 240 seconds]
cotangent has quit [Ping timeout: 240 seconds]
travankor has quit [Ping timeout: 258 seconds]
vulpine has quit [Ping timeout: 250 seconds]
kiedtl|litterbox has quit [Ping timeout: 240 seconds]
mahmutov has quit [Ping timeout: 252 seconds]
GalaxyNova has joined #kisslinux
riteo has quit [Read error: Connection reset by peer]