Skip to content

Stop using @namespace to identify scripts #130

Closed

Description

@sizzlemctwizzle

It's just ugly and unnecessary. I want to wait on merging #129 before I do this.

Activity

  1. added this to the milestone on Jun 10, 2014
  2. Martii commented on Jun 10, 2014

    @Martii
    Member

    and lengthy on urls... I've been wondering at what point we're going to hit a pathname limitation of the server drones.

  3. sizzlemctwizzle commented on Jun 11, 2014

    @sizzlemctwizzle
    MemberAuthor

    Also, I need to remove the .toLowerCase() nonsense on usernames since it's completely unnecessary.

    pathname limitation of the server drones.

    I'm not sure if there is one, but shorter urls would be very nice.

  4. Martii commented on Jun 11, 2014

    @Martii
    Member

    remove the .toLowerCase() nonsense on usernames

    I was waiting on this issue with a lower priority because .../Marti accesses me currently on production and .../marti does not.

  5. sizzlemctwizzle commented on Jun 11, 2014

    @sizzlemctwizzle
    MemberAuthor

    Usernames are supposed to be case-insensitive (because they have to be for S3), but we use the case that you signed up when we display it on the site somewhere. You're right though, that url should work. The case shouldn't matter.

  6. sizzlemctwizzle commented on Jun 11, 2014

    @sizzlemctwizzle
    MemberAuthor

    Something to add to the list: make script.meta.icon a string in cases where it might be an array of strings. Then add "icon" to the list of unique metadata keys in scriptStorage.js

  7. sizzlemctwizzle commented on Jun 22, 2014

    @sizzlemctwizzle
    MemberAuthor

    Well I did it and I only broke three scripts: 1 2 3

    S3 wouldn't let me copy those files to a new path for whatever reason. Perhaps they failed to upload to S3 in the first place. I added case insensitivity for user and script names, but I totally forgot about the icon. Oh well, that can be handled another time.

    Edit: Almost forgot to mention. This is totally backwards compatible with links still including the namespace. That portion of the url is just ignored. You could put any old junk there and it'd still work. Example:

  8. jerone commented on Jun 22, 2014

    @jerone
    Contributor

    Great work!

    The old namespaced urls are all over the web. Do those get a 301 status code to circumvent a penalty by Google?

  9. sizzlemctwizzle commented on Jun 22, 2014

    @sizzlemctwizzle
    MemberAuthor

    No but it could be added.

  10. jerone commented on Jun 22, 2014

    @jerone
    Contributor

    No but it could be added.

    Reference issue #75

  11. added a commit that references this issue on Jul 6, 2015
  12. added a commit that references this issue on Feb 21, 2016
  13. locked as resolved and limited conversation to collaborators on Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    DBPertains inclusively to the Database operations.enhancementSomething we do have implemented already but needs improvement upon to the best of knowledge.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions