![](https://lemmy.world/pictrs/image/92efb986-f47b-4c53-8690-0647886e93ac.jpeg)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
What kind of patch cables are you using here?
What kind of patch cables are you using here?
That is the best part; such confident incompetence coming back to bite them in the ass.
When a vulnerability at this level happens and a patch is created, visibility is exactly what you need.
It is the reason CVE sites exist and why so many organizations have their own (e.g. Atlassian, SalesForce/Tableau )
It is also why those CVE will be on the front page of sites like https://news.ycombinator.com to ensure folks are aware and taking precautions.
Organizations that do not report or highlight such critical vulnerabilities are only hurting their users.
If you go to your profile, there is a setting to turn it private; after that you should have an option on your posts to keep them private or public
I wish there was a simpler way to keep PixelFed private; I get that there is a lot of focus on the fediverse, but this can also serve as a private image/video sharing platform for close friends and family.
Being public by default creates a blocker for the average person joining it.
Does codium handle updates for the extensions?
This is what training new folks looks like. Even something as simple as a browser; watching someone click into the address bar and hit enter just to refresh the page, hurts my soul.
Does docker really spin up a VM to run containers?
Never understood homes that pave/block out all the greenery; makes the home depressing af all for saving some 30min of upkeep per week.
has anyone ran into errors with pict-rs throwing
0: Error in store
1: Error in object store
2: Error making request: Failed to connect to host: Failed resolving hostname: failed to lookup address information: Name does not resolve
when trying to upload to object storage?
I am running a minio instance and have other applications creating/getting without issue and confirmed that the credentials are valid for the pict-rs bucket - hitting a wall on what might be causing this
Can anyone share what bucket permissions they used for pict-rs? I am using minio and used the below policy for an access key, but am still getting unauthorized responses
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": [
"*"
]
},
"Action": [
"s3:GetBucketLocation",
"s3:ListBucket"
],
"Resource": [
"arn:aws:s3:::pict-rs"
]
},
{
"Effect": "Allow",
"Principal": {
"AWS": [
"*"
]
},
"Action": [
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::pict-rs/*"
]
}
]
}
Having grown up in the commercial tv era is why I despise ads.