Conversation

Notices

  1. The Cabal has arrived.

    Monday, 04-Apr-11 23:23:56 UTC from web
    1. @widget I could've sworn I fixed that. Hold on a tick, I think I must've not committed a change somewhere.

      Monday, 17-Sep-12 00:14:04 UTC from web
    2. @widget http://stackoverflow.com/questions/1223354/undo-git-pull-how-to-bring-repos-to-old-state (Explains it much better than I could possibly do within the limits of this text field.)

      Monday, 17-Sep-12 00:20:13 UTC from web
    3. @widget Also, I found the problem. Pushed the fix now, and it seems github automatically rolled it into the pull-request. I'm not entirely happy with the solution, since calling profile links notices is semantically hairy, but evidently the actual .profiles selector was coming from either the theme or RDNPlus, not the base setup, so I can't use it without hacking up the CSS and hoping all the themes do too.

      Monday, 17-Sep-12 00:24:36 UTC from web
      1. @bitshift ...What _are_ you doing with it, by the way?

        Monday, 17-Sep-12 00:25:41 UTC from web
        1. @redenchilada Making the "new users"/"popular groups" sections not be <table>s (since all the other similar sections are <ol>s), and as a handy side-effect fixing the thing where their links overflow without having to add another CSS rule.

          Monday, 17-Sep-12 00:27:05 UTC from web
    4. @widget Yeah, it's nice. Also shows all refs rather than just the ones that are parents/grandparents/etc. of the current HEAD, which can be handy if you manage to really mess up your repo somehow.

      Monday, 17-Sep-12 00:25:28 UTC from web
    5. @widget Yep. There's literally only one change in the new commit, so it should be pretty easy to see if you have it locally or not: https://github.com/bit-shift/rainbowdash-network/commit/bc2a093f63e020ff608cfc145a89a37bbc627e4d

      Monday, 17-Sep-12 00:31:21 UTC from web
    6. @widget Hm yeah, it's definitely live (and still messed up) on your test instance. Poking about a bit with the live page via firebug to figure out what on earth is making it work for me, but break over there.

      Monday, 17-Sep-12 00:42:26 UTC from web
    7. @widget Doing it the old way causes links to overflow out of the sidebar, because tables don't have `word-wrap: break-word` applied. Fixing the emitted HTML (which is what I've mostly done, I just need to figure out what I'm still missing) seems a lot better than every theme needing to add that rule.

      Monday, 17-Sep-12 00:46:09 UTC from web
    8. @widget (It's also more consistent, though I wouldn't have bothered if that was the only difference.)

      Monday, 17-Sep-12 00:46:40 UTC from web
    9. @widget Hm?

      Monday, 17-Sep-12 00:48:34 UTC from web
    10. @widget I'd use word-wrap: break-word;

      Monday, 17-Sep-12 00:48:53 UTC from web
    11. @widget http://www.quirksmode.org/css/textoverflow.html lol

      Monday, 17-Sep-12 00:50:10 UTC from web
    12. @widget overflow: hidden; is an ugly way of cutting words imo. Do a graceful cut using some code instead.

      Monday, 17-Sep-12 00:50:25 UTC from web
    13. @widget It also overflows the group notices thing (that was the other bit I fixed), and that will actually have links that long, potentially. Plus, that involves setting CSS rules, and then we're back to the problem of needing _every_ theme to use that same rule

      Monday, 17-Sep-12 00:52:44 UTC from web
    14. @widget Yah, determine the minimum value and get a data value or a class on it's wrapping element to clean it up using some Javascript I'd say.

      Monday, 17-Sep-12 00:53:22 UTC from web
      1. @zeeraw minimum width*

        Monday, 17-Sep-12 00:53:41 UTC from web
    15. @widget Anyway, I found what I'd missed, and as I expected, it was something stupidly obvious in hindsight. About to make one last push, and this _will_ fix it, because it'll change it to be exactly the same as what's demonstrably working on your test site if I live-edit the same changes in.

      Monday, 17-Sep-12 00:53:33 UTC from web
    16. @widget Assume it's turned on and have it ungracefully falling back on breaking the word using word-wrap. # # #

      Monday, 17-Sep-12 00:55:52 UTC from web
    17. @widget It's now showing up in github's web UI, so pulling now should finally fix it. Sorry for causing so much hassle, I should've tested without RDNplus and a theme on before I started committing my changes. :(

      Monday, 17-Sep-12 00:56:41 UTC from web
    18. @widget Also, take a look on it from the perspective that allowing too slim of a layout might be a fundamental design flaw.

      Monday, 17-Sep-12 00:57:27 UTC from web
      1. @zeeraw It's stuff like this that makes me wonder why we're still using StatusNet. :/

        Monday, 17-Sep-12 00:58:08 UTC from web
        1. @minti Other than "we're all too lazy to code our own"

          Monday, 17-Sep-12 00:58:32 UTC from web
        2. @minti There is a guy in the fandom that nicks Scan who's really talented. He's working on a twitterish like service http://neighr.com/

          Monday, 17-Sep-12 01:02:04 UTC from web
          1. @zeeraw Oh gawd! That animation for loading more post is #

            Monday, 17-Sep-12 01:03:30 UTC from web
          2. @zeeraw It doesn't seem to load anything at all with javascript switched off. That's not great. (It's both possible [i]and[/i] preferable to gracefully fallback in such a situation.)

            Monday, 17-Sep-12 01:03:52 UTC from web
    19. @widget "Did you mean: @commodorecrazycommanderofthefirstroyalbrigadeofspiceracksandcheese?"

      Monday, 17-Sep-12 00:59:15 UTC from web
      1. Awww, that's not right either? I used to remember this one without checking. :(

        Monday, 17-Sep-12 00:59:59 UTC from web
    20. @widget It works cause it implements OStatus. I'm sure we could also do that.

      Monday, 17-Sep-12 00:59:43 UTC from web
      1. @minti OStatus is sufficiently geared to an architecture very much like status.net that you would effectively be coding under the exact same limitations, and end up with just another status.net.

        Monday, 17-Sep-12 01:01:17 UTC from web
        1. @bitshift Yeah but, the actual codebase would be clean and use actual *TEMPLATES* for functions. xD

          Monday, 17-Sep-12 01:03:53 UTC from web
          1. @minti True. Just seems like a lot of wasted effort when the protocol would still limit you to making something that can't really have a competitive edge beyond "yeah, but our code is cleaner".

            Monday, 17-Sep-12 01:05:00 UTC from web
            1. @bitshift The main problem is us though. With a custom codebase we could probably shave off maybe 60% of the processing, and like 40% of the memory usage.

              Monday, 17-Sep-12 01:05:59 UTC from web
          2. @minti @bitshift Templates for themes*

            Monday, 17-Sep-12 01:05:21 UTC from web
    21. @widget Then that's the design flaw :D When I build services I just look at what patterns and paradigms Twitter use for their details. They are usually right.

      Monday, 17-Sep-12 01:00:03 UTC from web
    22. @widget simple solution: stricter character limit for usernames? #

      Monday, 17-Sep-12 01:00:04 UTC from web
    23. @widget I have time and will, I just don't have the dedication. :/

      Monday, 17-Sep-12 01:08:03 UTC from web
    24. @widget I'll rewrite it! (Don't get mad when it's only 10 lines of code though.)

      Monday, 17-Sep-12 01:08:35 UTC from web
    25. @widget I'm totally willing! I'd just give up after a day calling it a useless project. ;p

      Monday, 17-Sep-12 01:09:06 UTC from web
    26. @thatonestocking SHUT UP HOW DO I ENGLISH ;_________;

      Monday, 17-Sep-12 01:09:29 UTC from web
    27. @widget It's not totally useless, it would be a neat learning experience to say the least. :p

      Monday, 17-Sep-12 01:10:18 UTC from web
    28. @widget s/$action->element/oh god how do I regex replace all the dom building with raw html

      Monday, 17-Sep-12 01:11:18 UTC from web
    29. @widget And how'd that turn out?

      Monday, 17-Sep-12 01:11:59 UTC from web