Amen. Now, where’s that Wine?
Web Developer by day, and aspiring Swift developer at night.
Amen. Now, where’s that Wine?
It’s blood-comma-sweat, not “blood sweat”.
FWIW, I’m referring to the local DNS (domain name system) resolver; the mechanism that resolves local domain names into IP addresses so that computers can talk to each other over the LAN.
Here is a good primer on the configuration files and their possible locations: https://www.freedesktop.org/software/systemd/man/latest/resolved.conf.html
Edit: be careful because this is your domain name lookup you’re messing with. 😊
I hate the fact that for the longest time, iOS would autocorrect fuck to duck. And worse yet, they touted no longer autocorrecting it as a new feature as part of their WWDC keynote.
Let’s be honest, they’d probably already be screaming foul play regardless.
Would have loved to, but keep getting a 401 when attempting to login. 😢
Reticulum? I barely know’um!
Quick! Somebody melt a bunch of soda cans and pour it down the ant hole.
Because it’s not simply “distributing” the load; it’s actively hiding an instance as if it doesn’t exist. So what do they do when the next instance gets “too big” for their liking? Hide it, along side LW? And the next?
Re-read my comment — specifically the second half where I offer a potential solution that would actually distribute the load more fairly without having to hide anything.
Honestly, it’s a short-sighted move made with hubris by the developer’s personal ideology. Both @nutomic@lemmy.ml and @dessalines@lemmy.ml admit in the PR that it’s not a good solution, but yet they continue any way — probably because it’s an easy “solution”, despite alienating 41% of their active user base.
It’s a terrible trend in a lot of programming circles that programmers think because it is easy and it “works” (in that one circumstance) that it must be correct. This can be evidenced by browsing StackOverflow and reading the accepted answers for a lot of questions (SSL errors in software and disabling hostname verification or cert checks comes to mind).
In my 18+ years of experience, if I find an “easy” solution to a complex problem, I keep looking for the correct solution. What is “easy” now will most likely lead to more complex problems down the line. And as they say, “if you can’t find the time to fix it right the first time, where are you going to find the time to fix it again?”
Look, I get Lemmy is meant to be decentralized. Hiding away your biggest instance looks shady to outside users not in the know. The real solution is to “go door to door” to app makers and ask them to not default to any one instance of Lemmy (side note: randomizing a default server is not much better). If anything, add a link to join-lemmy where people can browse the list of ALL instances (yes, ALL of them) and let them make a genuinely-informed decision on their own. As a convenience, and API should be provided (assuming one does not already exist) so that apps can query a pageable/searchable list of existing/active instances (maybe also provide a link to their homepage too).
Hell, if it makes everyone feel warm and fuzzy, the default sorting of returned values can be weighted by percentage of active users (i.e., higher percentages get lower weights to help promote smaller instances). This would help to round out the number of signups without excluding instances.
But whatever developers do (not just Lemmy devs), do NOT overly dictate how people use your software “because I don’t like it”; lest you piss your user base off.
/two-cents
Edit: clarified a few points.
You can use kill -l
(lowercase L) to see a list of signals. But IIRC it’s the same as -KILL
.
EDIT: fixed the signal name.
Nah, we gotta kill
, preferably with -9
. 🤣
The rights of children, especially privacy, has never been a priority for anybody except the children themselves.
Nice! Amazing what a few extra pixels can do.
I’m more intrigued by what appears to be a ghost arm behind his right shoulder.
Technically yes, by way of Planet Hulk first.
The problem is that they both are contextual and can mean any position in a list/array. The starting index or starting offset is generally zero, but could be one, depending on the language used.