1,899 karma · joined May 9, 2016
That of course assumes time is free, so I wouldn't compare it to cloud pricing directly. I'd also personally budget in incremental backups.
Is there a way to compile this as a native library? I imagine some of the work should be reusable.
I just wish these groups making fan-made builds would share at least patches, so they don't become gatekeepers and others could build on their work.
Here's a marketing page for a WIP pan-EU project to implement this kind of digital ID: https://commission.europa.eu/topics/digital-economy-and-soci...
There are also various plans for age-verification schemes that should (partially) preserve anonymity, but those aren't implemented and it's not what people mean by "digital ID".
Information that was previously in paper form and scattered across various bureaus is now being digitised and centralised, but that's orthogonal to "digital ID"!
I feel like what you mean by "digital ID" is very different to what others mean.
Caring about the products you use is pretty standard behaviour, and when the product changes under the user's hands, it's normal to complain. It can resolve the issue faster and less painfully than switching products would.
I've read the article and don't see anything dangerous, much less extremely so. Care to explain?
That's not to say Fediverse-style moderation would solve this. I don't really know what the solution is for algorithmic feeds. Personally I'd rather go back to lightly-federated or unfederated forums, but that idea seems sadly unpopular.
Social media is often seen as a public opinion manipulation machine, but I hope building another one of those is not the goal.
When almost everyone has access to something and you are singled out and denied that access (without due process), then there's a problem, discussions on the definition of monopoly notwithstanding.
You can try to fix that by ensuring the process is fair and transparent, or by changing the market so that there is no single entity whose services almost everyone uses.
I don't really see my posts remaining in people's RSS readers after deletion as a problem. It's a fundamental property of information distribution as far as I am concerned.
I strongly dislike this, since you always have to be careful not to make some unwanted change. When checking permissions, you have to check before you modify the object. You can't modify it and then run some permission checker. You also can't easily keep the old version around.
Sadly it seems most ORMs follow this style, and that Django's is the odd one out.
Pretty soon after the railways were opened to non-state operators, quality of long-distance train routes improved, both by new trains by private operators and increased competition forcing ČD to improve. On regional railways, where the state pays for train operations, costs have gone down thanks to competition. It seems to me like this model can work well, you just need an infrastructure operator that's receptive to its "customers" (which SŽ often isn't), or a political structure that can force them to listen.
So if you're doing it "properly", sorting strings in Czech involves understanding the etymology of every word.
- Allow configuring the controls. For example, the multi-purpose "focus" ring is great, but is severely hampered by having to press the "iFn" button every time.
- Add bulk upload of photos to Immich (though that could just as easily be an external script).
- Write custom widgets for the LV view, like a RAW histogram or time display. Also hide the bottom buttons that have already burned into my screen.
- Allow full electronic shutter (I already had to change this camera's shutter once).
- Add highlight metering, or rewrite the autoexposure entirely.
- Support outputting raw video.
- Tone down the denoising on out-of-camera JPEGs.
- Play with custom sensor crops, line skipping and other things to get zoomed in videos.
Personally I think the NX300/30/2000 are the most hackable cameras ever made, even compared to the NX1/500. The read-only rootfs isn't really a barrier, since the software runs a shell script from the SD card on boot (or rather resume from hibernation, it's a pretty clever system). And unlike the newer models, they don't have an RTOS coprocessor, so everything is handled in the easier-to-modify Linux code. It's not a design decision I would have made, but it makes in-depths mods easier.
The older cameras are also easy to unbrick, since the bootloader files used for firmware flashing without a working OS were released in the FLOSS code dump. The availability of some C headers in that dump is the cherry on top.
I'll admit I'd still rather have an NX500, I just bought the NX300 because I'm cheap :)