• 0 Posts
  • 50 Comments
Joined 2 年前
cake
Cake day: 2023年6月30日

help-circle

  • The risk of somone emerging and using the protests for their own gain exists, but the solution isn’t to start appointing leaders. These student protests have been organized in an anarchst manner from the very start and decisiona are made through direct democracy. The demands have been clear from the very start and haven’t changed in the past 3 months that we’ve been protesting.

    The big thing outside of the immediate changes expected out of these protests (regime change and criminal responsibility for the death of 15 people) is the chance to agitate people imo. The studenta especially have now seen that organizing is possible and have seen the strength of solidarity. Now obviously turning all of them into leftists is an impossible task, even if the current organization follows an anarchist text (blockade cookbook). But the potential is certainly there and hopefully when this is all over we’ll be left with a much more politically engaged and motivated society.




  • Perfectly fair take tbh, in terms of security on android phones grapheneOS is as good as it gets and has been for a couple of years. I personally refuse to use pixels due to no sdcard, but more importantly no 3.5mm jack. The slight hiss/hum noise present on every bluetooth headset I’ve tried (and I’ve tired my friends bluetooth sennheiser that’s like $600) bothers me way too much for w/e reason. I find crdroid for example gets me 90% of the way there with a bit of work through various magisk modules and it’s good enough for me. But things have definitely gotten better on nonpixel phones over the years, I’m for example running a poco x3 nfc that was $250 4 years ago when I bought it and I still get monthly security updates through crdroid anf battery life is still great cause it came with a 5300mAh battery.


  • But besides, being able to unlock bootloader is great (even though root is way more important to me)

    My bad I thought you were generally up to date with how rooting basically works nowadays. The defacto rooting method today is systemless root using magisk, which works by patching your boot.img. So on 99% of phones today if you can unlock the bootloader, rooting is as simple as installing the magisk, patching the boot img from the app and the flashing itl. You can also just flash magisk from recovery too. That’s why I focused on bootloader unlocking in my previous post.

    Now I can’t claim that every device from these manufacturers works flawlessly with magisk, but most do. And a quick glance at the xda page of the specific model would be an easy way to find out before buying.


  • No wonder, as they’re the only phones left (to my knowledge) that don’t demand half your soul just to fucking own your own phone.

    Literally who outside of samsung and Huawei? I guess xiaomi is a bit annoying with the wait time but pretty much all other phones are dead simple.

    Oneplus, Nothing phone: literally the same process as on a pixel, no code required to unlock bootloader or anything like that. Just fastboot flashing unlock

    Vivo: The exact same thing, just get vivo’s binary for fastboot since the unlocl command is different

    Motorola, Sony: Just go to the website and you get the unlock code instantly, then just run a fastboot command and you’re done

    Realme: Download their app, apply for unlock, gets approved within an hour. Unlock with a fastboot command

    Xiaomi, poco: Get their app, wait a couple of days for the code, unlock bootloader with fastboot command.

    Honor and huawie are a pita, but there is an open source unlocking tool for certain devices which makes it deadsimple.

    So there are still plenty of options if the goal is unlocking bootloader and rooting a phone, all of these brands offer phones with oled 120hz screens, with cameras ranging from decent to some of the best on the market depending on the model. There are probably some brends I missed, but you get the point.




  • Complete nothingburger of a study, which itself is locked behind a $25 paywall to access it. And the author of the article obviously didn’t cause there’s 0 mention in the article itself about the methodology used to determine the 20% revenue lost (nice round number might I add). The only thing that even alludes to the methodology used in the abstract is

    When Denuvo is cracked very early on, piracy leads to an estimated 20 percent fall in total revenue on average relative to an uncracked counterfactual

    Which really doesn’t tell us much, how are these counterfactuals selected in the first place? What is the cirteria? How are you determining that the differences between revenue of a game that was cracked and that went uncracked are due to one game being cracked? How can anyone even confidently claim that they’ve normalazied the data set enoguh that these differences in revenue are mainly caused by a game being cracked, especially with how rare early denuvo cracks have been in the past few years. Statistically this sounds dubious at best, especially when we have fully open studies (like the one funded by the EU a few years back) that have found no statistical proof that piracy has any impact on revenue ( with the exception of box office revenue of big new movies being leaked and pirated while still in theaters). Surely they wouldn’t have missed a 20% meadian difference in revenue.

    Lastly you have major tech news outlets all reporting on a study less than a month after it was made available online. For context the journal containing this study will only be published in jan of 2025.


  • Because you would be using std::shared_ptr<> rather than a raw pointer, which will automatically deallocate the memory when a shared point leaves the scope in the last place that it’s used in. Along with std::atmoic<shared_ptr> implements static functions that can let you acquire locks and behave like having a mutex.

    Now this isn’t enforced at the compiler level, mostly due to backwards compatibility reasons, but if you’re writing modern c++ properly you wouldn’t run into memory safety issues. If you consider that stretching the definition then I guess I am.

    Granted rust does a much better job of enforcing these things as it’s unburdened by decades of history and backwards compatibility.





  • i’m having a lot of trouble with doing so because i have a very rough history with jobs ( quitting without notice many times when i was much younger )

    The neat part about writing your resume is that you can leave out parts of your employment history that make you look “bad” (kinda like japan does with WWII). So let’s say you had 4 jobs over the course of a year, skip the two jobs that you had for the shortest amount of time. After that do some stretching, ex say you started a job a month earlier than you did and tack on a ~month - month and half to the end of it. Now never say you were fired or quit for no reason, you could say that it was a temp position from the start cause your employer had more business that time of the year and that there was no prospect of staying longer from the very start. Try to keep the gaps between jobs small (I’d say two - three months at most). Now if you have a lot of jobs where you quit early on you could just skip that entire part of your employment history and say you starter working later in life. Employers generally don’t care about how old you were when you got your first job, and they have no way to get your employment history (some government jobs can and will check tho I think) so don’t mention stuff that makes you look bad. And yes this will shorten your work experience but being inexperienced is more desirable than frequent job changes on a resume (dumb af, ik, but it is what it is).

    Now regarding embellishing how long you worked at a certain place, the further back the job was the better. Employers will typically only check with your last one or two employers if they check at all ( again some gov jobs might be an exception). One more tip, most place won’t keep a digitalized employee database where they could easily search up your contract, so when embellishing try to avoid jobs that you believe might have kept digital records ( like chains etc). A lot of customer facing jobs have a huge turnover anyways so there’s a good chance that there’s noone you worked with that stil works there, let alone rembers you by name to be able to dispute what you said on your resume. Lastly if you get confronted about embellishing the time you worked a specific job, there’s two things you could do: I didn’t have my old resume on hand since I haven’t worked in 2yrs so I wrote it from memeory or (better imo if you can project confidence during the interview and if you claimed you started earlier than you did) you can claim that you were on a trial position before signing the full contract so the one they looked up probably doesn’t reflect your actual time there. If you can sell this with enought confidence they won’t bother calling again to check, as it’s a perfectly reasonable explanation and they already confirmed you worked there. If you aren’t feeling confident about lying about any of these things, first lies by omission are much easier to sell and second just practice with your friends/parents.

    Now depending on how confident you are there is another approach (which is more effective imo and it’s what I did). You could only list a year on your resume and then just positions and places where you worked during that year (again feel free to omitt some jobs here) without specifying the duration. This lets you wing it during your actual interview where you can meet, judge and lie just enough based on the person interviewing you. It also lets you avoid some lies that would be easily exposed by not telling them in the first place (ex. If your interviewer worked at the place you were gonna lie about there’s a good chance they’ll mention it when the topic of that job comes up, so you just don’t lie about that one). Note that some jobs might not even invite you to an interview without specifying the length of employment at each position, but in such cases, of you notice you aren’t hearing back from them at all, you could just reapply with version according to the first approach I gave. Fixing a resume and reapplying is super common and you aren’t really losing anything (except some time ofc).

    As for the two year gap as some have suggested saying that you worked freelance is an option. If you aren’t feeling confident with that approach you could say that you had to take care of a sick/injured parent/relative, they can never get their hands on their medical records and asking about details would feel kinda rude for most people (but not all, so be prepared for questions just in case, but also know that if the question seems to detailed refusing to answer would be pretty normal) so that might be an easier sell.

    Anyways hope you find some of this usefull, feel free to ask if you have any questions.





  • At the (SQL) database level, if you are using null in any sane way, it means “this value exists but is unknown”.

    Null at the SQL means that the value isn’t there, idk where you’re getting that from. SQL doesn’t have anything like JS’s undefined, there’s no other way to represent a missing value in sql other than null (you could technically decide on certain values for certain types, like an empty string, but that’s not something SQL defines).