How do i use it without an Airtag? At the step number 9 the setup asks me to enter an Apple ID, which i do not have. Is there a way to track it on Android or Linux without an Apple ID?
I've tried to create an Apple ID recently on a non-Apple platform and it was a huge PITA. Tried using different browsers on Windows and Linux, tried Apple Music on Android , tried iCloud on Windows - nothing.
Basically I was able to pass email and phone number verification, but then "Continue" button on the "Apple ID & Privacy " page doesn't work and you can't get around it. No error or description whatsoever, just internal server error in the browser's console.
Turns out it's a known problem and the same button works perfectly fine when pressing it on an Apple device. I haven't tried it in a macOS VM though, but presumably Apple flags such accounts anyway.
Yeah, Apple is crap that way. Whenever I log in from my Linux desktop, they "lock" my account and I have to go through a long process where I verify my email, phone, password, and they send me an SMS code.
If you want, I can create an account for you on my Mac, email me (email in profile).
The problem is unlikely to be around the corner for AMD since they do not have to supply as much voltage to their chips as as Intel to keep up since they are - at least when it comes to x86 chips - currently leading in performance and power efficiency
Which will likely affect performance as well, right? As I understood it, they were too ambitious with pushing performance using higher voltages, which now needs to be reduced using a microcode update?
Either performance or stability/reliability. Or even both.
At higher frequencies (during a frequency boost phase for example) signal quality in the digital signals degrades, because the "stable 1" or "stable 0" plateau is shortened and the "maybe 1 or 0" phase in between stays the same. So a signal that is supposed to be as rectangular as possible gets smushed down towards a sinus, and then smushed even further towards lower amplitudes.
One measure against this is of course better (faster) transistors, such that the "maybe" phase is shorter, but that only works by replacing the hardware. The other measure, which you can do during runtime, is to increase the signal amplitude by increasing the voltage. Then even a degraded signal close to the transistors' maximum switching frequency gets over the "stable 1" and "stable 0" thresholds fast enough.
With a lower supply voltage you can thus not clock the CPU as high as before which is important in boost phases during high load. Which would decrease peak performance in standard desktop and server workloads, and decrease overall performance in compute-intensive workloads. Or if you still clock it as high as before, signal quality will be lessened, increasing the probability of bit errors, lessening system stability and reliability of results.
Which direction intel will pick for this firmware upgrade, degraded-performance, degraded-stability or degraded-both, I don't know, I guess we'll see.
Maybe. I don't think anyone had information yet regarding the details. The extra power may have been just pure waste, rather than a performance improvement.
Unless I missed a real investigation posted somewhere?
> for AMD since they do not have to supply as much voltage to their chips
... unless you're using EXPO/XMP. I would really recommend people who run automatically overclocked memory taking a closer look at how much voltage the motherboard is pushing into your CPU, especially into the SoC. Some motherboards just push the voltages to the absolute permitted maximum; ASUS is particularly bad at this. I run lower RAM frequencies than my system is capable of because I haven't seen much performance improvement above 5600 "MHz", and it can be made to run at almost stock voltages.
It definitely causes faster silicon degradation; the question is how fast it will kill the processor. Both Intel and AMD have shown us that it can happen very quickly, not in the course of several decades as we've assumed for the longest time.
There are two apps from Fuji and i heard the newer one works better but the older one does not work for transferring pictures 70% of the time and unfortunately my camera is not supported in the new "Fujifilm X App"
Xapp works as well as I believe Apple lets them on iOS. You need to connect via the app, tap an iOS “Join WiFi” dialog, then 30-70% through the transfer it will stop and you need to tap again “This WiFi doesn’t have Internet, disconnect or continue?” and then it succeeds most of the time.
Don’t even get me started on Fujifilm refusing to support Geotagging unless the iOS app is in the foreground though. That is entirely Fuji’s fault and their design choice because apparently users complained that “it was tracking my location when the app is closed” uh duh that’s how geotagging works, turn off location if you don’t use it.
I have both the XT4 and the XH2.
I’m still surprised that in 2024 these big cameras don’t have a built-in something that does gps and sets the time correctly. The current time is floating in the air in radio waves. And gps units are small and with many low power options. Super annoying when you’re traveling around across timezones and suddenly all your photos are in the wrong time zone if you didn’t update it. Or if there is daylight savings update… And for gps, even a ballpark 1km gps range would be better than nothing.
Well that's not quite true. You can do a few things:
1. Reduce dependencies and features of dependencies
2. Use a faster linker like mold
3. Use a faster compiler backend like cranelift(if possible)
4. Use the parallel compiler frontend(again if using nightly is possible)
5. Use sccache to cache dependencies
But i do get what you mean. Especially in CI the build times are often long
Oh that is awesome!
I've used the cloud version previously but now that the desktop version is free with some small limitations i think I'll probably use it instead of Ghidra
Well while esp-idf is powerful and has awesome features it also provides attack surface. And for me an additional advantage that no C code is below and it's fun!
Honestly the biggest issue with Linux desktop right now is that Xorg is still more compatible and widely used. I tried Wayland on multiple machines and always had trouble when using it on my Laptop with no way to switch between integrated and dedicated Graphics cards(on X i always used optimus-manager which works fine 99% of the time).
I can't wait to finally switch to Wayland when those issues are fixed.
