jadero

joined 1 year ago
[–] [email protected] 23 points 4 months ago

They are just the biggest asshole in the room.

So one day the different body parts were arguing over who should be in charge.

The eyes said they should be in charge, because they were the primary source of information about the world.

The stomach said it should be in charge because digestion was the source of energy.

The brain said it should be in charge because it was in charge of information processing and decision-making.

The rectum said nothing, just closed up shop.

Before long, the vision was blurry, the stomach was queasy, and the brain was foggy.

Assholes have been in charge ever since.

[–] [email protected] 3 points 4 months ago

Thanks! Once I knew that there was such a thing, a bit of online searching got that part of it sorted. And took me into what I hope is a productive rabbit hole of permissions management. :)

[–] [email protected] 1 points 4 months ago

That's what I worked through this morning. I learned elsewhere in these comments that users have both names and IDs and that docker references IDs.

I've changed ownership of the files and folders a few times. First to match the default setting in docker-compose.yaml, then as I tried different user IDs. Always the same message.

I did additional research and found references to something known as "mounting volumes", but have not yet had a chance to explore that angle further. It's not mentioned in the GTS documentation that I can see, so I just assumed (I know...) that the .yaml file was taking care of it.

At this point, I suspect that there is something else going on, possibly with ports. I had to do a bit of fiddling with ports to kill a bind error resulting from the fact that there is another service hooked up to ports 80 and 443. I'm only guessing, but maybe it's unable to create the database because it needs to do so via those ports. That doesn't sound quite right to me, but it's not like I have any real clue!

One thing I noticed is that docker-compose is recommended by GTS, so I installed it and that really blew up in my face, so I went back to docker compose as I've used elsewhere.

Research continues...

[–] [email protected] 2 points 4 months ago (2 children)

Oh, that user ID must be the answer. I was wondering what those numbers were ☺️

More digging to figure out what the appropriate user id is...

[–] [email protected] 2 points 4 months ago

Ok, thanks. I was hoping that it was specific to GTS, because that's more my speed. I've been through the docs, but obviously not carefully enough! I'll give it another go...

 

I have a Bluesky PDS running successfully. Now I'm trying to set up GoToSocial, an ActivityPub server that also uses sqlite. When I run

sudo docker compose up -d

I get the following error in the docker log for GoToSocial:

Error executing command: error creating dbservice: sqlite ping: Unable to open the database file (SQLITE_CANTOPEN)

Is this more likely to be a conflict between the two docker applications or something specific to GoToSocial? (I've gone through the sqlite issues I've been able to find in GoToSocial's GitHub.)

If something to do with running sqlite in two containers, do you have any tips to resolve the issue?

[–] [email protected] 2 points 4 months ago

Amazon allows 2FA, but I'm pretty sure they don't require it.

[–] [email protected] 8 points 4 months ago (2 children)

I have seen some that seem to be doing that kind of thing, but many others that will reject a bad username before asking for a password.

To double check, I just now tried putting a known bad email address into the username field for amazon.ca and was not then asked for a password, but told that no account could be found.

My possibly flawed understanding of login security is that a failed login should reveal nothing about why the login failed in order to prevent information leakage that can be exploited.

[–] [email protected] 19 points 4 months ago (4 children)

And yet more sites do it, even on desktop. As far as I can tell, most of them are also doing it in a way that breaks security by validating the username before asking for the password.

[–] [email protected] 6 points 4 months ago

I think you mean "OAUTH" not "OATH". That might make your search for information easier.

Sorry, I don't know much about OAUTH and even less about Mastodon.

[–] [email protected] 6 points 4 months ago

FFS, and here's me celebrating the fact I can tie my own shoes.

[–] [email protected] 3 points 4 months ago

Then I must be among the manliest of men. :)

I learned all the different ways to use the keyboard in Windows and never looked back. The best of both worlds, although relearning everything now that I've switched to Linux is proving a challenge. I'm starting to think that the Linux GUIs don't have true keyboard accessibility.

[–] [email protected] 1 points 4 months ago

Why not? The last decade before semi-retirement I had all the different ways to get in touch with me restricted to my phone. My work computer had no email client, no messengers, nothing. I even helped lead the charge to eliminate desk phones.

That little display may have been the single greatest priductivity booster ever. It stayed on a shelf across the room on do not disturb. The only people allowed past the DnD were my wife and my son. If there really was a work emergency, a manager or coworker knew where to find me to tap me on the shoulder.

 

cross-posted from: https://programming.dev/post/5838448

I came across this semi-randomly by using Search Marginalia to find information on functional programming courses.

I also very much enjoyed the two articles referenced in the footnotes.

 

cross-posted from: https://programming.dev/post/5838448

I came across this semi-randomly by using Search Marginalia to find information on functional programming courses.

I also very much enjoyed the two articles referenced in the footnotes.

 

I came across this semi-randomly by using Search Marginalia to find information on functional programming courses.

I also very much enjoyed the two articles referenced in the footnotes.

 

From Cult of the Dead Cow, Veilid allows anyone to build a distributed, private app. Veilid will give users the privacy to opt out of data collection, and online tracking. Veilid is being built with user experience, privacy, and safety as our top priority. It will be open sourced and available to everyone to use and build upon, with flagship apps available from the launch.

view more: next ›