Indie iOS app developer with a passion for SwiftUI

  • 2 Posts
  • 21 Comments
Joined 2 years 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



  • 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).


  • The presumption of innocence doesn’t preclude the fact that criminal courts don’t find someone innocent, rather they find someone not guilty.

    This is for the simple fact that it’s neigh impossible to establish someone’s innocence, whereas it’s easier to establish that there isn’t enough evidence to consider someone guilty.

    This case is, and sexual assault cases in general are, a great example why we can’t expect criminal courts to establish innocence.

    These are often cases with little evidence available either which way, because often there are no other witnesses. Even if there would be physical evidence of a sexual act, it’s still challenging to prove under what circumstances those acts have occurred, specifically on the matter of consent.

    To expect a court to be able to say with certainty that something hasn’t occurred is unreasonable.

    That is not to say that it isn’t good that we have these high standards before we impose punishment onto someone, but it is important to recognize what it means when a court comes to a decision.

    Additionally the presumption of innocence is just that, a presumption to establish who has the onus to prove something, there is no additional meaning attributed to it in the legal principle beyond establishing who has the onus to prove the facts at hand.

    In that regard it’s rather unfortunately named, as it would’ve been more apt to name it “the presumption of not guilty” but I suppose that doesn’t roll as nicely off the tongue

    To add to that, that the presumption is specifically a principle that only has meaning in criminal court, because the burden of proof is generally higher than in civil court.

    People can be, and have been, found liable in civil court for the very thing a criminal court has found them “not guilty” on, on the very basis that criminal court can’t establish innocence and that the bar that needs to be met in civil court is generally lower than in criminal court.

    As such to bring up the presumption of innocence in a vacuum is kind of like bringing up the generally recognized human right of freedom of speech when a social media company bans someone and removes their post.

    Yes, the concept exists, but it’s irrelevant because it doesn’t apply to the topic at hand, because the concept aims to govern a very specific circumstance that isn’t applicable here and withholding the important context surrounding it (i.e. the role it plays in criminal court for the presumption and the fact that it only limits governments for the freedom of speech) masks the limitations of said concept.

    None of the above aims to reflect my opinion on Spacey’s innocence (or lack thereof), rather it aims to provide the necessary details to put things into context.


  • Most of these services are US-centric because a lot of the necessary records to provide the information isn’t public in many countries outside of the US.

    Birth records, death records, marriage records, divorce records, voting records, criminal records, etc. is considered public information in much of the US. Even address information can be found publicly and immigration records become available to the public after a certain time.

    In a lot of countries, especially in many European countries, these are hard to access for people that aren’t the subject of these records, if accessible at all.

    For example while court records are public in much of Europe, often times the names of private persons are censored because it’s not deemed necessary to know who the parties are to be able to check if the courts make fair decisions.
    This automatically excludes criminal and divorce information from disseminating into the public.

    Some countries will make some records public once the subject of those records have passed for X amount of years, but that’s still pretty rare.

    As such services like these have limited use outside the United States.


  • This reads as incredibly condescending, naive and duplicitous, filled with hubris.

    For starters, the whole “yeah sure XMPP got EEE’d but who cares, only nerds cared about that, lol” is not only false (e.g. Jabber), but also does nothing to quell concerns.

    Here’s an account by someone who was in the XMPP trenches when Google started adopting it.

    Notice something? The “omg so cool!”, this is exactly the same as Rochko.

    It’s the hubris when you’re a FOSS maintainer who toiled away for years without recognition and now a $700B+ corporation is flattering him by wanting to use/interact with his work.

    The blog is a far cry from the anti-corporate tone in the informational video from 2018.

    Then there’s the fact that Rochko is extremely tight lipped about the off the record meeting with Meta and consistently refuses to deny having received funds from Meta and refuses to pledge not to accept any funds from Meta.

    There’s also the unsatisfactory answer he gave to people who started questioning some dubious sponsors and the fact that he rushed to lock the thread, killing any further discussion.

    I genuinely think the dude is just so hyped for the perceived recognition, that he lost the thread.

    So much so that he thinks Mastodon is untouchable.

    And it’s extremely naive to think that Meta has benevolent motives here or that Mastodon will survive any schemes Meta might have.
    What’s more realistic is that Mastodon will die because people will flock to Threads if their social graph has moved over.

    Similarly these lofty and naive ideas that people on Threads will make the switch to Mastodon once they get a taste of what it has to offer.

    So now all of a sudden the “difficulty” to get started in Mastodon, that is keeping people who want a polished corporate experience away isn’t going to be an issue?

    Especially when in the “extinguish” phase Meta will have siloed off from Mastodon and its portability function, having to leave their social graph behind?

    It’s all so increasingly naive, one can’t help but wonder if it’s intentional sabotage at this point.

    Mark my words, this’ll be the end of Mastodon especially when Meta can outspend Mastodon all day every day to add proprietary functionality.

    Sure perhaps years from now a few hundred to a few thousand people might still use it, but it will be as irrelevant as XMPP is to most people, and Rochko with it.

    @remindme@mstdn.social in 2 years.



  • Current 2FA implementation in Lemmy is a bit janky with the risk of being locked out.

    First things first: DO NOT UNDER ANY CIRCUMSTANCES LOG OUT UNTIL YOU’RE 100% SURE YOUR AUTHENTICATOR WORKS AND THAT YOU CAN LOGIN USING ITS GENERATED 2FA CODE

    Now that that’s out of the way, here are some steps to follow:

    1. Ideally clicking on that button will open your authenticator which will then prompt you to select login credentials to attach it to; if it doesn’t and you instead are lead to a URL with a secret key or if you right click and you can copy that URL, then you need to manually copy the URL and paste it in the 2FA section of your authenticator or password manager
    2. Once you’ve figured this out don’t log out, instead open a private browser window and test to see if you can login with your credentials + 2FA

    If you can’t get it to work then you can disable it in the window you’re still logged into.

    If you share which authenticator you use, people might be able to give you more specific instructions to get you through step 1.

    Whatever you do, don’t log out. You will be locked out!
    Unlike most common implementations, there is no built in step to verify if you can successfully generate a TOTP before 2FA is fully enabled.