2,269 karma · joined October 5, 2010
Let me assess this, with the tip of my napkin:
1. linkedin 'firebase' + amazon (current employer) -> 695 people.
2. 10% of above = 70 FTE
3. They started (googled): They founded Firebase as a separate company in September 2011 and it launched to the public in April 2012.
1+2+3 = It's impossible you will have feature parity in next 10 years.
BUT it's possible you can achieve pareto parity, leaving off the table most complicated 20%. Good luck :)
This Uber trick: taking % of the revenue for the fixed cost service (they provide to the taxis drivers ) is the master trick making uber money.
So far, in Europe, all taxi corporations charge taxi driver FIXED (quite small 100..200 usd/month) amount for operating telco/web/radio and coordinating fleet of taxis.
Uber's ability to push bulshine here is really business milking 101 course: Fixed costs, uncaped incomes.
Could you please explain/point me to some information/source, why docker can't use -net=host namespace if userns is enabled, while on the other hand rootlesskit[1] which uses userns by default, dont have problem with using host netns (--net=host) ?
I'have two family members which were offered the same pricing, BUT with terms clearly stating that 'google reserves right to change price any time' on the new youtube service.
I have this confirmed with YT/Google support tickets.
WFH will strip 'friendship creation factor' from work. Definitely not to zero, but it will in effect reduce fun from work because 'working with friends' will be less often (unless you start work with people you're already friend).
it's fired, not furloughed.
it's to be able to not lose ability to generate profit, not "to be able to serve our customers"
it's to save 85% who we think are more worth, not "we are all in this together"
otherwise is clickbaity.
what they're planning now to do is to invent completly new business, utilising assets they have at hand (relations with hosts, but this is it).
their 'online experiences' is a lesson on 'wishful thinking' or 'painting the grass green'. Quoting article: "we have nearly 100 hosts offering experiences online and thousands more who’ve offered to host experiences".
Let me remind them, that they have at least THREE..FOUR ORDERS OF MAGNITUDE bigger hosts number (problem 1), there is no space in youtube/twitch area for that amount of content creators (problem 2), and most hosts can't do it (problem 3).
Why rewrite you ask?
npm install gives: added 509 packages from 307 contributors and audited 258096 packages in 11.65s
509 packages WTF?!????????????? Javascript ecosystem is a mess.
I did not believe it, but looks like it's true: `npm ls |grep -v deduped |wc`
512 3359 24956
56M !?!?!?!?
and final check: `find node_modules -type f|wc `
6745 6745 303596
p.s. among them 6 warnings about using sth deprecated. You can guess how many of 500 of them just dont give a shi^H^H^Hwarning.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^2.1.2 (node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
I received an update from our specialist. To set your expectation, we understand that you want to keep the old pricing for your membership. However, as per our specialist they no longer have a link that you can regain the promotion pricing. To compensate this, we'll grant you a 3 months free time for your membership.
WTF Google??!?!?!
I of course rejected their "offer" and asked to reinstate things as they were before their mistake, I'm now waiting for their response.
As someone wrote, this might be dark pattern of 'how-to-get-rid-of-lifetimes'. I'm really disgusted by Google.
Anyone can help on this?
2. Did you have the original grandfather plan of Google Music?
3. Besides, YTM does not have guarantee of lifetime price.
Upon contacting support, the only remedy they offer as for now is to subscribe to You Tube music (higher price and no lifetime guarantee) and are 'investigating' while of course they hadnt provided any solution.
Additional info:
* you did not get ANY information about this cancellation, up to the moment people starting flooging their support which was yesterday :)
* at that moment, you probably got two cancellation mails without any usefull info
* this is Google problem/action (not known atm), not your bank or CC
Additional info v2:
* Google did NOT try to do monhtly charges for the service on the usual date, bank/CC confirms NOT a single charge attempt until, YTM resubsbription on support request.
* The problem affects probably (?) subscribers with renewal dates between April 1st and 12th (incl.) as on 13th Google noticed problems and stopped "auto-cancel-feature".
Additional info v3:
* Looks like that only some subscribers (Europeans for sure) were affected by it, so smaller impact, maybe related to country of subscriber (unknown atm)
* It was probably part of the glitched (?) and multi-steps transition of google music to youtube music services (speculation atm)
Omnifocus 2 was a joke in any category, while I have mixed fealing about 3 (speed, ergonomics, features).
Anyone want to chip in? :)
One thing which I'm also analysing recently is electron shit^H^H^Happs, triggering XSS (X screen saver) idle detection on some internal app events (not user actions!).
Being: if you dont move mouse, nor touch keyboard, plus you're receiving slack messages, XSS considers youre NOT idle, in result not allowing lock to work if relying on xss-idle-detection.
needing it as I'm expermineting with some cool X11 software from 199x. I added XSS support, as original detection engine(*) dont work reliably on modern X11.
Anyone?
moral bonus: ability to 'explain' it that is just because you can claim unemployment benefit.
I don't have problem with netflix reducing it. I have problem with netflix not reducing price together.
They're essentially painting themselves in glory AT THE PRICE OF THEIR CUSTOMERS.
Bug is open already for a year :-(
P.S. 1password has it.
I just verified every single post of you on hackers news in last 12 months, and every one, in different DB discussions are doing the some shamefull plug about Realm.
E v e r y o n e.
And not a single disclaimer from you, not to mention some of your posts (like here, what janl pointed) are simply not true.
Disgracefull. I'm leaving this comment for anybody in the future doing check on you to notice this.
And by "one from North Dakota" he means "only in departament of immigration" of them.
Paul Graham wrote: never do things for money or ego, but techcrunch clickbaiters writing about facebook employees, sorry, founders, supposedly dont agree.
P.S. this whole title reads like from git manpage generator.
Telegram crypto was redone, and is now using standard primitives. You can verify it at high level at https://core.telegram.org/mtproto or low level if you'd like to check sourcecode in their github. BTW, telegram has reproducible builds since last year.
I'm tired of people repeating 7 years old meme without verification.
ad1: starting from quite a long time, secret chats use MTProto 2.0 which is build on stanard crypto primitives you're seeing everywhere. Read it here high level: https://core.telegram.org/api/end-to-end and free to verify on github.
ad2: this is not true, and is discussion about user choice, not security.
please do not spread false old information. world changes.
p.s. and is based on information which in 2020 is not anymore actual as most things were corrected.
Down there, 2/3 of this hackersnews discussion (if you are patient to get there) you can see questions about production deployment of btrfs, with some VERY interesting answers of BIG deployments of btrfs. Read success confirmed with data. My takeaway from reading whole discussion:
* lot of people (individuals) praise of btrfs
* lot of people (ind.) tell about problems
* quite nice features/btrfs usage patterns, not matched even by zfs mentioned
* still for VM/DB you shall consider different approach (thin LVM + xfs or ext4) and slave machine WITH btrfs and snapshots on it
* quite many problems/deficienses of ZFS mentioned (apart fomr typical license/kernel inclusion)
* lot of new features on the way in recent kernels for btrfs
* btrfs is not dead
p.s. worth to comment that kernel 5.6 just received another huge new features batch for btrfs (async discard!)
Also: could you write which models of components you bought:
a. 580 gfx card ? /nitro? pulse? others :)/
b. in terms of 5700 youre planning to buy do you have exact model?
c. which exact memory (size of one) and 3600 was base or overclocked
If you look for really FAST and streamline solution (one binary), check this post: https://michael.stapelberg.ch/posts/2020-01-21-initramfs-fro...
My quite large 1tb multivolume, multisnapshot BTRFS fs never had any problems.
And it's quite aggressive cfg (big fs commit).
P.S. I do have backups though.