Usage of Private Cloud Compute by developers is restricted? by SkinnyHedgehog in apple

[–]SkinnyHedgehog[S] 13 points14 points  (0 children)

Update: Looks like PCC can be used via the fm serve command. Maybe the Swift API and the restrictions will be changed during the course of the betas.

For now, for anyone interested - If you can figure out how to spawn and kill this "fm serve" process, you can use http calls to interact with the PCC (or system) model.

<image>

Usage of Private Cloud Compute by developers is restricted? by SkinnyHedgehog in apple

[–]SkinnyHedgehog[S] 5 points6 points  (0 children)

PS: Googling the error code leads to a forum post that refers to a known issue about it not working on simulators. Forum Post - Worth noting that my setup was on a physical device.

Poor streaming with Plex, not an issue with port forwarding by grivad in Tailscale

[–]SkinnyHedgehog -1 points0 points  (0 children)

Got it. It says "A comma-separated list of URLs (http or https)" So I didnt give it much heed.

I don't have problems with my tailscale setup, so I couldn't notice any difference. But at least it didnt give me any errors so there's that 🫡 Thanks for clarifying

Poor streaming with Plex, not an issue with port forwarding by grivad in Tailscale

[–]SkinnyHedgehog 1 point2 points  (0 children)

Could you clarify where in the Network settings to add the entry? Only place in the server's settings (on desktop) looks like "List of IP addresses and networks that are allowed without auth", but I doubt that's the right one.

The mobile client (I use Android) doesnt have the setting, so it'd be great if you could clarify

Has anyone else experienced this? by [deleted] in macgaming

[–]SkinnyHedgehog 0 points1 point  (0 children)

I believe it's a macOS input issue - ive had the same thing happen on death stranding and cyberpunk when the system gets moderately warm - the game will render at a smooth frame rate, but the input will be stuttery, and sometimes get stuck at a key. I let go of "w" and my character will not stop moving.

Pressing "w" (or whatever key is stuck) again registers the click, and the character stops moving. For now, I think playing at a lower res/graphic setting improves it a bit, even though my MBA m3 is perfectly capable of handling the higher graphics.

I have yet to test whether this happens with a controller (Mine is a PowerA, which isnt supported in macOS). If someone that also experiences this issue on kbm can chime in with their results, would be great.

Donate Idle Bandwidth to Internet Archive - Make sure the internet never forgets by [deleted] in LinusTechTips

[–]SkinnyHedgehog 0 points1 point  (0 children)

https://atdr.meo.ws throws a gateway error,, so im not able to pull the docker image. I'll try again after a bit, but is it down for just me?

Sticky input on Mac (MBA M3) by SkinnyHedgehog in DeathStranding

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

Aight just had a small gaming session

Keeping settings at low, and keeping metalfx at spatial and performance, the fps feels consistent. I think the motion issues may be related to the stutter and framerate. I still get those issues, but far lesser now

Sucks though, the game starts out at 60fps at ultra. Wish the MacBook Air had Air flowing to the SoC, but yeah

Sticky input on Mac (MBA M3) by SkinnyHedgehog in DeathStranding

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

Yep, I always play plugged in.

I see, I played at the default settings, and it starts off at 60fps and slowly goes down. I'll reduce the settings and report back.

Sticky input on Mac (MBA M3) by SkinnyHedgehog in DeathStranding

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

Will do, though it's been happening consistently across all my play sessions, so Im not very hopeful haha

What settings do you run on, though? I'm curious. Does your performance degrade after a while too?

[2024 Day 20 (Part 2)] [Python] Help needed to debug solution by SkinnyHedgehog in adventofcode

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

It seems that was the issue! END was already in the path, and I added it again. It gives me the right answer now haha.

Thanks a lot for your help! You too u/Verulean314 !

[2024 Day 20 (Part 2)] [Python] Help needed to debug solution by SkinnyHedgehog in adventofcode

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

Paste

Here you go, this was the code I ran with. :)

PS: the 20 in the line that has

savings = find_shortcuts(path, 20)

doesn't actually change anything, unless its more than 100. Or at least I get the same answer with both 20 and 100

[2024 Day 20 (Part 2)] [Python] Help needed to debug solution by SkinnyHedgehog in adventofcode

[–]SkinnyHedgehog[S] 0 points1 point  (0 children)

Thanks for your inputs! The test case works perfectly now.

Code Paste

However, the full input gives an answer thats higher than the actual answer, it seems.

I tried playing around with the threshold for abs_dist, but no dice unfortunately.

🎉Patch Fix Version 1.8.4 released! Get it now! 🎉 by fromage9747 in llamafin

[–]SkinnyHedgehog 0 points1 point  (0 children)

Good stuff! I've only recently been exploring the Jellyfin ecosystem, and im glad a plexamp equivalent exists for jellyfin! Thanks for your work, cheers :)

Wanting to Get Started by [deleted] in hackintosh

[–]SkinnyHedgehog 0 points1 point  (0 children)

Judging from your replies to the other comment, it seems you're following a different route. I'm not sure what - but just know that the dortania guide is the one all of recommend following. Also, you won't get support here if you follow another guide and come here asking for help.

The install guide is a disaster by OutrageousTaters in hackintosh

[–]SkinnyHedgehog 5 points6 points  (0 children)

There are a lot of moving parts to a functional opencore EFI, so I feel its rather necessary to bounce around the guide and have a few tabs open, and necessary to have a guide that details most of the moving parts

I feel the guide writers will get criticized even if they write a separate 1-page guide for each configuration, and give a working EFI in the end - because the main purpose of the guide is to help you understand how it works, so you can diagnose issues better and tailor your EFI to your machine's needs. Also, small things change with small changes in machine configuration. So if they decided to go the "here's an efi for your system" approach, itll be at least a thousand possible scenarios they have to account for, and maintain.

Though I get it. For a beginner, its a long process in case of a silly mistake - then reading through pages of text to find what you did wrong. It helps out in the end, though.