Hacker News new | past | comments | ask | show | jobs | submit | oasisbob's comments login

Everyone shares lists.

I have a politics label in gmail that is blue/red from 2012 onwards. All the GOP emails are from poking around Romney 2012, and nothing else.

I'd say you'd be surprised on the reuse, but you shouldn't be.


It's not just the re-use and sharing of lists, but also the incredible Facebook-style targeting available to anyone for spamming. Anyone can sign up for something like ActionNetwork.org or NationBuilder and send out an email blast to registered voters in a particular zip code. NGP VAN is even more powerful.

The whole industry is mature and super targeted like any other spammer, but mostly immune to spam regulations (because politics are specifically exempt from CAN-SPAM etc., and most voter registration and donation data is public record). The whole pipeline is thoroughly automated and you're marketed and remarketed to just like you are with Google or Amazon, but without any of the already-minimal consumer and privacy protections.


Their targetting is shit. The people selling the targetting capability are scamming everybody else. I get countless spam messages from both political parties, both seemingly certain that I support them. I never donated to any of them.

Good.

If the price of living in a democratic society with transparent voter/donor records is a few annoying emails, we should all be paying that price gladly.


I dunno if that's either necessary or sufficient... in a country with legalized bribery, billionaire presidents, SuperPACs and all sorts of dark money, I doubt that knowing Joe Citizen donated $27 is really going to save democracy.

Don't forget about infrastructure domains, static-asset domains, separation of product domains from corporate domains ... there are plenty of good reasons to use multiple domains, especially if you're doing anything with the web where domain hierarchies and the same-origin policy are so critical to the overall security model.


I don't think this is accurate - I have multiple MFA devices associated with all my AWS IAM users on multiple accounts of various ages.

AWS documentation specifies that users are allowed upto eight MFA devices each:

https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credenti...


Interesting, last I bothered with IAM users they were limited to a single MFA "device" virtual or otherwise.

https://aws.amazon.com/blogs/security/you-can-now-assign-mul...

Apparently I haven't bothered with them for a few months and didn't notice, glad they finally added it.


Oh I've either overlooked this too (2022, not just a few months) or there's some caveat like 'one of each type' or something.

Will have to try again. Presently have a user per key, named with the end of the keys ID so I know which to use, not brilliant but works.


GFCI requirements will interfere with the legality of many modern-day multi-wire branch circuit plans, yeah?


You can get a two-pole GFCI breaker for this purpose. The prices are a bit silly.


two poles breakers, 2×120V@20A, $USD:

    - $20
    - GFCI, $115
    - GFCI + AFCI, $115
Yes it is expensive, but it can also save your life.


Many things can save your life. Most of them don’t have a UL-provided monopoly making it quite unpleasant for anyone to compete to produce the version that fits where you need it.

A 1-pole GFCI breaker, a 2-pole GFCI breaker, and an ordinary GFCI outlet all have the same clever pair of coils, the same IC, and rather similar trip mechanisms. Yet the costs are quite different, and the costs get _really_ absurd if you want a breaker that trips at a level other than ~5mA.

And yes, they’re all very much worth using. I do wish that electrical codes would at least start encouraging the use of GFCIs for 240V outlets, which might encourage manufacturers to start making them, and those would actually be able to compete with each other.


Additionally, with early pioneer logging, another solution to avoiding having logs which are too large to handle was to not drop them in the first place.

In the Pacific Northwest, US, early loggers would leave the huge ones - to the point where pioneers could complain about a lack of available timber in an old-growth forest.

When the initial University of Washington was built, land-clearing costs were a huge portion of the overall capital spend. The largest trees on the site weren't used for anything productive; rather, they were climbed, chained together, and domino felled at the same time. By attaching the trees together, they only needed to fell one tree which brought the whole mess down into a pile and they burned it.

I think there's a lesson here about choosing which logs you want to move.


That's an interesting tidbit I did not know about UW. Sad the wood wasn't used.


Having not read the article yet, this was one confusing comment until I realized by "logging" you meant actual trees and not log files.


The "to record an event" meaning of logging does in fact originate from wooden logs, which were used to calculate the speed of a ship under sail. A log, tied to a fathom-line, was cast off the stern, and the number of knots which passed through the sailors hands in a measured time interval determined the speed. This was recorded as "log", in what came to be known as the "ship's log". The term came to be used for event recording in general. This was used as a component of "dead reckoning" (that is, deduced reckoning of position) in navigation, prior to the development of accurate time-keeping and direct position reporting through LORAN, radar-navigation, and ultimately GPS. Dead reckoning was not especially accurate and had some rather notorious failure modes.

<https://www.etymonline.com/word/log> (definition 2)

Chip log: <https://en.wikipedia.org/wiki/Chip_log>

Dead reckoning: <https://en.wikipedia.org/wiki/Dead_reckoning>

Scilly naval disaster of 1707, in which four warships and 1,400 to 2,000 sailors of the British fleet were lost in a single navigational failure: <https://en.wikipedia.org/wiki/Scilly_naval_disaster_of_1707>

This directly inspired the Longitude Rewards prizes for developing accurate navigational methods (<https://en.wikipedia.org/wiki/Longitude_rewards>) and John Harrison's invention of a marine clock (<https://en.wikipedia.org/wiki/John_Harrison#Longitude_proble...>).

More recently, the Honda Point disaster in which the US Navy, 1923 saw the loss of 7 destroyers at flank speed of 20 knots off the Santa Barbara coast: <https://en.wikipedia.org/wiki/Honda_Point_disaster>.

It's interesting to note that advances in timekeeping typically translate to improvements in location determination.


Perhaps an analogy can be made with respect to information priority and which trees to fell.


This may vary a lot by bank.

At the small regional bank I used to work for accounts were assigned a home branch, typically where the account was first opened, and that branch had enhanced responsibilities in terms of servicing and maintaining the relationship.

Chase is big enough that their KYC fallout queues probably have an entire team working them, and it wouldn't matter who else you CC on the email.

("Hey Joe, come quick! Just got an email from someone claiming they need their money we just froze...")


> Chase is big enough that their KYC fallout queues probably have an entire team working them, and it wouldn't matter who else you CC on the email.

The trick is to become so incredibly annoying that some CxO / VP is going to bump you ahead in the queue and assign a dedicated customer experience manager.

Personally, if a bank were to steal $180.000 of my money, a few weeks in I'd probably start considering sticking "Chase is a criminal organization" posters on the doors of their regional headquarters, or getting tickets to industry events just so I can ask them at the Q&A where my money is. They may think "computer says no" is an acceptable answer, but that doesn't mean I can't make their life a living hell too - so why not make my problem our problem?


>The trick is to become so incredibly annoying that some CxO / VP is going to bump you ahead in the queue and assign a dedicated customer experience manager.

Hard to be annoying when they can just completely ignore and redirect it to /dev/null


It gets a lot easier to be annoying when you add meatspace antics to your portfolio.


> Yes officer, this neerdowell right here.


There's quite a lot you can do which isn't illegal, but is incredibly annoying. Such as renting a billboard on the CxOs daily commute route or near their golf club. They might be able to personally ignore me, but can they also ignore their golf buddies asking questions about it?



> Chase is a criminal organization

This should be your operating assumption from Day 1.


But this isn’t a KYC issue and clearly escalating worked.

Any time I’ve ever had issues that weren’t resolved within 24hrs by t1 support I’ve sent a succinct, mostly emotionless email to anyone I could find and it’s worked every time. Phone companies, banks, hell even the government.


Can confirm KYC really helps (in reverse) at small/regional banks. Shout-out to Midfirst Bank https://www.midfirst.com/about-us for walking the walk.

I deliberately flow a higher percentage of transactions through my, literally 10 min walk away, regional bank branch. I also occasionally (~once/month), literally walk into the lobby (shocking I know) to say "hi!" when withdrawing cash at the ATM for travel.

They know me by name & face. I'm not just a number to the tellers, the manager, and the vp, and likewise back to them.

Shockingly, I get fees waived for wires the occasional cashier's check, and am appraised of anything else going on with the website, upcoming services, and pending transactions (even at high relative holding percentages from one-time routes) flow through like butter.

Relationship banking at its finest.


> What's worse than a toast? No feedback at all.

I'd argue that the YouTube iOS app found a more worse toast: the confirmation toast for removing videos from a playlist covers the original menu which triggered the action in the first place.

Makes it very hard to perform the same action repeatedly.


Noticed a new-ish behavior in the slack app the last few days - possibly related?

Some external links (eg Confluence) are getting interposed and redirected through a slack URL at https://slack.com/openid/connect/login_initiate_redirect?log..., with login_hint being a JWT.


Multicast too. If you've never needed to manipulate ACLs for multicast traffic, you're not really living.


Asked to print a 300,000 page PDF you say? Almost sounds like it was meant for this guy:

https://www.psihoyos.com/image/I0000jtF1ui2j79Q


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: