Hacker Newsnew | past | comments | ask | show | jobs | submit | flavien_bessede's commentslogin

Updater | Lead Data Analyst | Oakland, CA or New York, NY | Onsite | https://www.updater.com/

Updater makes moving easier for the 17 million households that relocate every year in the US.

Job posting with more details: https://boards.greenhouse.io/updater/jobs/1845916


Updater | Lead Data Analyst | Oakland, CA or New York, NY | Onsite | https://www.updater.com/

Updater makes moving easier for the 17 million households that relocate every year in the US.

Job posting with more details: https://boards.greenhouse.io/updater/jobs/1845916?gh_src=88f...


You can disable it in your settings, if you hated it so much you would have spent the 30 seconds it takes to get rid of it :)


Read my post, that isn't true.


Read my reply, I'm talking about settings, not dismisses.


There are two aspects to the feature. There's not a setting to disable that one. I've disabled the setting that does exist but the while-you-were-away version of the feature persists.


It's disabled in settings. They periodically re-enable it, it's a very user-hostile behavior.


I'm going to expand on this. There are two distinct annoying features.

1. The one you're talking about, messes up the chronological order of the timeline completely. That one is called "Show me the best Tweets first", in settings, and I have disabled it. Some people report Twitter flips the switch whenever they see fit, but that has never happened to me.

2. The second one is a small widget that appears at the top of your timeline that says "while you were away" and shows three tweets. There is no way to disable this. This is what it looks like on a desktop: http://i.imgur.com/R6rPRGo.jpg There are similar ones for mobile. I don't personally care too much about it (I close it... just one of hundreds of annoyances I have to put up with when I use a computer) but there's a huge problem: those three tweets are removed from your timeline, wherever they were. So they mess my timeline up (someone might have tweeted two things in rapid succession, and one of the tweets goes missing because they move it up to that widget). And there is no way to disable this, at all.


I believe that even when you dismiss the recent tweets box, the tweets still don't return to your timeline.

It's baffling bad.


Yes exactly. It's embarrasing. Those tweets are just removed from your timeline and there's no way you can make them return. For someone like me who follows just a few people and intends to read the entire timeline, it is very very bad.

That's their core product there and it's broken. And they don't care. I miss the twicca days... That's the Twitter I liked, a chronological stream of text. I mourn for it.


It's also one of very few changes I've seen (one of which was changing the icon and word for the favorite/like action [which was a breaking change as far as I'm concerned; it changed the semantics of past discussions and eliminated the personal bookmarking aspect]).

I cannot imagine what Twitter is spending its time doing.


Twidere for Android is a great client that respects chronological ordering, saves your previous position, and doesn't show ads. I don't know of a desktop solution. I just put up with their shitty website and avoid it whenever possible.


There's no way to disable that feature.


So what happened between the Big Bang and Earth formation? For some reason I always thought they were one and the same.



The Big Bang was the formation of the entire universe. About ten billion years later, our solar system, and eventually the Earth, started forming due to gravity pulling various bits of matter together. Ten billion years is a really, really long time! The two events are completely separate.

If you're interested in cosmology, there are a ton of fascinating popular science books on the topic, and research is very active and ongoing. As an introduction, I recommend Cosmos by Carl Sagan. It's a bit outdated these days, but the main points hold and it's a fascinating read from start to finish. Alternatively, if you prefer video, check out Cosmos: A Spacetime Odyssey with Neil deGrasse Tyson. It's an up-to-date retelling of Sagan's original idea.


Come on downvoters, it's a naive question, but not the sort of thing that needs to be punished...


Two generations of stars, including heavy stars that produced all the elements up to iron (including, relevant to this particular case, oxygen), and then became supernovae, which a) produced traces of heavier elements b) blew a lot of stellar material out into the universe, to become part of new star systems. So there was oxygen around by the time Earth was formed (~4.5 billion years ago, as opposed to ~14 billion for the big bang).


CRC's GED prep book used to contain this error. Most of the book was good but the "Earth Science" section looked like it had been deliberately mangled in order to discredit opponents of creationism. Or that was my theory, anyway, it was pretty bad.


If you want to learn more, this is a valuable resource: https://www.bighistoryproject.com/ .


The Cosmos series (either the old Sagan one or the new Neil DeGrasse Tyson one which is on Netflix) covers this in a very nice format.


Distributed systems design aside, the core of the problem is that they relied on ntp (as they probably should), and in their case ntp was not working properly.


The key take away from the article SHOULD be: don't rely on ntp if you don't have to.

There are people who have to. They run their own atomic clocks, and worry about things such as precision delivery of nuclear ordanance.

Then there's you. You should use vector clocks, with a builtin conflict resolution mechanism based on domain knowledge.

That's the point of the article.


And this is precisely why a thing that is not monitored is not actually a thing.


> "A thing that is not monitored is not actually a thing."

That should be on a cross-stitch sampler on the wall of every NOC.


Nice. Much stronger than the "you can only manage what you measure" adage I learned from accounting.


Even if NTP had been working properly, you would not have clocks synchronised at the level of individual ticks - only to the level of time intervals. If two updates happened at roughly the same time, and fell into the same time interval, there would be no way to tell which one happened before the other. A paper by Cilia et al on timing of composite events in distributed event-based systems using NTP deals with this issue.


But this is not a problem in many situations. Whereas successor writes failing within an entire 30 second span is a pretty big problem.


Ntp is good. Assuming that time is coordinated, much less monotonically increasing, is a bad plan. Just the other week i got paged in the middle of the night because a clock moved backwards.


Insane metrics? They might have a lot of shares but only 50 millions monthly active users ...


Feature idea: Offer to take the screenshot from different OS/Browser!


Am I the only one here that think this system won't scale?


Why do you think that?


The entire workflow of managing more than one write-up needs some more work. Few examples:

- if you come back and try to edit a write-up you'll have to first open the preview then remember the shortcut to edit it, not really another way around except maybe changing the URL.

- if you have more than one write-up with the same name, you don't really know which one you are on right now.

- deleting the write-up is kinda confusing too. and you can't delete on the view mode.

- shortcuts gets mixed up between control and option.

But overall love it and will try to write more with your help!


tl;dr


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

Search: