893 karma · joined December 11, 2020
I have one friend who absolutely swears that "covid babies" are a thing, and that you can spot them from across the room. I haven't yet figured out what that means, but I tend to believe her.
So not sure I can really quality/quantify it, but just like this article, maybe someone will try and an article with a catchy title will be written about it.
Generally speaking, there are short codes, and long codes. Sometimes alphanumerics are allowed, but the rules vary regionally.
Long codes resemble traditional phone numbers and tend to be treated as more disposable, low volume, and person-to-person. As such, they are typically easier to spoof with.
Short codes tend to be more like car license plates: short random/vanity codes that require a more in-depth process to get access to. They are easier to verify ownership, suited for higher volume messaging, and tend to be backed by automation systems that respond to a set of automated commands like "HELP". These qualities make them less likely to be used for nefarious purposes.
It's definitely a topic I'd love to understand more. Any corrections/additions are very much welcome!
I have a few years of experience w/ SQLite as a backend for dev/test purposes, and the biggest lesson has been in reinforcing best practices... the kind Postgres demand and you're lucky if MySQL reminds you about.
So my newb two cents is that Litestreams makes some unique and significant contributions: it's not "scale out" but "pivot out" to reflect that you've got great backup/replica solutions with impressive agnosticism around what the future solution is.
Thats a lot of leeway to prove that "X's brainchild is a viable product" while minimizing "Y's devops team and infrastructure" without compromising on durability essentials, especially where the solution to so many things is "dump/serve a(n) [encrypted] copy to/from S3" already.
Eager to drink some more kool-aid. :-)
I still tend to keep the "HACKS" thing though, simply because they localize the documentation right where you need to be aware of it.
For "DREAM" there is a ticket for proper tracking. For FIXME, code review prior to merge is sufficient. For HACKS, you really only need to care when you happen to be working in that space.
And yes, HACKS is to highlight the importance of a comment. It also signals an intentional deviation and an opportunity for someone to offer a suggestion on how to improve things.
- DREAM tags let me focus on getting things shipped and avoid over optimizing/generalizing things that won't provide immediate value. When working in a professional context, they are always accompanied by a ticket. This adds a nice binding for whoever comes next to pick up the task.
- FIXME is also used to help maintain focus, but with the rule that no code ever gets merged with this tag still in place. For personal projects my branches tend to be quite large, so I'm comfortable accumulating some small number of these.
- HACKS calls out unintuitive behavior: breaks in abstraction layers, worst-practices that have better implementations than best-practices, or anything that smells "clever".
Everything else is just comments that future me/team can look back on and say "he must have been drunk when he wrote this, but thanks to these comments I can clearly understand the context and at least what was intended."
- https://how-i-experience-web-today.com/
- https://news.ycombinator.com/item?id=28280051
Agreed 100% that I'm increasingly more inclined to instantly close a site and move on instead of put up with all the attention hi-jacks.
I like the reader-mode ideas folks have mentioned. In some cases I maintain custom Tampermonkey scripts for automating this, but have yet to try any add-ons around pop-up management. Maybe it is time...
Quite the opposite. I have really poor ability to tune them out, especially any audio portions. Once in front of me, they get under my skin easily and this isn't something I feel comfortable trying to just accept, despite how much "easier" it'd make things.
> Because it does not get better. As you begin to adapt to them, the ads change.
Agreed 100%, thus why zero tolerance is the only permissible option for me.
Here is a wager I don't wanna win: the "apps are constantly force-updated" world merges with the marketing world so that downtime is filled with ads. It's devilishly perfect: you're eagerly waiting to use the thing, so you're already a captive audience.
- https://krebsonsecurity.com/tag/sodinokibi/
- https://krebsonsecurity.com/tag/revil/
In particular, for the individual named: https://krebsonsecurity.com/2021/11/revil-ransom-arrest-6m-s...
I'd love to do a shameless plug for radioparadise.com as a wonderful model of someone who does an extremely tasteful periodic reminder to donate :).
It's honestly like quitting your drug of choice (e.g. even just coffee or alcohol) and observing the affect it has on you after using it again for a long time. Only in this case, there is no "upside" to these (forced) capitulations.
Advertising has become so entrenched that it acts as if it has absolute right to your hijack your attention, and this landscape respects no boundaries. Apple in particular drives me nuts doing the same thing: pitching their arcade or wifi hot-spot partnerships with absolutely no opt-out mechanism.
That they are a for-profit company is completely irrelevant, as is whether or not they have a bug bounty program. Legal abstractions aside, it's still just people on both sides.
The expectation isn't that the poster work for free. The poster could have easily obscured identifying details and the content of his article would not be diminished. It is my opinion that if he wanted to "show his work", work done of his own initiative, then I think it would be more interesting and useful to include something about attempting to assist in remediation. I think, as mentioned by others, it would make a far stronger argument to click that "hire me!" button than anything in his technical analysis.
Of course automated systems are on the hunt for this stuff. Same with public code repositories, Docker images, and if you operate a subscription-based service with any popularity then your web interfaces for sign-up, login, etc will be subject to well-orchestrated brute force attacks. That someone did a poor job is all the more reason to avoid potentially contributing to their exploitation.
A response within the positive spectrum is absolutely above and beyond. Of all the feedback this community can provide, I think this is the most useful and I'm grateful that the poster has been responsive to it.
I look forward to the update and will be very curious to see how that goes. Best of luck!
[EDIT] Also I think it worth adding one more thing. I think the poster has demonstrated an openness to feedback that is wonderful. Coming back to the keyboard to read "let me give that a try; I'll update things" is really cool.
I've tried to be as careful as possible in my wording to avoid demonizing the poster. I still see absolutely nothing indicating maliciousness or ill intent and I would just as strongly disagree with anyone trying to do that. My apologies if I have come across as being hateful in any way.
I prefer to champion a web that goes back to a "hacker" culture I learned from in my youth that predates Internet culture: we believe DO owe each other something, somewhere in the positive gradient: basic decency, an assumption that we're all worthy of respect (unless proven otherwise), and that you never try to "score points" at the expense of someone else.
But that is just what I believe and what my preferences are. Certainly "do no harm" is the rock bottom line.
I have to say that if this is "showing your work" then the most important thing you've shown is poor judgement in publishing their secrets in a submission to a very popular website. The fact that they have followed such shockingly bad security practices themselves is absolutely no excuse.
The work I wish we saw was the valiant effort you made to contact the company and help them see their mistakes. That is an area where we can all use more good examples, even if only to show how difficult it is to get something so obviously problematic taken seriously.
I'm certain you mean no ill will, but the lack of consideration here is concerning.
[EDIT] As per the posters comments, the keys included weren't the real ones. I still think the point stands: they are trivial to obtain when you know they are included in the package so their exclusion only means so much.
Pucker Up - The Fine Art of Whistling
There is a short, but great segment where this is demonstrated with two men whistling across mountain tops to communicate.The film is filled with gems like one guy explaining as a compulsive whistler he got in trouble once for whistling a tune at a funeral.
You really can't "red pill" people, and the closer they are to you the lower the chances of success.
You can, however, ask (non leading) questions and listen. If you can't start by being curious, don't expect them to make that leap first... and thats really where you have to start before you can change your mind.
It's really not pretty what can happen when you have a juicy target, plenty of time, and a perfect idea of how you can use it to your advantage.
Fortunately they weren't at all malicious... just looking for ways to grow their little empire to play their war games and hopefully make some cash.
Maybe this is our version of the "infinite monkeys" thing: given enough software people, enough computers, and enough time, someone at a company will eventually grant universal remote root access to anyone who knows how to read some source code.
At one job, way back in the day, I had a dream that a shared web-hosting installer framework could give you root on whatever server hosted your stuff. Went to work the next day and indeed... it was true and trivially easy to exploit.Sadly, it was a custom wallpaper upload feature that ended up being the actual source of shenanigans. You get 3 guesses on what happened and probably need just one.
On the flip side, nothing seems more exemplified by humanity than a zeal for doing a thing as big and grandiose as possible: for curiosity, for business, for art, or just for sheer vanity.
I don't think we've seen how far those will take us yet, even w/o improvements to the bottlenecks you suggest. I do agree that those "meta" fields matter and will make a huge difference.
Two tricks in my bag for this:
1. Exactly you already said: "write a list of the steps you need to take and keep breaking it into smaller parts" :)
2. Play competing heel-dragging tasks against each other, when possible.
I find that doing this ensures that sustained effort is almost guaranteed to be more productive (and it doesn't take long) than trying to do a controlled, focused burst to get something out of the way.I don't doubt your point for a moment, but I think the author is taking a more literal, traditional approach to the word. In either case, it's a useful distinction around how people align themselves (intentionally or otherwise) around these geopolitical issues.
> How long does food in a freezer stay frozen when the power goes out
https://woodgears.ca/heating/freezer.html
I especially love this post and video showing a data-driven approach to understanding just how much it costs to stand there w/ the door open while you scan (again) for food that hopefully magically appeared since the last time you checked.Thus, drivers are employees of a bigger company who manages every other part of the economic relationship. Kinda like Uber (and Lyft, etc), but because "you can bring your own gear" people are fungible (nothing stops you from working multiple companies either) and subject to agreements that:
- Expose minimum liability to the company
- Provide maximum profitability to the company (even w/ surge pricing -- the house still wins)
- Minimizes extra legal obligations to employees
In other words, it's a game of "heads I win, tails you lose". If all goes well it's steady, relatively straight-forward (just do what the app tells you to do) work.The gig-taxi industry certainly doesn't stand alone and they have exploded over the last decade (and especially so in the last year). These jobs/companies do (and should) bring out a lot of strong opinions.
[1] https://duckduckgo.com/?q=new+york+city+medallions+auction&i...
Edit: to be clear, what makes this so unique is that there are significant safety risks inherit in the job (accidents, crime, drunk/offensive/dangerous/etc riders). They scale linearly with how much you do it and some times/places/events add multipliers to that.
We all have our blind spots, and they're always bigger than we think they are.
I'll heartily second that! I'd rather plop down next to a guy who can't stop talking about his favorite video game. At least they're sure to be talking about something they actually do and there is none of that ridiculous "we" talk.
And they aren't fooled for a moment that it's all just a game they're obsessed with.
Also, except for brief mentions of Flask/Django/etc practically nothing has anything to do with Python specifically. Python is useful in the areas mentioned, but this article contributes absolutely nothing to help understand that.
Nothing to see here; move along.