sreevisakh

The biggest problem with Play store is that many apps are geographically restricted. That includes banking and public transport apps. Some apps are restricted without even the knowledge of the developer. Most of those apps have no good reason at all to be restricted like that. Such apps often cannot be accessed through Aurora. Sadly, there are no laws or provisions to challenge such unethical tactics. Using Google's services is like living with a manipulative and abusive partner.

If it wasn't clear, people aren't objecting to the use of automated tools to prevent crime. It's that there is absolutely no avenue of appeal or review against it even if the law enforcement exonerates them and a big news media reports it.

Google has inserted itself into almost all spheres of digital life by hook or crook. It's practically difficult to avoid them in many services - especially email. And now they play judge, jury and executioner. I don't understand any of these are acceptable, much less justifiable. The old argument 'think of the kids' used to justify digital authoritarianism is such a cliché by now.

Arch wiki is precious. But the reason for quality of OpenBSD documentation is unlikely to be the same as Arch wiki's. The article even mentions the problem with wiki's. Arch wiki clearly shows signs that it is collected together by people looking for solutions. Articles often contains discussions on contentious or confusing issues. OpenBSD documentation on the other hand, is prepared along with the application source, often by the same developers. That is a much better solution IMO to ensure documentation quality.

That said, I'm happy that Arch wiki exists. It has become the defacto place where people elaborate their solutions for Linux.

The GNU project does sell print copies of their texinfo manuals. But you could also download the manual and print it yourself. Buying the print is an optional way to support the development of the software.

Can you elaborate a bit on what you mean? It's a bit difficult to install build artifacts directly into the system. There are problems like tracking version compatibility, installing resource files and tracking artifacts for removal etc. This is what packages and package managers do. If you wish to take that route, then Arch PKGBUILDs and Gentoo Ebuilds are reasonably easy. Ebuilds have a lot of similarity with ports. Debian's checkinstall is also somewhat successful in it. Nix and Guix also allow you to do this - but the approach is slightly different from the rest. However, all distributions need some metadata and procedure from the user/packager to achieve it.

Accusations of victimization is a widely used strategy to deflect discussion of caste discrimination. And one common tool for that is the caste reservation system in India.

The post just shows one recent event. If that makes you upset, then I suggest that you don't go searching for it. That's for the sake of your sanity.

Probably because the perpetrator and victim often belong to the same race. Besides, it's hard even to prove that discrimination occurred. The usual strategy is to put lower caste people in no-win situations and blame them for the failure.

Really hard. There are so many caste markers. Surnames are the least of it. Speaking accent, diet, clothing and several other habits can some among them. Even worse, people who believe in castes are part-time detectives who often do background checks on others. At least, that's the case in India. I don't know how bad it is in the US - but I'm sure there will be some.

> In India, yes it does family name is derived from caste.

That is not always correct (but is true in most cases). There are caste-neutral names in India - especially Tamil Nadu. But that itself is a hint about the person's caste, since it is adopted mostly by people of the unprivileged caste.

Do you know of any Indians who treat all non-Indians as inferior? My understanding is that non-Indians are judged based on their skin color. That is most certainly racism, but not based on nationality.

Another thing that puzzles me is how you differentiate caste discrimination from racism. The underlying motivations are different. But the treatment, politics and tactics used are almost the same in both cases. I'm curious about your perspective on these.

The interface is very discoverable, unlike screen or tmux. You can start using it productively even before reading any documentation. The keybindings feel like a cross between vim (modal) bindings and CUA bindings.

That isn't even right because almost every single victim of caste discrimination is an Indian themselves. If there are caste allegations outside India, then it can only be from Indians themselves. Covering it under the wide umbrella of anti-India smear campaign is disingenuous at best.

You're missing the cultural insight needed to understand caste. For example, two people from New Jersey may tolerate each other even if one of their ancestors are from other places. Castes on the other hand, carries on from generation to generation. It's extremely hard to get rid of the caste label you're born with. Another factor is the level of discrimination involved. Caste is widely used to judge academic and professional proficiencies. It's extremely hard for lower caste people to rise up even if they work hard. They get denied and often demotivated in public. It gets much worse within India. Lower caste people are kept away from good residential areas, many commercial establishments and even village wells.

That sounds very similar to the electromagnetic accelerator by Hyperspace Pirate [1]. The difference is that it uses magnets to accelerate the balls instead of mechanical oscillations. And there is no stream in a strict sense.

[1] https://www.youtube.com/watch?v=uNbL3tRZeMQ

You have to really search hard to find an example like this that is contrary to what I said.

I don't think that the idea of either free software or the semantic web were hopeless or that they lead to the dystopian hell. Open source was created due to a disagreement with the idea of software freedom. It turned out to be exactly what free software wasn't - a tool for exploitation. Similarly, the semantic web was easy to implement - except that the big tech saw it as a hindrance to profit. That lead to the blockchain web hijacking the web3 designation from it. That said, both ideas are still viable and still alive on a small scale.

As I understand it, org-roam uses the database as an information cache to improve performance. But the org roam files are self-contained and doesn't need the database to be saved along with it.

I've been waiting for years for the emergence of the original Web 3.0 - the semantic web [1]. A web of machine readable data based on ontologies. How did it get redefined as a web on top of append-only blockchains?

[1] https://www.w3.org/standards/semanticweb/

They love to introduce features that make politicians and rich people happy. The YouTube dislike button is a case in point.

Specifically, section D.4 [1] of Github's terms of service. That agreement gives them the right to parse or analyze source code. Sounds very much like it justifies training copilot.

[1] https://docs.github.com/en/site-policy/github-terms/github-t...

> I think what you might be asking for is if there is a federated code repository that supports git. That’s an interesting question, and I don’t know if such a thing yet exists.

Sourcehut itself is fully federated if you are willing to learn email workflow. You don't need to register an account anywhere to collaborate on sourcehut. That include feature requests, bug reports, discussions, submitting patches and even pull requests from any public repository anywhere [1]. The discussions also exist on mailing list archives and personal mailboxes. They are not lost even if you decide to change host.

But developers are extremely resistant to email workflows. When I suggest it, people react as if I am suggesting black magic. But in my experience, email workflow isn't that unpleasant. Most of the problems with email workflow are due to poor email clients (issues with plain text, composing, rendering and threaded displays). Setting up git and a good but simple email client for git is not a hard task. The rest of the workflow is actually very pleasant.

[1] https://git-scm.com/docs/git-request-pull

Copying off Github and copying off another host is not quite the same. I explained it twice on this thread already. So I'm leaving a link here: https://news.ycombinator.com/item?id=31937705

There is a hidden problem with licensing here. Developers are giving Github the permission to use the code with a different license [1]. The clause sounds broad enough for them to justify training copilot with it. This allows them to disregard the license with which the project is published. The developers don't have the protection of a FOSS license anymore when you host there.

[1] https://docs.github.com/en/site-policy/github-terms/github-t...

> That's my point-- how? Presumably you're just going to host your FOSS somewhere else that Microsoft can still get it.

The problem isn't that Microsoft can access you code. It's the section D.4 on Github's terms of service [1]. If you are hosting your code on Github, you are essentially giving Microsoft the legal rights to do certain things with your code. That section is broad enough to allow Microsoft to train copilot with your code. It gives them the freedom to disregard the license. On the other hand, it would be a clear violation of the license if they read your code off another hosts and reproduced it verbatim. I don't know whether any legal challenges would stand in a court, but at least you are not giving away the right to do so.

[1] https://docs.github.com/en/site-policy/github-terms/github-t...

I want to add the guide to submitting patches for the Linux kernel [1]. It contains a bit more finer points, in addition to what's on the site you linked.

[1] https://www.kernel.org/doc/html/latest/process/submitting-pa...

You could mail patches as plain text attachments, if there are concerns about the clients mangling them. You could also try some easier plain-text clients instead of mutt. Claws mail is a simple GUI based one.

[1] https://www.claws-mail.org/

> I am not that excited about that last part, but federating pull requests sounds like a killer feature

Git already has a pull request feature [1] that's as federated as it can get. The 'request-pull' command can be used to request pull on upstream repositories hosted anywhere (or not at all). The only requirement is that the downstream clone must be online. I know that HN isn't particularly found of email-based workflows for git. But requesting a pull is as simple as copying the output and mailing it (or via any text messaging service) to the maintainer. And doing a pull as a maintainer is actually easier than doing local PR merges using Github.

[1] https://git-scm.com/docs/git-request-pull

Gitea and Gogs weren't originally meant to be replacements for Github. They were meant for self-hosted internal repositories. That's why they are still on Github, even though hosts like Codeberg use them for public hosting these days.

It's baffling because practically all learning resources on git emphasize its decentralized nature. Even the online free book explains that several times. They never left me with any confusion regarding the difference between git and github, even though my first version control was the centralized subversion. I don't understand how any developer can learn git without this idea being drilled in constantly.