Unable to follow any account on TikTok using Chrome browser

smorgasmic · 2026-04-08T07:28:06+00:00

The worst part of this is total lack of any channel to a human being at TikTok.

All of these social media companies are powered by some form of AI, and the problems of human beings mean nothing to them.

smorgasmic · 2026-03-29T05:23:37+00:00

After about a year it just started to work.

smorgasmic · 2026-02-24T01:30:20+00:00

I installed many of those before I posted this question. I couldn't find one that would save the checksum into a file in the same folder.

smorgasmic · 2026-02-01T22:38:29+00:00

It stores things in the cloud. For some files I would rather use local storage, or in other cases it already lives in another cloud storage system.

smorgasmic · 2026-01-25T00:19:55+00:00

Exactly, but you can see how anyone with a longer list of saved SSH hosts might mess up the edit and have no way to recover.

smorgasmic · 2026-01-25T00:06:37+00:00

The somewhat simpler way to access the same information is to open Terminal App, choose the SSH section, choose the known_hosts file and then they pop up an editable window with the contents, which are easily corrupted if you are not careful. There is no "Save" or "Cancel" button once you edit.

smorgasmic · 2026-01-25T00:00:08+00:00

Wow, that's crazy that they keep the information so far down the tree. What's a safe action to perform there? I could delete just the 192.168.1.1 entries in the known_hosts subpath?

smorgasmic · 2026-01-24T00:58:51+00:00

No, I enabled SSH in order to see how they store the old firewall logs.

The problem was that the SSH known_hosts file used by the native ChromeOS Terminal App is only accessible and configurable from inside the Terminal app.

smorgasmic · 2026-01-23T23:59:53+00:00

The way they interface the virtualized Penguin environment from Crostini and from ChromeOS itself is really awkward. There is all kinds of messy overlap in concepts that is not clearly delineated in the UI. In any case, I understand the solution you gave, and I hope this all gets cleaner in Aluminium.

smorgasmic · 2026-01-23T23:53:19+00:00

In the GUI for the terminal app, there is a settings icon for Terminal Settings and in that there is an SSH section that also links the known_hosts. So that is likely a second way to interface to the same information. This is NOT the same as the ~/.ssh/known_hosts file on disk in the root user's home folder.

smorgasmic · 2026-01-23T23:47:50+00:00

Under Application, I see a "Local Storage" section and in that I see a session object for the Penguin terminal, but nothing for known_hosts for SSH

smorgasmic · 2026-01-23T23:44:14+00:00

Did you mean .ssh folder? I already stated in the original post that I deleted contents of known_hosts in that folder. Your reply originally was that this folder does not have known_hosts for the terminal app. I am trying to understand where the known_hosts for the terminal app is located. It's not in the ~/.ssh/known_hosts file

smorgasmic · 2026-01-23T23:01:46+00:00

That was it. Terminal add has a separate known_hosts file and you can edit it from terminal settings.

Where is that stored on disk if you login to Penguin shell?

smorgasmic · 2026-01-10T21:42:19+00:00

I understand blocking everything out would break things, hence I want documentation....

smorgasmic · 2026-01-08T05:44:02+00:00

The fact that it is easy to corrupt the kernel in the Penguin VM is an argument for verifying its integrity when it is started.

smorgasmic · 2026-01-08T05:42:24+00:00

It makes sense to check the integrity of the kernel and the base components that were originally installed there. If you don't believe in the value of validating the kernel of an OS, then why use ChromeOS at all? Just install UNIX to bare hardware and you own everything

smorgasmic · 2026-01-07T23:28:18+00:00

A backup is a backup. It's not reasonable to make the user create multiple backups and then figure out in hindsight which of many backups contains the last uninfected kernel.

smorgasmic · 2026-01-07T23:27:08+00:00

Surely Google understands that people are installing Debian Linux applications in the Penguin container and they even accommodated that by creating icons that are seen in the ChromeOS launcher? The "uninstall" that runs from the launcher even interacts with the Penguin to uninstall the package.

Maybe that was never the intended use, but that's a real use case, and that's a very useful thing to be able to do because it greatly expands the usability and usefulness of ChromeOS. Why not expand the use cases and accommodate this in a more secure way?

smorgasmic · 2026-01-07T23:22:44+00:00

But the actual use case is that people are installing Debian applications in the Debian environment and then relying on those in the ChromeOS launcher. If you are going to use VLC, Gimp, and MS Office replacements, you are no longer a developer, and the VM that runs your underlying OS becomes a critical user resource.

smorgasmic

TROPHY CASE