redcalcium

Checking lemmy.world federation status at: https://phiresky.github.io/lemmy-federation-state/site?domain=lemmy.world . There, you can see that social.packetloss.gg is listed among the "407 failing instances".

You'll need to check if your server actually configured to receive federation traffics. If you're using cloudflare or some other web application firewall, make sure they're not doing any anti bots measures on the /inbox endpoint. For example, in Cloudflare, create a new WAF rule (Security -> WAF) for /inbox and set it to skip all security.

If you don't use any web application firewall at all, did you just upgraded your instance from v18.x to v19.x recently right before experiencing federation issue? v19.x has increased resource consumption and will have problem running on small server after running for a while. For small VPS (~4GB of RAM), you might want to adjust database pool_size to <30 on lemmy.hjson file. Restarting lemmy AND postgres every once in a while also helps if you're on a small VPS.

What's the point of planning to integrate with activitypub if they do shit like this?

Creators must disclose content that:

Makes a real person appear to say or do something they didn’t do

Alters footage of a real event or place

Generates a realistic-looking scene that didn’t actually occur

So, they want deepfakes to be clearly labeled, but if the entire video was scripted by chatgpt, the AI label is not required?

Because there is no demand, display manufacturers don't produce small phone displays anymore. And because there's no small display in stock, phone manufacturers have given up on producing small smartphones. Technically, you can contract the display manufacturers to restart production of small phone displays, but no one seems to be interested in taking the upfront risk.

But there is law governing how you store your firearms and ammunition, so kids can't access them, right? It's not true freedom then /s

I'm often blinded by flickering due to the recent Nvidia issue on Wayland so it's still accurate.

I think that's the icon for archived posts, not ads marking.

Mostly for convenience and standardizing your security procedure. Most apps popular for self hosting now supports OIDC, so it's no brainer to setup. On the other hand, most apps don't support 2fa, or support it in a weird way (e.g. no recovery code). By using an identity service, you can be sure all your apps follow the same login standard you setup.

For those apps that don't support OIDC, you can simply slap oauth2proxy in front of it and it's done.

If you have some error message, it would be easier to identify the issue. Typical problems:

• incorrect redirect url
• incorrect endpoints on gitea. I haven't used gitea yet, but keycloak changes their openid configuration endpoint from [your host]/realms/[your realm]/.well-known/openid-configuration/ to [your host]/auth/realms/[your realm]/.well-known/openid-configuration/, and some apps still use the old one. You might be able to correct this by manually entering keycloak endpoint in your oidc settings.

Currently it's using ~511MB of memory, which is comparable to typical web apps. CPU usage is almost zero because it's idle most of the time (you're practically only using it on login only).

I'm still on keycloak v19 and haven't had a change to upgrade to the latest version yet and have no idea how much memory the latest version will use, but I remember testing keycloak before they migrated to quarkus and it was sitting at ~2GB memory and was immediately turned off by it. I gave it a try again after I heard the memory usage got better and stick around since then.

Keycloak seems complicated, but it's actually not that complicated if you use it for simple OIDC provider.

Just create a new realm, then go to client -> create. Enter your client-id, with openid-connect as protocol. Then, set access type to "confidential", set valid redirect uri to "https://" (or even "https://*" if you're lazy and want to use it on multiple apps). Then hit save and go to the credential tab to copy your client secret. Then head to "users" menu to start adding users to your realm.

That's the basic setup which should be good for home use. The good thing about keycloak is, as you grow your homelab, whatever stuff you may need later can be provided by keycloak. Want some users to have access to app A, but not app B? 2 factor auth? Allow users to login with google account? Heck, allow users to login with another sso provider (chaining)? You can do pretty much anything.

Multiplayer games? Freedom wars, soul sacrifice delta, toukiden, various warriors games (e.g. dynasty warriors, samurai warriors, pirate warriors, etc), Darius burst, Spelunky, dragon's crown,

My favorite single player games are: muramasha rebirth, odin sphere, tearaway, persona 4 golden, rogue ace, luftrausers, rogue legacy, steam world, binding of Isaac. Vita has a strong collection of indie games.

The vita can be unlocked to run homebrew/emulator, overclock,and to use SD card instead of the pricey Sony proprietary card. Check out https://vita.hacks.guide if you want to learn more. People also ported various games not released on vita such as GTA San Andreas, Bully, etc. check out https://github.com/MuxaJlbl4/Awesome-PlayStation-Vita and https://www.gamebrew.org/wiki/List_of_Vita_homebrew_games for more.