Shipping labels, tickets etc. Printers suck, but I can rely on paper being suitable for its purpose. Can't say that about most alternatives (mostly phone apps).
That joke is actually pretty old. In fact the link you posted says that it's not his joke. I don't really know where it came from, but it's certainly not from that guy.
This is nice. I run dark mode everywhere and I used to use notepad for quick notes and stuff. Problem is that notepad is a giant wide window so it would burn my eyes out when opened, so I had to switch to something else. Now I can use it for that purpose again...
Providing I move to Win11 that is. Still not a fan of the task bar lacking features I use a lot.
The first definition is "very stupid or foolish" which seems quite apt given the context. The second one talks about a disability, which does not really seem applicable since we're talking about monitors and not people.
So where is the issue exactly? He used the word correctly as far as I can tell.
That still fits. OP is describing the product which they believe to be sub standard and likely want to imply offense to it. There would be a difference between "This product is shit" and "You are shit". Both are sending offense to the target, but one of them is a computer with no feelings.
Looks to me like they just straight up ripped the Discord front-end, changed the parts where it connects to a back-end and hosted it. Registration page has links to Discord's ToS, opening dev tools will give you a message about working at Discord. You can even try to buy nitro on it and it will try to call stripe with what I assume is Discord's key.
Scummy as hell.
Tinc 1.1 is actually fairly easy to set up - it's only a couple of commands for defining the name of the network, getting a link nodes can use to join etc. The only problem is that it's technically not a full release, so most distros don't carry it. Compiling isn't difficult (a simple ./configure && make && sudo make install), but it could be better. My only major issue with Tinc is lack of any central authority making it really niche - revoking keys seems to involve deleting them on each connected machine. Not fun.
From what I can tell ZeroTier seems nice as long as you're okay with using ZeroTier's servers for things (a curious trend I've noticed - so called decentralised services will always be great until you want to have fully independent servers). Sure, you can find github issues telling it's possible to set up your own planets, but the software seems somewhat complex and there's no documentation for it, and moons (what is with this lame terminology anyway?) will ping ZeroTier by default.
Oh thanks, I wasn't aware of that change in Tinc 1.1, I'll try it out. I'm indeed using the distro version, I compliled 1.1 once to have that network view (where you see which nodes are connected) but it wasn't that useful so I didn't bother with it. Didn't realise they simplified the joining also.
Though I never thought the joining and revocation was all that difficult anyway. I just have 2 central servers which carry every key, and the others just need to have the server keys. Everything else gets distributed automatically. So keys for clients you can keep on your servers only. You don't have to delete it from all of your clients!
I know tinc doesn't really have a client/server concept but I consider clients those devices that aren't publicly reachable (behind NAT) and not used in a ConnectTo statement.
And yeah the centralised VL1 "Planet" server in ZeroTier also bothers me. I know it plays no part in the actual access rights to the network and it can't see the traffic content, but still. I just want to run it myself.
yup, `sudo tinc -n %VPNNAME% invite %CLIENTNAME%` will generate an invite URL on the server side and `tinc join %INVITEURL%` will let you join it. It's definitely really easy now, but unfortunately it's being marked as a pre-release which sets tinc back a bit imho.
As for revocation, I have a similar setup and I agree. My worry is that in a theoretical situation an attacker could get access to a network and then spread his key to the entire network and there's little you can do about it. For personal use it's fine (I use it), but because of this, I would be vary of using Tinc for some sort of production use (although I've heard of people doing it). Even if it's a big IF since you need to actually have an access to a node to generate an invite, the attack surface is still there and there's no good way to undo it.
Yeah, 1.1 should really go into production at some point, it's been in beta for years.
It's really a good point you have about a hacker adding themselves to the network. I never thought of that. That could happen with every client so the attack surface is pretty big. It would be great if this feature could be reserved to only certain trusted devices (like the ones I have designated 'servers').
So maybe there is a good point to at least monitor the network activity with this 1.1 feature. Hmm... Thanks for getting me thinking about this!
> We've gotten so used to phone notifications and a persistent history, that IRC has fallen behind purely from a convenience factor.
I have that with a bouncer (znc) and a plugin. I've not used it, but it is my understanding that IRCCloud does this too. Problem is that there aren't many easily usable options for this apart from IRCCloud and even IRCCloud itself isn't all that well marketed.
Always seemed kind of weird how while IRC is full with FOSS people who are willing to use their time on various projects they're not getting paid for, most of whom also seem to worry about IRC dying out, nobody is really doing anything about it. A lot of the conveniences we miss could mostly be solved by making modern clients that are actually good.
I think free (spyvertising supported) and free or steeply discounted (operating at a VC-backed loss) commercial offerings both being so common dampens enthusiasm to work on and demand for open source software, especially the user-facing stuff. Earlier on in computing history (into the mid '00s, at least) such things were much less common.
I think it also dampens the same for traditional paid software in a lot of areas, incidentally.
I've been using it for... around nine years. It used to have a lot of performance issues, notably around synchronising initial state/backlog fetch on first connection to the core/daemon, but those were eventually fixed.
It works very well now, and the Android client is pretty great too, but there are still some gaps. Mainly, the surrounding ecosystem is quite sparse, e.g.:
- There is basically only a single web client for it (node-based, which is a con from my perspective)
- There are only a handful of semi-functional log searching/browsing utilities around
