Shouldn’t that happen automatically if the drive is identified as removable? And the real solution should be to tell the OS that it’s removable?

You are right! I was fooled by my server already having git installed and this requirement not being mentioned anywhere. I guess that explains why it uses SSH rather than SCP/SFTP.

I feel like you made it sound a bit backwards :)

There’s nothing to install on a “git server”, git doesn’t have a server component. You can point your git client to a remote place where it can store its files using SSH. But you don’t install anything on the server for this.

Which is why self hosting a git remote is super easy. All you need is a server with ssh and a little bit of storage.

If you just want to sync code between different computers and have a backup, that’s all you need.

Repeating what they heard is very different from automatically processing the chat to harvest personal information about the participants.

Just because some data is publicly available doesn’t mean all processing of that data is legal and moral.

You’re both getting side-tracked by this discussion of recording. The recording is likely legal in most places.

It’s the processing of that unstructured data to extract and store personal information that is problematic. At that point you go from simply recording a conversation of which you are a part, to processing and storing people’s personal data without their knowledge, consent, or expectation.

Money does not equal capitalism. Money existed a thousand years before the invention of capitalism.

I dream that the reason AMD delayed their launch and are being so cryptic, is because they saw how underwhelming the 5080 was and decided to make a card (perhaps a 9070 XT) that matches its performance at the price of a 5070 or something.

Now I don’t think that will happen. Their previous market strategies have been very uninspired. But there’s certainly an opening here to make a play for market share and make Nvidia look like greedy fools.

Why upgrade from a 4080 to a 5080?

What are some of the outstanding issues that haven’t been addressed? I feel like there are genuinely good ways of doing everything these days

They’ve done amazing work trying to turn the clusterfuck they started with into a good language

I tend to write guthub.com and then chuckle to myself imagining a social network where people have beer bellies as their profile pictures

Yup, just like a library

I’ve never seen a place selling books not have them organized alphabetically! They might not be libraries but they have an interest in their customers being able to find what they’re looking for

You really can’t though. For several reasons. Which would have been apparent to you had you bothered to actually create your example link to http://аpple.com or to understand this problem.

This is likely because docker runs Linux in a VM on MacOS right?

We’ve had similar problems with stuff that works on the developers Mac but not the server which is case sensitive. It can be quite insidious if it does not cause an immediate “file not found”-error but say falls back to a default config because the provided one has the wrong casing.

Well completion-ignore-case is enough to solve this particular problem, the other options are just sugar on top :)

I’m going to add completion-prefix-display-length to these related bonus tips (I have it set to 9). This makes it a lot easier to compare files with long names in your tab completion.

For example if you have a folder with these files:

FoobarSystem-v20.69.11-CrashLog2022-12-22 FoobarSystem-v20.69.11.config FoobarSystem-v20.69.12 FoobarSystem-v20.69.12-CrashLog2023-10-02 FoobarSystem-v20.69.12.config FoobarSystem-v20.69.12.userprofiles

Just type vim TAB to see

 ...1-CrashLog2022-12-22   ...1.config   ...2   ...2-CrashLog2023-10-02   ...2.config   ...2.userprofiles
$vim FoobarSystem-v20.69.1

GNU Readline (which is what Bash uses for input) has a lot of options (e.g. making it behave like vim), and your settings are also used in any other programs that use it for their CLI which is a nice bonus. The config file is ~/.inputrc and you’d enable the above mentioned options like this

$include /etc/inputrc

set completion-ignore-case on
set show-all-if-ambiguous on
set completion-map-case on
set completion-prefix-display-length 9

I and l also look identical in many fonts. So you already have this problem in ascii. (To say nothing of all the non-printing characters!)

If your security relies on a person being able to tell the difference between two characters controlled by an attacker your security is bad.

I believe that type of stuff is specified in your locale, so it’s possible that it would do the right thing if you’ve set your language to Turkish. Please try it and let us know though :)

If you did it would likely break something as it’s one of only two characters not allowed in a file name (the other being null).

You can do a lot of funky stuff within the rules though, think about control characters, non-printing characters, newlines, homographs, emojis etc. and go forth and make your file system chaos!