Haha you see, that's the trick: It's not your game. Our corporate overlords in their absolute perfection merely granted you permission to temporarily enjoy their impeccable creation. Hail them.
You will own nothing and you will like it. See this new amazing GamePassCloudStreamXNextWowUltime service we're offering? It's super cheap! (For now.)
Could you provide more info? On what grounds?
Well, according to ark the J4105 also only supports 8G and mine's been running 16G ever since I got it.
I can tell you that my Celeron J4105 (the N100's predecessor) can run paperless and most other NAS/home server tasks just fine. I haven't dabbled with Immich and its ML though. The 10W are pretty accurate. With hard drives, HBAs and PSU inefficiency, my home server comes out to about 20W from the wall under full load IIRC.
Also look out for RAM extensibility; you probably want 32GB in the not too distant future.
They claim this one talks to Apple's servers directly without proxy and therefore does E2EE.
See https://blog.beeper.com/p/how-beeper-mini-works
They do claim to use a custom-built proxy for push notifications (Apple's push notifications obviously won't work on Android) but that's a helluvalot less critical than a message content proxy.
Given their previous behaviour, I'll only believe that when an independent security researcher confirms that the app's code actually implements the iMessage protocol with E2EE as they claim.
Correct. However, the instance will contain any federated content it knows of aswell. As long as there is at least one subscriber to the community from your instance, you should be able to find the community's posts.
Indeed. You should rather post the blog post itself then; it explains that they're posting it a couple months after the release.
I still don't see any value in posting a blogspam article announcing the release from 4 months ago with little to no extra insights that the actual new thing (the blog post) contains.
These can however get stuck sometimes. It's harmless but you can fix it by re-subscribing and then reloading the page.
For myself, I just created a !lemmy custom bang in Kagi with this URL:
https://lemmy.ml/search?q=%s
(URL encoding on.)
You can replace the domain name with your instance's and it should work the same.
Kagi is great.
This release is from August. What you linked is probably just auto-generated blogspam.
The e-privacy directive is not a thing yet.