fulldecent

I read this article and found it to be a great example of why we should NOT adopt modern PHP techniques at our company.

50 lines of code and contrived examples (is HelloWorld class a view or controller? AwesomeClass is a model?) get one line of HTML emitted in a barely readable way.

This article fails to motivate why each layer of complexity is added. It basically starts with the assumption that you want to use a framework and says "hey look you can do the same thing with 50 lines of boilerplate, not really, but kind of."

I would be much more impressed with an article that starts with the obvious way to write a PHP application (.htaccess, index.php, products.php, library/database.php, library/*.php) and then explains the actual problems that would make you want to opt for more complexity/organization/modern techniques.

The (perceived?) reality is that social grows your user base and RSS doesn't.

Publishers care about growth more than serving existing customers.

A visitor that comes to your site via social is MUCH more valuable than someone that comes via RSS. The economics of this reality are what removed RSS from the limelight.

Dear publishers, let's fix this. Whenever you publish a blog post, etc. please syndicate it on social and then go back to your site to add "DISCUSS THIS ON TWITTER/whatever AT https://t.co/aesou02". Make sure that this also syndicates to RSS.

Dear pubsubbers, let's fix this. In your reader software, please lint these special links and show the discussion below the news. We know you want to get into the content discovery business -- this is the first step.

See the Slashdot RSS feed as a good example, they inline the discussion right in the feed.

Or how about the AM radio transmitter that is built into all x86 hardware - https://github.com/fulldecent/system-bus-radio

Still no first-class SFTP support. Doesn't look like I'll try VS Code until at least 2019.

This article could be more clear in showing who it is addressed to.

"How to Make the Most Out of Pull Requests -- a guide for project maintainers" or "How to Make the Most Out of Pull Requests -- so that your contributions get accepeted"

I just want to say when iPhone supports external flash I will probably never use Canon again. And I've used it for 10+ years professionally in the studio. Seriously, it's like Japan's products are moving at the same speed as their economy, i.e. not at all in the past 20 years.

1/4" mount with no anti-rotate hole.

I have a 80D and there is a 1/4" mount at the bottom. But if you take a photo in portrait orientation with a long lens then the 1/4" bolt will not be strong enough and the camera will twist out of it. It's a joke!

FYI, here is more analysis on the reality of "recruiting by grep". https://fulldecent.blogspot.com/2010/10/classic-and-modern-j...

Under the section Keyword Stuffing.

My company does $1m in sales annually. Stripe requires 7 days to close payments (versus 1d for other merchant accounts).

The extra $16k of float that Stripe requires is not worth it for me. This is why we have credit card numbers come to our server.

Before all the thought experiments, which I'm sure will ensue below, I just want to ask. Is it possible that men and women are actually different?

(The `flag` button above to mod this comment into oblivion.)

Is it just me or does anyone else think this will be a lame project just because it of GNU stewardship?

Please explain what you are seeing.

Also note that learning is a slow process. Please play multiple times while thinking about the same object to make an impact.

Thank you, I have made the update and it is live now.

TLDR. Was any of the information non-public?

There are lots of great example replies here.

I miss using machinations in MS Access back in the day. Now with Google Sheets, I am left wonting for a tool that enforces primary keys and is /easy/ to set up a view or query.

If they're paying rent I suppose I can't complain. All my projects are on GitHub.

Thanks for understanding. I was writing this up and wasn't sure anyone would really connect with the story or care about one line of code against a now non-existing broker. I'm so happy to hear this support.

Penson created the system that multiple brokers use for multiple branches.

I cannot verify that number but I am quoting it from a phone call with a Penson engineer.

Just FYI, I use the uBlock Origin extension for Chrome and I believe it solves all this for me.

Only briefly mentioned in the article:

2017 I have yet hear from FINRA that any action has been taken. I have yet to hear from ZECCO / TradeKing that the issue has been resolved.

I have closed my account and do not know the answer. Also, please if someone would be able to confirm in the affirmative in this or any other Penson site, then please start a new round of responsible disclosure.

Very nice LOL here.

Native English speaker. Very jet-lagged. Posted from Doha airport and blogspot.com kept redirecting to that other domain. Thank you, I have made many corrections now.

Thank you for taking the time to reply. @jacquesm, @komali2, @LanceH, I have made many typographical corrections and given you credit where due.

I realized that life is shorter than I expected and I started putting some affairs in order. This is something I had wanted to do for a while and now any consequences are less important to me.

YES. Many authors love to write more than the readers love to read them.

FIRST, be reasonable. This is a good life axiom. Don't expect a large organization to confirm, engineer, test certify, and deploy a change that requires external documentation in less than 14 days. Even if the ship's on fire.

SECOND, be valuable. If you are reporting a vuln that is a bug report. When's the last time you got thanked for /any/ buy report for a non-GitHub project? If your report explains the cost and liability for lawsuit if they fail to fix your reported vuln then you are speaking their language.

---

I have a confirmed vuln reported to Apple under their "responsible disclosure" program since 2015. They have yet to fix it or provide credit as they promised. If you thought Apple was a magic company that "does the right thing", then I hope this dispels that myth.

That's how I started the discussion with Zecco. The next phone call had the FBI on the line. Then I signed the NDA.

Next time I would change 30 to a reasonable number. In this case (multiple vendors and a large installed base) maybe even 180 days may have been fair. And then I would stick to my guns.

Also, the company was sold. Not class action, but if they did not properly disclose this then there could be liability there.

Surely Raneri had no authority to speak for FBI.

BUT actually this vuln may have been from upstream with Penson. And then it may affect many broker-dealers. They have many clients in US and Canada. (Don't laugh that such a ridiculous vuln could be in so many places.)

At the time, considering this (and Penson was on the phone) I understood that irresponsible disclosure could have serious consequences. FBI would have been warranted to knock on my door.

That's why I'm now publishing 10 years after the fact.