Sabine Hossenfelder
| Celebrity |
German theoretical physicist |
| User | Typing | Confidence | Alternative | ||
|---|---|---|---|---|---|
|
Analysis updated 5 weeks ago |
Science blogger. Along with Peter Woit, Hossenfelder has emerged as one of the leading skeptics of string theory. She derides the widespread groupthink present in the theoretical physics community (which has attracted a lot of controversy), while not advertising much of a commitment to any particular research program of her own - in any case much of her public-facing content is about tearing down bad ideas ("gobbledygook"). Wrote a whole book about how the failures of fundamental physics are because of an over-emphasis on mathematical elegance (a point that Woit disagrees on by the way). Has also been outspoken against the idea of building a bigger supercollider due to viewing it as a waste of money and resources and essentially propped up by promotion by particle physicists who are complacent with existing methods (which largely have not worked). Has gotten a lot of people mad by delivering her criticism of the community in a persistent and less than diplomatic way. Used to make YouTube videos where she sings original songs or reads her blog posts verbatim, because it's easier to get new followers on YouTube than on a blog. Now she increasingly devotes more and more energy and thought into promoting her YouTube content and has been successful as a popsci Youtuber, albeit a more technically oriented and dry one than something like VSauce. Her videos are less awkward now although they are still put out fast with minimal editing and a few images being edited in for humor. Has made some more interesting and constructive suggestions about how to improve metrics and hiring in physics. While ILI is a reasonable alternative, I think her career progression over the last few years into a relatively popular content creator amply proves that LIE is preferable. |
||||
Keyboard navigation
| j | move down row |
| k | move up row |
| t (or d) | edit type |
| T | edit subtype (wing) |
| c | edit confidence |
| a | edit alternative |
| A | edit alternative subtype (wing) |
| v | edit visibility |
| g | go to top |
| G | go to bottom |
| s | open subject page |
| y | show or hide analysis* |
| m | show or hide comments* |
| esc | leave editing mode |
| D | delete typing, if possible (confirmation required) |
| P | previous page |
| N | next page |
| / | go to search bar |
| ? or H | toggle help |
*An analysis or comment being written still has to be submitted by hand
Markdown syntax
Markdown syntax is used for comments, analyses, About Me's, and forum signatures. See here for how Markdown generally works.
Some parts of Markdown are not used on Sedecology. Embedding images is disabled, and you can't use HTML tags. Headers are limited in length to avoid abuse of the large text.
Replies and mentions
Highlighting syntax (==text== with two equal signs on both sides) is repurposed for replying to comments and analyses. The first number that occurs inside will be interpreted as a comment id, unless it is preceded by A or A# in which case it will refer to a typing that has an analysis attached. The output will show the person you're replying to and everything other than the number will be ignored.
Currently notifications are sent for mentions and replies but only inside comments, not analyses or About Me's. For this reason, when you quote something the reply links will be escaped like ==/text== and the mentions will be escaped like @/user -- the links will still work but the slash will deactivate the notification. You can add a slash yourself too, if you don't want to bug people. Only a limited number of notifications will be sent per comment. Editing a comment updates the forward links but will not send new notifications.
Cross-thread replies are also fully supported.
Spoilers
Spoiler syntax is like ~~this~~ (which is normally the syntax for strikethrough), it is toggleable and will also be hidden with [spoiler] in the event feed which does not normally render markdown. Spoilers can go across lines in the markdown but cannot include an empty line (which separates paragraphs).
Other
Basic features like bold, italics, quotes, and links will probably stay the same, but other syntax may be repurposed or disabled in the future, such as indented code blocks and backticks.