Pika

But you have heard of me~

#hadto

I just don’t go to social interactions, easier

Just chiming in, this is not recommended for proxmox

The documentation (FAQ 13) actually directly says that docker should be installed as a QEMU VM on proxmox and that it should not be installed on the Proxmox VE Host

the amount of software I’ve used that lacks this type of system is aggravating. How hard is it to keep an object of property names, and if the name isn’t in it then it errors.

this can be continued into command line as well. if flag -z doesn’t exist, you shouldn’t allow me to run a command with it. It’s clear I am trying to do something (incorrectly) thinking -z is something it isn’t, just error it and tell me that.

Because it’s universal, it works, it’s multi-platform, device agnostic and it’s simple to use user side.

Nothing else available really fits that criteria.

The closest in todays age is probally discord or teams, but neither of which are decentralized. XMPP could work for it, but nobody really uses it anymore and to be honest the standard is ugly as hell to implement.

Browser Notifications are ineffective and have a high probability of failing or not being seen, they are more meant for real-time notices not historical notices not to mention locked to that browser.

App notifications would be amazing for things with apps, but not everyone wants to be forced into using their mobile device for everything, and it would again only be available from said app(unless you do use something like NTFY), which would generally be locked down to a device

Email sucks admin side, but there’s a reason its used.

This is also ignoring the multi-use case that email allows for such as authentication as well, so if its already being stored for accounts, might as well use it for notifications

hard agree, I hate browser notifications with a hard passion, I would never see them if they swapped to that.

my only complaint about it is the lack of clear “hey this is going to be a major update” on the webUI. I did the update command and was met with a different UI. Which wasn’t difficult to figure out, and I have to blame myself for not actually checking the patch notes first, but I wasn’t expecting a major update from the webUI as it only said “new version available run this command to upgrade”

the upgrade as a whole is all and all a great improvement

Jokes aside, this is an amazing book series, I loved it

Me logging onto Skype after so many years

I’ve recently setup an recipe archival project using tandoor, I’m working on converting all my grandparents fading old as dust cooking recipes from their misc handwritten cursive notecards to digital.

Setup was uneventful but it took a little research to figure out how to use a remote postgres server, turns out the app doesn’t give an error when it can’t connect to the server, it just fails to run

Have to say the actual program itself is absolutely absurd and how they choose their permissions, it breaks all conventional and took quite a bit to get used to.

I thought about it, but immediately dismissed it cause they would lose their entire user base. It would be far too complex to have whitelist based access, as soon as anyone realized how restrictive it is they would bail

You don’t even have to leave the work Sim at home, a lot of phones allow you to just disable the SIM card in your settings. For example my phone has three SIM card slots in the settings. It has the primary sim, Sim 2 and then it has the esim. Granted I only use sim one and Sim 2 is a SIM card for a pay as you go style carrier that way if I ever get in trouble with my current carrier I can just activate it and go.

Back when I was in retail, Sim 2 was my “work sim” , paid for by the company, when I clocked out for the day I just turned it off

Less wear and tear on the phone as well by doing that

So I went to a little bit of a deep dive regarding this, they do require interrupting DNS as part of their Redemption grace period. Furthermore I went into the hexbear website and their current header indicates that despite the fact that it’s in current auction the current owner can still sign in and redeem the domain. Which makes me think that they’re running a more gracious rgp then what is to be expected. So that being said they could just be placing bids on a domain that won’t actually sell.

Being said though apparently according to other comments the infrastructure maintainer of hexbear has been AWOL for a while so it’s entirely possible that they just won’t notice it that it will transfer

The way I see it, there’s a few things that may have happened here.

1. Either the domain registrar incorrectly processed their expired domain system and sold the domain without interrupting DNS in which case a third party bought it and then immediately put it to auction (unlikely cause the status / NS is the expired servers), this route would open up the domain registrar to a complaint being filed against them via ICANN

2. Or their domain registrar had a 30-day preemptive period where they were messaging the person, and then an additional few days with auction rgp that’s the actual official last call for it, if this is the case then hexbear’s infrastructure admin should be able to just sign in and renew the domain, but they may be forced to pay a Redemption fee on top of it, if that’s the case then when they renew the domain, the auction would continue running it’s just when it ended no buyers would be selected because the original owner renewed

3. Essentially the same thing as one, however they never disabled DNS, and instead of it being a third party, it’s themselves putting it out to auction on the tail end of the 30-day rgp window. If that’s the case then like number one they’re in violation of ICANN as DNS wasn’t disabled.

Again though, this is off the consensus that they didn’t disable DNS a month ago, which I’m leaning at because I haven’t seen any comments regarding it nor have I found any ststus sites showing that the domain was offline

I must not understand it properly, how was the instance functioning during the grace period for the domain? I was under the understanding that the grace period still had the domain name disabled it’s just the owner had the ability to renew it still

then once the grace period ended then it hit redemption period where it’s auctioned.

If the domain expired 1/12, how was hexbear functioning for the last month(or was it not and I just didn’t notice cause I don’t interact with it)

this is what messed me up with ZSH for a bit, having a shell default to 1 instead of 0 was weird

in all fairness, most developers that are still passionate about code aren’t looking for promotion anyway, because usually once you hit the management level positions you do far less code and more bureaucracy bullshit, and what code you do is usually limited to guidance or review.

Now being passed on raises or laid off? that might be annoying.

Yea for sure, I plan to implement that as well when I have some free time.

Oh ok, thank you, I already use Portainer for my existing setup so it wouldn’t make much sense to fully rework it. I haden’t thought of version pinning though so I may implement that instead, it makes sense “breaking changes” wouldn’t happen within the same major version.

Strangely it sounds like that’s correct. I was under the understanding that depends_on cared about it past start as well but it does not. It doesn’t look like there’s a native way of turning containers that are depending on one another when you turn the dependency off. It looks like the current recommended way of doing it is either with a Docker compose file (which doesn’t help if the process crashed/was concidered unhealthy), or having a third party script on the host monitor the dependencies and if one is considered offline, it turns the dependees off.

Looking into it the concern has been approached twice now on the GitHub page, however every time that it’s been brought up it’s been closed for stale because nobody ever replies to the question

I don’t use Watchtower myself for the same reasons described, but I was under the understanding if you had a container as a dependency on another container that if you took the dependency down it also took the container down. Is this not actually true?