Indie iOS app developer with a passion for SwiftUI

  • 3 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • I was wondering myself as well so I got you.

    Basically what happened was that these were technically two separate cases with two separate jury pools to decide the amount for damages.

    One jury pool came to the decision that there were damages and awarded $50k to each individual in couple 1 (totaling $100k) while the other jury pool independently decided that no damages should be awarded based on the same evidence.

    Keep in mind that this region is generally pretty hostile towards LGBTQ+ people. The judge had the option to overrule a jury if they find that the decision doesn’t match the evidence in the case.

    The lawyer of this lady is actually hoping for that in the case that lead to a $100k damages award as per the quote below.

    “Two juries heard the same evidence and the same arguments, and only one jury returned a verdict that was based on the facts and the evidence presented at trial,” Daniel Schmid, senior litigation counsel for Liberty Counsel and one of Davis’ attorneys, told CNN via email. “In the Yates case, the jury returned a verdict of $0.00 because that is what the evidence required.”

    “Without any evidentiary support, the Ermold jury reached a verdict of $50,000 for each plaintiff. The evidence presented at trial simply does not support that verdict, and Ms. Davis will be filing a motion for a judgment notwithstanding the verdict next week,” Schmid said. “Ms. Davis trusts that the courts reviewing the evidence presented will see that the Ermold verdict lacks any evidentiary support and will agree with the Yates jury that the plaintiffs are entitled to no damages whatsoever.”

    Source




  • I get asking for mercy for family or a close friend, even when they’ve committed crimes, heinous or otherwise. I’ll chalk that up to human emotions.

    But ffs, read the room a bit.

    His dedication to leading a drug-free life and the genuine care he extends to others make him an outstanding role model and friend.

    One of the most remarkable aspects of Danny’s character is his unwavering commitment to discouraging the use of drugs.

    His dedication to avoiding all substances has inspired not only me but also countless others in our circle. Danny’s steadfastness in promoting a drug-free lifestyle has been a guiding light in my journey through the entertainment world and has helped me prioritize my well-being and focus on make responsible choices.

    Saying stuff like that when he’s convicted of drugging victims before taping them is just nuts. Even by some sense of stupidity you think you’re just trying to highlight that he’s not a habitual drug user, you’re essentially just highlighting how calculated his actions were by drugging his victims.


  • Cue the nuclear shills that will handwave away any legitimate concern with wishful thinking and frame the discussion as solely pro/anti fossil, conveniently pretending that renewables don’t exist.

    ETA:

    Let’s look at some great examples of handwaving and other nonsense to further the nuclear agenda.

    Here @danielbln@lemmy.world brings up a legitimate concern about companies not adhering to regulation and regulators being corrupt/bought *cough… Three Mile Island cough*, and how to deal with that:

    So uh, turns out the energy companies are not exactly the most moral and rule abiding entities, and they love to pay off politicians and cut corners. How does one prevent that, as in the case of fission it has rather dire consequences?

    So of course the answer to that by @Carighan@lemmy.world is a slippery slope argument and equating a hypothetical disaster with thousands if not millions of victims and areas being uninhabitable for years to come, with the death of a family member due to faulty wiring in your home:

    Since you can apply that logic to everything, how can you ever build anything? Because all consequences are dire on a myopic scale, that is, if your partner dies because a single electrician cheaped out with the wiring in your building and got someone to sign off, “It’s not as bad as a nuclear disaster” isn’t exactly going to console them much.

    At some point, you need to accept that making something illegal and trying to prosecute people has to be enough. For most situations. It’s not perfect. Sure. But nothing ever is. And no solution to energy is ever going to be perfect, either.

    Then there’s the matter of misleading statistics and graphs.
    Never mind the fact that the amount of victims of nuclear disasters is underreported, under-attributed and research is hampered if not outright blocked to further a nuclear agenda, also never mind that the risks are consistently underreported, lets leave those contentious points behind and look at what’s at hand.

    Here @JohnDClay@sh.itjust.works shows a graph from Our World in Data that is often thrown around and claims to show “Death rates by unit of electricity production”:

    Seems shocking enough and I’m sure in rough lines, the proportions respective to one another make sense to some degree or another.
    The problem however is that the source data is thrown together in such a way that it completely undermines the message the graph is trying to portray.

    According to Our World in Data this is the source of the data used in the graph:

    Death rates from energy production is measured as the number of deaths by energy source per terawatt-hour (TWh) of electricity production.

    Data on death rates from fossil fuels is sourced from Markandya, A., & Wilkinson, P. (2007).

    Data on death rates from solar and wind is sourced from Sovacool et al. (2016) based on a database of accidents from these sources.

    We estimate deaths rates for nuclear energy based on the latest death toll figures from Chernobyl and Fukushima as described in our article here: https://ourworldindata.org/what-was-the-death-toll-from-chernobyl-and-fukushima

    We estimate death rates from hydropower based on an updated list of historical hydropower accidents, dating back to 1965, sourced primarily from the underlying database included in Sovacool et al. (2016). For more information, see our article: https://ourworldindata.org/safest-sources-of-energy

    Fossil fuel numbers are based on this paper which starts out by described a pro-nuclear stance, but more importantly, does a lot of educated guesstimating on the air-pollution related death numbers that is straight up copied into the graph.

    Sovacool is used for solar and wind, but doesn’t have those estimates and is mainly limited to direct victims.

    Nuclear based deaths is based on Our World in Data’s own nuclear propaganda piece that mainly focuses on direct deaths and severely underplays non-direct deaths.

    And hydropower bases deaths is based on accidents.

    So they mix and match all kinds of different forms of data to make this graph, which is a no-no. Either you stick to only accidents, only direct deaths or do all possible deaths that is possibly caused by an energy source, like they do for fossil fuels.

    Not doing so makes the graph seem like some kind of joke.


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




  • There’s not much for him to be concerned about currently, given that he is dead.

    As for 16 yo Aaron who wrote that list of hot takes in order of controversy, is it really surprising that a kid that developed an opinion of free speech extremism penned that down?
    Especially after being inspired by this article as per his own admission?

    The article also helps provide context for the time period this was written in.
    Simple possession was still a relatively novel concept and simulated CSAM wasn’t criminal yet in the US.

    Don’t misconstrue my own position on the matter, I originate from, and was legally trained in, a jurisdiction that criminalizes hate speech, imposing a significantly broader limit on free speech than the US currently does, and I think that’s the better path to take.
    So I personally don’t adhere to free speech extremism.

    Nevertheless, while not agreeing with his take, I can see the logic that persuaded him.

    It’s essentially the facetious version of “Why stop here, why not also ban hate speech/guns/drugs/etc?”
    All of those can be argued to be gateways to the harm of others, perhaps even disproportionately children.

    To me it reads as him challenging the logic, not condoning the outcome much less the subsequent consequences. Very edgy indeed.

    As for those who bring up that he reinstated his blog multiple times and with it this particular post from when he was 16, as a way to posthumously attribute this to a more older adult version of him; I’m not sure it’s that cut and dry.

    As a fundamentalist such as himself it could also just be an exhibition of his free speech extremism perhaps combined with an effort to maintain transparency.

    After all, it could suggest an eroding of his beliefs on free speech if he would remove it “now” with little benefit to him since the cat’s already out of the bag, even if he disagreed with his former self at the time of restoring the blog.

    A better indication of his opinions later in life would be comments that reaffirm the prior expressed beliefs or, if the suspicion is that he practiced what he preached, one would expect this to have come out during the FBI investigation, considering they went through all his data.

    Do I think it’s healthy to consider him a hero, or anyone else for that matter?
    No not really, if only because the likelihood of heroes having irreconcilable blemishes is extremely high just by the very virtue of their, let’s say, unique thinking producing the things we love about them but also the things that might cause pause in many.



  • The proposal is bad enough as it is, but it’s the duplicitous gaslighting BS that really pisses people off.

    If they came out and said “We came up with this thing to prevent loss of revenue on ads and prevent LLMs from capturing data” then people would still be against it, but at least it would feel like an honest discussion.

    Instead it’s just another page out of Google’s playbook we’ve seen many times already.

    1. Make up some thinly veiled use cases that supposedly highlight how this would benefit users, while significantly stretching the definition of “users”
    2. Gaslight every one by pretending that people simply misunderstand what you’re proposing and what you’re trying to achieve
    3. Pretend that nobody provides reasonable feedback because everyone is telling you not to commit murder in the first place instead of giving you tips on how to hide the body
    4. Latch onto the few, inevitable, cases of people going too far to paint everyone opposing it in a negative light
    5. Use that premise to explain why you had to unilaterally shut down any and all avenues for people to provide comment
    6. Make the announcement that you hear people and that you’re working on it and that all will be well
    7. Just do what you want anyways with minimal concessions if any and rinse repeat

    For what it’s worth I blame W3C as well.
    Their relatively young “Anti-Fraud Community Group” has essentially green lit this thing during meetings as can be seen here:

    https://github.com/antifraudcg/meetings/blob/main/2023/05-26.md

    https://github.com/antifraudcg/meetings/blob/main/2023/07-07-wei-side-meeting.md






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




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


  • It’s hard to explain without a similar sound existing in English.

    The “eu” part in “neuken” and “keuken” is pronounced like the French word for 2: deux.

    The ”-ken” end of both words is almost exactly pronounced as the word “cunt” without the t.

    “de” is pronounced like “the” but with a “d” sound, like “duh” but not in the exaggerated way you’d do it when you’re mocking someone. And “in” is the same pronunciation as the English one.

    So putting that all together, I’d write it out as follows if I’d like to make it pronounceable for an English speaker: “neuxcun in duh keuxcun”