As this article is actually on-topic, then it’s most likely because it sows internal discord.
Like most minds, the HN hive mind prefers to deny and suppress in response to various forms of cognitive dissonance, such as that which arises when one’s actions (or inaction) contradict one’s stated beliefs or morals.
HN also isn’t one for conscious introspection (ie meta commentary). Your comment and my response are generally no-nos.
“Vannevar Bush's 1945 article "As We May Think". Bush envisioned the memex as a device in which individuals would compress and store all of their books, records, and communications, "mechanized so that it may be consulted with exceeding speed and flexibility".
The memex was a deterministic device to consult documents - the actual documents. The "LLM" is more like a dumb archivist that came with it ("Yes, see for example that document, it tells you that q=M·k...").
I grew up with physical encyclopedia, then moved on to Encarta, then Wikipedia dumps and folders full of PDFs. I still prefer curated information repository over chat interfaces or generated summaries. The main goal with the former is to have a knowledge map and keywords graph, so that you can locate any piece of information you may need from the actual source.
A Texas court reduced the viability of the business with one of its rulings. This meant that Intellectual Ventures had to spin out a bunch of companies to actually defend the patents they held. I believe they had mixed success. An example is Pivotal Commware.
There should be an IKEA for medical devices relying on scale to absorb design, testing and regulatory compliance.
The AirPod hearing aid feature and other OTC hearing aids from headphone manufacturers demonstrate it’s possible to leverage modern consumer electronics improvements for devices with a higher engineering barrier to entry than a wheelchair.
I think paying a premium for anything via insurance is detrimental to markets and only benefits bottom feeding bandits and deferring or deflecting the cost.
I'm really curious about the hearing aid feature, but haven't seen any review actually featuring a patient using it in a real world situation. I was assuming there would be pre FDA approval reviews, but doesn't seem to be the case.
The older accessibility feature didn't seem to be that great, and I'm pretty eager to see how much it improves through the complete revamp of it before throwing money at it.
It's crazy, 400,000k per person. It would feel like nothing but an unfair waste of my "cheap-country" money to fuel "overpriced-county" with a donation.
But that's not salary, that's the total cost per employee. So if you factor in ~40% cost for healthcare, pension, perks, and various taxes, then the average salary is closer to $240,000 which will still a bit high, is probably less than market for the average engineer working at the company.
Per the 990, which is just salary, multiple employees at Signal are getting paid over $650k. That's way above market for the nonprofit sector for comparable positions.
From page 2 of Schedule J (at the bottom) they break out the components of the compensation, showing that most of those numbers incorporate a base salary that looks fairly normal with 2-600k of bonus & incentive comp on top.
In curious Googling to see if there was an explanation for how their structure works, I stumbled on this interesting Glassdoor review:
> The bonus structure promised up to a 100% match with salary, but in practice the system was set up so that nobody got more than 50%, if that. Had I understood this I probably would have taken a competing offer that ultimately would have had much higher comp.
> The quarterly cliff on the bonus system, where a feature failing to ship within the quarter specified (even if just by a single day) was counted as if you hadn't done it at all. This led to death marches each quarter as everyone scrambled to try to finish unrealistic goals. It wasn't possible to get help from anyone else at these times since of course they too had the same problem.
> Nominally, the quarterly goals were set in a collaborative process. In practice it was a 2 day full day meeting where we were told what Moxie had decided we were going to do - our input wasn't really considered at all, including if it was even viable to complete in a quarter. I'm fine with top down control, that's how most corps work, but I disliked the false patina that this was some democratic process.
> Internal communications are a disaster, because Signal uses Signal for everything, including things Signal isn't at all designed for or good at. Bug tracking is literally done in a giant group chat. I have a newfound appreciation for JIRA.
After a few hours of reaching out to people about this, the Signal salaries appear to be grossly inflated not only compared to other non-profits, but to what engineers working on iMessage and Meta Messenger make for the same or more difficult work (considering that both of these competitors many several times the users as Signal; Meta Messenger has over 1 billion users).
When combined with the rate limiting on 365 email api and ultimately removing imap access this seems like a strategic goal to capture our data.
The dark patterns pushing content to one drive from office apps and web access opening attachments and keeping them in one drive is another example of this data grab.
It’s an example of shareholder value trumping customer value, the primary purpose of cloud is to make you pay more without having to provide more in return.
> When combined with the rate limiting on 365 email api and ultimately removing imap access this seems like a strategic goal to capture our data.
While I agree with your other points, I'm not sure how this one works. If you're using Office365, you're already having your mail at least go through their servers. What difference does IMAP make to their snooping intentions?
This attack targets people's personal accounts. Many people have Office 365 because their work requires it, so they have to use the Outlook app for that. So if those people then choose to add their personal account to the same mail client, Microsoft can also snoop on the private correspondence of their captive corporate audience.
The majority seems to like one-drive. In theory having everything in one place sounds great. Few people think long term. Customer value trumps customer value if you ask me. IT departments and clueless users love MSFT and that will never change. Embrace it.
Hi, Brian from Rollbar here. We believe that the items listed comprise the entirety of the scope. We will be able to state definitively once forensic analysis is complete.
GitHub tokens are not exposed. More specifically: customer credentials stored for third party integrations (i.e. GitHub, Slack, JIRA) are stored encrypted using a key that is not stored in the database, so those are not exposed.
