Indie iOS app developer with a passion for SwiftUI

  • 2 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • lazyvar@programming.devtoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    28
    ·
    edit-2
    1 year ago

    You’re right that a lot of Terms of Service documents and similar agreement documents have language that reserves the right to modify those terms.

    At the same time just because something is in the terms doesn’t mean it can stand the test of adjudication and terms as well as changes are often challenged in court with success.

    Unity is in a particular tricky situation because the clause that governed modifications in their last ToS explicitly gives the user the option to pass on modifications that adversely affects them and stick with the old terms:

    Unity may update these Unity Software Additional Terms at any time for any reason and without notice (the “Updated Terms”) and those Updated Terms will apply to the most recent current-year version of the Unity Software, provided that, if the Updated Terms adversely impact your rights, you may elect to continue to use any current-year versions of the Unity Software (e.g., 2018.x and 2018.y and any Long Term Supported (LTS) versions for that current-year release) according to the terms that applied just prior to the Updated Terms (the “Prior Terms”). The Updated Terms will then not apply to your use of those current-year versions unless and until you update to a subsequent year version of the Unity Software (e.g. from 2019.4 to 2020.1). If material modifications are made to these Terms, Unity will endeavor to notify you of the modification. If a modification is required to comply with applicable law, the modification will apply notwithstanding this section. Except as explicitly set forth in this paragraph, your use of any new version or release of the Unity Software will be subject to the Updated Terms applicable to that release or version. You understand that it is your responsibility to maintain complete records establishing your entitlement to Prior Terms.

    https://web.archive.org/web/20201111183311/https://github.com/Unity-Technologies/TermsOfService/blob/master/Unity Software Additional Terms.md



  • lazyvar@programming.devtoMemes@lemmy.mlGoogle DRM when?
    link
    fedilink
    English
    arrow-up
    5
    ·
    1 year ago

    Oh wow, they really closed it down huh?

    Not too long ago you were able to change it.

    This dumbing things down to prevent customers from fucking themselves over and using up CS resources is getting ridiculous.

    Say you need to change some settings but your modem/router isn’t online then you’re SOOL.

    Cox, who uses the same gateway, is even worse. They won’t even allow you to enable legacy mode (802.11b) for IoT devices that cheaped out on WiFi cards, not even on a separate network and their customer service can’t enable it either.

    I dread moving into a Cox region where there’s no fiber competitor available.



  • There are plenty of instances that are open, but it depends on your definition of “censored” if they are what you seek.

    Completely “uncensored” instances are rare if not non-existent because most instances will at least try to adhere to the laws of their jurisdiction and in addition will have some rules in place to keep things running smoothly and pleasant for everyone.

    Most big instances are run from the EU so they’ll often have rules regarding hate speech.

    Depending on your definition your only options might either be Japanese instances due to less strict laws around certain content or right wing instances, but both will be almost uniformly blocked on other instances.








  • But for iOS you’re forced to use Xcode for implementing certain things like permissions, build and upload.

    You can do all that via VSCode as well if you so desire.

    Permissions, configurations, etc. are essentially all just XML files and can be edited as such, building, running in simulator and uploading can all be done via CLI.

    And if you’re not comfortable doing it via the terminal in VSCode, you can also find some extensions.

    Personally as a native dev I don’t know why you’d want to of course, but to each their own.


  • I think you might be misunderstanding what this does.

    You did a search for symbol references that contain “User” ignoring cases.

    When you do a search for symbol references this way, Xcode will return two things:

    1. A declaration of all the symbols containing “User” and/or some context surrounding the symbol (ignoring Case)
    2. Show any places where your code references the symbol

    And it did just that.

    The first three .swift files show references to symbols that contain “User”.
    The forth one, User.swift, is in and of itself a symbol that matches the query and has symbols inside itself.
    The last one UserViewModel.swift is in itself a symbol as well and all the parts that are nested within that you’ve annotated with underscores and question marks, serve to give you context about the symbol “UserViewModel”, hence the ellipses.

    It’s essentially telling you “Hey I’ve found this symbol UserViewModel, it starts with a var named username, has a bunch of stuff following that (i.e. …) then has an extension, then some more stuff (i.e. …) and then ends”.

    Without knowing what’s inside UserViewModel.swift I can’t tell if it goofed with giving you a typical declaration, but that doesn’t change the fact that its trying to give you context about a valid search result, the symbol UserViewModel, so that you can figure out if that’s the one you’re looking for.

    Keep in mind that variables are considered symbols as well, but in this instance I don’t think that’s what happened here, otherwise it would’ve been marked with a P instead of a C.

    If this is not desired behavior then I suggest you switch from “Containing” to “Matching Word” or instead consider using the search bar at the bottom of the Symbol Navigator. Another option, if you’re searching while going through code, is to right click on the symbol in your code and click Find > Find Selected Symbol in Workspace.

    Lastly it might be an idea to go over the Xcode documentation as a refresher. This would be a good starting point.

    That said, Apple clearly feels that things can be improved by clarifying, because in the current Xcode beta they’ve changed the option label from References to Symbols (and added a few more options).