[1] https://github.com/ish-app/ish/issues/249#issuecomment-54433...
366 karma · joined July 5, 2023
[1] https://github.com/ish-app/ish/issues/249#issuecomment-54433...
Signing in to websites will work fine since it doesn't depend on Google.
Regarding DRM: I never really used anything that required it so I don't know, but you can go to Issues on the GitHub page and search for "Widevine", "DRM" etc
Edit: Here's the FAQ https://ungoogled-software.github.io/ungoogled-chromium-wiki...
1. A phone number is a useful piece of information to have on a customer (to sell to someone or whatever).
2. Some (most?) people are too dumb to manage passwords/TOTP and shouldn't be allowed to use a computer. As a result, everyone suffers and is forced to use broken SMS 2FA that can be SIM-swapped.
3. Companies want to stop bots and use phone numbers for that, even if it's a non-issue for bot operators in practice. A little inconvenience, sure, but it doesn't change the bigger picture in any way.
https://github.com/ungoogled-software/ungoogled-chromium
> Brave is run by a homophobic, anti-vax crypto clown. I won’t dignify it here with a link.
Brave is a decent browser, I don't understand why would you care who created it. Attacking author's persona and not the technology itself really reeks of bias
Not to mention the fact that some interviewers feel obliged to ask useless cliche questions like "why do you think you are a good fit for this position" yada yada.
Not going to be surprised if picking people based on random chance (if they meet basic requirements) is going to actually be better statistically than bombarding them with questions trying to determine if they are good enough. Really feels like we are trying to find a pattern in randomness at that point.
Bottom line is that if ChatGPT is actually a problem for the interview process, then the process is just broken.
And because C is more popular in embedded, new vendors are more likely to pick it for new platforms instead of Rust, which doesn't help.
But the number of values is just 2^n, because that includes zero.
That's some kind of logic right there. If people don't read the manual, they have every right to expect that things will break. It's not surprising or shocking, it's just user error.
> we can simplify that advice to "don't write shell scripts".
No, we cannot simplify it like that. Shell scripts are a brilliant tool for a certain kind of problem, and they work well when used for that class of problem. When used for anything else, they work poorly. Same applies for literally any other tool. It's like saying "essentially nobody is good with a CNC machine so don't use it"
If you aren't good with shell scripts, why bother? Go use Python or something else entirely. And it's not like you would use shell scripts to write all your programs, they aren't suitable for anything more complex than stiching a bunch of programs together anyway, yet people still try. And then those people complain that shell script is full of "footguns" when they are misusing it.
> Trivial to do so that it works for you. Absolutely not trivial to do so that it always works.
No idea what you are on about, literally every single detail you need to correctly parse /proc entries is in proc manpage. And yes, if you wrote your parser correctly it will still work between kernel versions, because /proc is considered a stable API between the kernel and userspace (same as syscalls). There are no "footguns" and no mysteries to it. It's a solved problem. Provide a concrete example of a footgun if there is one, and by "footgun" I mean something that isn't clearly stated in the manual that everyone dealing with /proc reads (right?)
2. Another fallacy. Obviously there will be badly written programs that don't handle paths properly. And I'm sure that if I put a space there it will screw things up. But it doesn't mean that most programs do that?
3. It's not a pain. It's absolutely trivial to do, and people whose code is vulnerable in this case are most likely just bad at programming and shouldn't be writing at such a low level as to cause vulnerabilities anyway. These are the type of people referred to as "developers" instead of "programmers". (Source: I personally parsed /proc entries without third party libraries, can't say it was hard)
2) No idea where you got that from, I never had a problem with this (as a full-time Linux user)
3) Mixed opinions on this one. There's a ton of various info in /proc that could theoretically be exposed via different syscalls, or maybe a single syscall? But having a text-based API in this case isn't a big issue really.
https://web.archive.org/web/20230811081600/https://voidlinux... https://voidlinux.org
You play as a witch, there are wands and spells that you can put in them to make unique builds with sophisticated wand mechanics. Every pixel in the world is simulated, like in falling sand games.
Really recommend it!
Technically per-device based filtering is done using MAC addresses, since local IPs can change sometimes. But even then it's trivial to change your MAC address even on an iPhone.
The compiler has pretty good error messages, `rustc --explain` exists, "unreadable syntax" is a common complaint from people that expect everything to be C-like or Python (or are just trolling), "forced structures" is explained by Rust being a statically typed programming language.
> You write backend code as of you were writing frontend code, which is not enjoyable.
No idea what's this about.
> You always have to think about who owns what.
If your code is well-structured this is a non-issue. The types of people that complain about ownership are the ones that write messy code with chaotic inter-dependencies and unclear semantics.
And besides, you have to do that anyway in e.g. C++, only it doesn't enforce it, which leads to programmer error, which is worse. Or you can use reference counting if you have skill issue.
> Compile times are long.
Compared to what? They aren't much longer when comparing apples to apples: C++ with static analysis tools and Valgrind will have pretty much the same compile times. Again, a bold general statement that doesn't really say much.
> What do you gain in performance compared to Go? Not a while lot, and you pay with wasted time aka increased development time and more complicated thought process.
Performance in what? For non compute-intensive tasks you can obviously pick any language you are comfortable with. Obviously there's no point using C++ to serve a static site when a simple Python server will do. In benchmarks, Rust just murders Go in performance, so you are objectively wrong if you are talking about raw performance.
> that means it's a propaganda post
Based on your wacky arguments, I'd say that your comment is in fact propaganda.
Why would anyone ever want that? If you buy a device, you are supposed to be able to do anything you want with it, including running emulators or whatever.
Thankfully, even when vendors want to prevent people from doing that, they often screw it up and leave exploits that allow people to regain control. Even funnier when they then try suing random people for that to compensate for their engineering skill issue/make an example etc.
Also see sstrip for ELF files and this legendary writeup https://www.muppetlabs.com/~breadbox/software/tiny/teensy.ht...
I'd also argue that most people that complain about those jokes unironically think that author is actually racist, like it doesn't even cross their mind that it could be a joke, even a "bad" one.
Ironically, the fact that some people react in this way makes these jokes even funnier
Some people are way too serious on the Internet. If you are offended by a bunch of words without proper context you really need to go outside.
Also see this thread that discusses this at length: https://news.ycombinator.com/item?id=33142122
> How can I trust you? You can't. Cock.li doesn't parse your E-mail to provide you with targeted ads, nor does cock.li read E-mail contents unless it's for a legal court order. However, it is 100% possible for me to read E-mail, and IMAP/SMTP doesn't provide user-side/client-side encryption, so you're just going to have to take my word for it. Any encryption implementation would still technically allow me to read E-mail, too. This was true for Lavabit as well -- while your E-mail was stored encrypted (only if you were a paid member, which most people forget), E-mail could still technically be intercepted while being received / sent (SMTP), or while being read by your mail client (IMAP). For privacy, we recommend encrypting your E-mails using PGP using a mail client add-on like Enigmail, or downloading your mail locally with POP and regularly deleting your mail from our server.
Also, there's this quote from /g/:
Administering a mail host is sort of like being a nurse; there's a brief period at the start when the thought of seeing people's privates might be vaguely titillating in a theoretical sense, but that sort of thing doesn't last long when it's up against the daily reality of shit, piss, blood, and vomit.
Now that I think about it, administering a mail host is exactly like being a nurse, only people die slightly less often.
--------------------------------
They also publish all emails/call recordings when dealing with law enforcement on their transparency page.
There's a lot of stuff you need to change, including fonts, screen resolution, system memory, user agent details (some browsers also add Sec-CH-UA strings), timezone, along with things like WebGL fingerprinting etc
It's also worth noting that you can sometimes actually make yourself more fingerprintable by not properly hiding something, like changing your UA in HTTP requests but not in JavaScript as well. If a website detects such a "quirk", it would be able to fingerprint you with a lot more precision.
TL;DR If you really want to stay anonymous and not worry about fingerprinting and trackers — use Tor Browser. It was specifically designed so that everyone has the same fingerprint, and has things like letterboxing to hide resolution etc. It's unlikely you'd be able to do a better job than Tor Browser by modifying your own browser.
It's not shocking, it's not surprising, it's pretty rational to do that if you think about it for 2 seconds. This is a solved topic, I really don't understand why people keep bringing this up.
If you are mad about people skipping your boring sponsorship segments — paywall your stuff already or stop complaining. Or better yet, find non-intrusive ways to monetize your content instead of relying on same old methods that became unsustainable years ago.
If you implement most of it then you would be able to call your project a POSIX shell.
[1] https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V...
[2] https://pubs.opengroup.org/onlinepubs/9699919799/idx/utiliti...
Your project is essentially an incomplete implementation of a shell where all commands are builtins, and the interactivity is limited by what you directly programmed in JavaScript.
What you are trying to make is a lot harder than you think, you first need to emulate a CPU and go from there, not read whatever user types and try to behave like a Linux system, which ChatGPT can do already.