Browse files

Initial commit: what if the newest toots are at the BOTTOM instead of…

… the top?

Currently implemented as a site style, eventually I hope to make this be a switch somewhere in the settings.
  • Loading branch information...
egypturnash committed Nov 14, 2017
1 parent 581fee2 commit 611434bdfd4125d4ab6434d203fc98f84c1e35d7
Showing with 31 additions and 0 deletions.
  1. +29 −0 app/javascript/styles/backwards.scss
  2. +1 −0 config/locales/en.yml
  3. +1 −0 config/themes.yml
@@ -0,0 +1,29 @@
@import 'darkwide';
* we put the newest toots at the BOTTOM of the timeline?
* We have gotten used to reading twitter conversations in reverse order.
* We all hate doing this. Or at least I do. But it's How Twitter Works.
* Twitter has tried to fix it, with that thing where they detect a conversation
* and glom all the relevant tweets together.
* But their timeline is still resisting this.
* What if we change this?
* It kinda makes my brain hurt, at first. But I'm gonna stick with it a little while.
* "I don't understand! The sound waves are reversing!"
* - Man or Astro-Man, "The Sounds Of Waves Reversing"
[role=feed] {
/* this is a terrible kludge but it will do for now until I have time to dive into mastodon's js and change it to add new toots when you get to the TOP of the */
[aria-posinset="0"]:first-child, .account-timeline__header {
@@ -590,6 +590,7 @@ en:
title: "%{instance} Terms of Service and Privacy Policy"
default: "Soft Rumblings in a Quiet Cavern"
natural-order: "The Sounds of Waves Reversing"
mastodon: "Mastodon Default"
@@ -1,2 +1,3 @@
default: styles/darkwide.scss
natural-order: styles/backwards.scss
mastodon: styles/application.scss

0 comments on commit 611434b

Please sign in to comment.