WTF Bites
-
@sloosecannon said in WTF Bites:
In some more modern systems, it's referred to as error code "LOLOK"
Could have sworn that was error code "PEBKAC"
-
-
@TimeBandit said in WTF Bites:
Could have sworn that was error code "PEBKAC"
also known as Code-18
I hadn't heard that one before... (I couldn't work that close - but then I have a 2 27" monitors...)
-
@TimeBandit said in WTF Bites:
Could have sworn that was error code "PEBKAC"
also known as Code-18
I hadn't heard that one before... (I couldn't work that close - but then I have a 2 27" monitors...)
Also known as Code-2-27...
-
@TimeBandit said in WTF Bites:
Could have sworn that was error code "PEBKAC"
also known as Code-18
Not unrelated to ID dash ten T problems.
-
As a matter of fact, I just came here to slack off during a Jira upgrade. Thought I could be away from that POS for a while, thank you so much!
There's nothing wrong with Jira that can't be fixed by a special visit from .
🍄 "Thanks for burning everything! But there's a mirror in another DC!"
It's all smoke and mirrors.
-
@sloosecannon said in WTF Bites:
@Polygeekery
That reminds me of the time Karen called and was shouting at the first line tech that we should stop printing and that she had already entered two boxes of paper into the printer ...
After some confusion we managed to gather that she, herself, had started a print job from one of our apps requesting a print out of all outgoing orders from 10 years back to present ...
I had a look at the server but our app had perfectly created a print job of 1000s of pages in record speed. It was all sitting in the print queue inaccessible to us ... we convinced her to shutdown the printer and call her local it drones ...Ah you see, you triggered an error code "IFYOUSAYSO".
This particular error occurs when the computer does exactly what you tell it to do.
In some more modern systems, it's referred to as error code "LOLOK"
This is the case for throwing a "cowardly refusing" error.
-
Once an iPhone or iPad joins the network with the name “%p%s%s%s%s%n”, the device fails to connect to Wi-Fi networks or use system networking features like AirDrop. The issue persists after rebooting the device (although a workaround does exist, see below).
-
@Zerosquare said in WTF Bites:
Once an iPhone or iPad joins the network with the name “%p%s%s%s%s%n”, the device fails to connect to Wi-Fi networks or use system networking features like AirDrop. The issue persists after rebooting the device (although a workaround does exist, see below).
Internet of Shit thread is
-
@Zerosquare said in WTF Bites:
Once an iPhone or iPad joins the network with the name “%p%s%s%s%s%n”, the device fails to connect to Wi-Fi networks or use system networking features like AirDrop. The issue persists after rebooting the device (although a workaround does exist, see below).
Sounds like they’re doing something horribly, horribly wrong.
-
@Polygeekery
That reminds me of the time Karen called and was shouting at the first line tech that we should stop printing and that she had already entered two boxes of paper into the printer ...
After some confusion we managed to gather that she, herself, had started a print job from one of our apps requesting a print out of all outgoing orders from 10 years back to present ...
I had a look at the server but our app had perfectly created a print job of 1000s of pages in record speed. It was all sitting in the print queue inaccessible to us ... we convinced her to shutdown the printer and call her local it drones ...Remind me this week that I have a similar story with a week rse end and I caused it.
-
@Zerosquare said in WTF Bites:
Once an iPhone or iPad joins the network with the name “%p%s%s%s%s%n”, the device fails to connect to Wi-Fi networks or use system networking features like AirDrop. The issue persists after rebooting the device (although a workaround does exist, see below).
Sounds like they’re doing something horribly, horribly wrong.
Sounds like a decent reason to change some network names.
-
@Zerosquare said in WTF Bites:
“%p%s%s%s%s%n”
Makes me so want to do that. Except my friend has an iPhone and I have an iPad (only for our dog show stuff).
-
@dcon worth it
-
@Polygeekery said in WTF Bites:
Remind me this week that I have a similar story with a week rse end and I caused it.
It's past midnight here. I missed that week when you posted, but on the other hand it's now this week.
-
-
@Zerosquare said in WTF Bites:
Once an iPhone or iPad joins the network with the name “%p%s%s%s%s%n”, the device fails to connect to Wi-Fi networks or use system networking features like AirDrop. The issue persists after rebooting the device (although a workaround does exist, see below).
Sounds like they’re doing something horribly, horribly wrong.
Sounds like a decent reason to change some network names.
You joke, but there was a somewhat recent patch to prevent computers named
wpad
from auto-registering themselves into DNS...
-
@Polygeekery said in WTF Bites:
It's past midnight here.
I'm a USian and nothing else matters.
-
@Polygeekery said in WTF Bites:
It's past midnight here.
I'm a USian and nothing else matters.
Fuck yeah!
-
@Tsaukpaetra you did blow something up, knock something over, set something on fire, or at least say that unreasonably loudly, I hope.
-
@Tsaukpaetra you did blow something up, knock something over, set something on fire, or at least say that unreasonably loudly, I hope.
Yes.
-
@Polygeekery said in WTF Bites:
It's past midnight here.
I'm a USian and nothing else matters.
-
-
-
: Sarcasm is no laughing matter!
-
I was tasked with evaluating a new ORM. Can it be used in our project, what are the pros, cons, do we need to break stuff depending on existing schema etc.
I ported one database to this shit and almost recommended it (the only problem I noticed was somewhat rigid table naming in many-to-many relationships, but this can be worked around), but then I realized I forgot to do the most important thing when evaluating new tool:
google "$TOOL_X sucks"
Well, guess what: Prisma doesn't really support transactions. They call it "long-running transactions", but in reality that applies to any transaction with more than one explicit statement.
Many users would like to do transactions, but the lead dev, instead of implementing it, spends his time doing mental gymnastics to explain away the need for atomicity:This is not how modern scalable systems are built
Predictably, he has pronouns in bio.
-
@sebastian-galczynski said in WTF Bites:
Many users would like to do transactions, but the lead dev, instead of implementing it, spends his time doing mental gymnastics to explain away the need for atomicity:
This is not how modern scalable systems are built
It might not be how modern scalable systems are built, but it is how traditional correct systems are built.
-
At the end of the universe, everything becomes eventually consistent.
-
At the end of the universe, everything becomes eventually consistent.
Close. However, the end implies the effective equality of thermodynamic and information entropy, therefore it becomes a fine point, probably calling for a schnitt, as to whether the information system can be said to have resolved.
-
The js community in general reminds me of those remote alpine villages before iodized salt was introduced. Everyone looks kinda weird, some can't talk or walk, but they all think it's perfectly normal, because they've never seen any other community.
That's why they have long debates whether the lock should lock
-
@Polygeekery said in WTF Bites:
Remind me this week that I have a similar story with a week rse end and I caused it.
It's past midnight here. I missed that week when you posted, but on the other hand it's now this week.
https://what.thedailywtf.com/topic/28063/on-the-time-i-accidentally-emptied-a-workstation-printer
-
@sebastian-galczynski said in WTF Bites:
The js community in general reminds me of those remote alpine villages before iodized salt was introduced. Everyone looks kinda weird, some can't talk or walk, but they all think it's perfectly normal, because they've never seen any other community.
That's why they have long debates whether the lock should lockI was hoping for a tale of Swiss hydrological engineering gone wrong, but this suffices.
-
@sebastian-galczynski said in WTF Bites:
The js community in general reminds me of those remote alpine villages before iodized salt was introduced. Everyone looks kinda weird, some can't talk or walk, but they all think it's perfectly normal, because they've never seen any other community.
That's why they have long debates whether the lock should lockI was hoping for a tale of Swiss hydrological engineering gone wrong, but this suffices.
Alpine engineering has its limits; Innsbruck remains defiantly not Innsmouth.
-
@sebastian-galczynski said in WTF Bites:
The js community in general reminds me of those remote alpine villages before iodized salt was introduced. Everyone looks kinda weird, some can't talk or walk, but they all think it's perfectly normal, because they've never seen any other community.
That's why they have long debates whether the lock should lockI was hoping for a tale of Swiss hydrological engineering gone wrong, but this suffices.
Alpine engineering has its limits; Innsbruck remains defiantly not Innsmouth.
Well, fuck up a lock bad enough
-
I was hoping for a tale of Swiss hydrological engineering gone wrong, but this suffices.
Was there any such case? Vajont and Malpasset were Italian and French respectively.
-
@sebastian-galczynski said in WTF Bites:
I was tasked with evaluating a new ORM. Can it be used in our project, what are the pros, cons, do we need to break stuff depending on existing schema etc.
I ported one database to this shit and almost recommended it (the only problem I noticed was somewhat rigid table naming in many-to-many relationships, but this can be worked around), but then I realized I forgot to do the most important thing when evaluating new tool:
google "$TOOL_X sucks"
Well, guess what: Prisma doesn't really support transactions. They call it "long-running transactions", but in reality that applies to any transaction with more than one explicit statement.
Many users would like to do transactions, but the lead dev, instead of implementing it, spends his time doing mental gymnastics to explain away the need for atomicity:This is not how modern scalable systems are built
Predictably, he has pronouns in bio.
Actually, the main point makes sense - if you're writing AWS lambda (or something similar), you should not use transactions. You should design your application in a way that it is not needed. Which might be , but hey - it can save you a lot of money.
So yes, it's OK for a specialty ORM.is that they don't have balls to declare it as such upfront (with a big warning at the main page), and instead try selling it as a standard, universal ORM. And declare all limitations as "the modern way".
But then again, this is endemic in JavaScript world, where every hack is "the modern way"
-
@Kamil-Podlesak said in WTF Bites:
@sebastian-galczynski said in WTF Bites:
I was tasked with evaluating a new ORM. Can it be used in our project, what are the pros, cons, do we need to break stuff depending on existing schema etc.
I ported one database to this shit and almost recommended it (the only problem I noticed was somewhat rigid table naming in many-to-many relationships, but this can be worked around), but then I realized I forgot to do the most important thing when evaluating new tool:
google "$TOOL_X sucks"
Well, guess what: Prisma doesn't really support transactions. They call it "long-running transactions", but in reality that applies to any transaction with more than one explicit statement.
Many users would like to do transactions, but the lead dev, instead of implementing it, spends his time doing mental gymnastics to explain away the need for atomicity:This is not how modern scalable systems are built
Predictably, he has pronouns in bio.
Actually, the main point makes sense - if you're writing AWS lambda (or something similar), you should not use transactions. You should design your application in a way that it is not needed. Which might be , but hey - it can save you a lot of money.
So yes, it's OK for a specialty ORM.is that they don't have balls to declare it as such upfront (with a big warning at the main page), and instead try selling it as a standard, universal ORM. And declare all limitations as "the modern way".
But then again, this is endemic in JavaScript world, where every hack is "the modern way"
Unfortunately only half sense. You're not well-advised to use XA transactions or anything that smells like a session, but transactionality benefits a lot of business... transactions... even under horizontal scaling constraints.
Of course, this stops applying once the microservices are gone too far of a specific kind of nuts with
-
Webex has popped up about a dozen modal "You can only join this meeting once" notifications. The fun part? They're stacked in such a way that a) you can only dismiss the topmost window, and b) you can't tell which one is the topmost window!
Status: playing whack-a-mole with modal dialogs
-
Webex
Their motto should be "Almost as bad as MS Teams."
Okay, not almost, there's still a long way to go.
-
Webex has popped up about a dozen modal "You can only join this meeting once" notifications.
What kind of weirdo would try to join a meeting several times? Isn't once already too much?
-
@topspin We're still running both for meetings and Teams is better than Webex IME
-
@loopback0 said in WTF Bites:
@topspin We're still running both for meetings and Teams is better than Webex IME
Which one are you using for the audio?
-
@loopback0 said in WTF Bites:
@topspin We're still running both for meetings and Teams is better than Webex IME
You forget to apply the "made by Micro$oft" penalty of -1000 points
-
@loopback0 said in WTF Bites:
@topspin We're still running both for meetings and Teams is better than Webex IME
You forget to apply the "made by Micro$oft" penalty of -1000 points
Well by the time you apply the "software made by Cisco" penalty to Webex, it's about the same.
-
Webex
Their motto should be "Almost as bad as MS Teams."
Okay, not almost, there's still a long way to go.
They were even, confusingly, calling their Slack-alike "Webex Teams". Then they rebranded "Webex" as "Webex Meetings" and "Webex Teams" became "Webex."
Here at Initech internally, when we say Teams we mean Webex.
-
I also find it baffling how many chat apps there are that seem, to me, to be identical.
Discord, Slack, Webex, RocketChat. It's all the same damn thing.
-
I also find it baffling how many chat apps there are that seem, to me, to be identical.
Discord, Slack, Webex, RocketChat. It's all the same damn thing.
Well, the skinning is different. And none are flat out using the WebRTC reference implementation unmodified... afaik
-
@error Slack was first for text chat.
Discord added WebRTC voice to the mix.
Then they took off. Then Slack added voice (I think?)
Then everyone else saw how successful they were and copied them entirely, as is oft to happen.
-
I also find it baffling how many chat apps there are that seem, to me, to be identical.
Discord, Slack, Webex, RocketChat. It's all the same damn thing.
Well, the skinning is different. And none are flat out using the WebRTC reference implementation unmodified... afaik
They are, but they aren't. They're all using their own.. forwarding service, I believe, which you have to hand-write because there is no reference. Also it's dark voodoo. Also there are no docs.
-
@sloosecannon said in WTF Bites:
I also find it baffling how many chat apps there are that seem, to me, to be identical.
Discord, Slack, Webex, RocketChat. It's all the same damn thing.
Well, the skinning is different. And none are flat out using the WebRTC reference implementation unmodified... afaik
They are, but they aren't. They're all using their own.. forwarding service, I believe, which you have to hand-write because there is no reference. Also it's dark voodoo. Also there are no docs.
The TURN server that gets two clients to handshake together?
The first result on a quick google search (since I have absolutely no idea what I'm talking about) suggests that you can just doapt-get install coturn
.Because once you got that it seems the rest is already implemented in your browser.