840 karma · joined July 20, 2013
>>>
Send to Kindle supports the following document formats: Adobe PDF (.pdf) Microsoft Word (.doc, .docx) Rich Text Format (.rtf) HTML (.htm, .html) Text (.txt) documents Archived documents (zip , x-zip) and compressed archived documents MOBI (.azw, .mobi) (will not support the most up-to-date Kindle features for documents) JPEG (.jpg), GIF (.gif), Bitmap (.bmp), and PNG (.png) images.
Additionally, Send to Kindle emails now supports EPUB (.epub). Later this year, we’ll also be adding EPUB support to the free Kindle app for iOS and Android devices and the Send to Kindle desktop app for PC and Mac.
I abandoned and went back to Fedora, which is odd as I’d stuck with it through lots of other NVIDIA crap issues and such.
Hopefully adoption increases and one day I can use in a workplace setting.
https://news.ycombinator.com/item?id=29942900 (it's not my post, but it was the first one here and deserves a comment or two as it is interesting IMO)
I did have trouble with the results aligning correctly on mobile.
What isn't clear is how it inlines kernelspace, whether that surface area is optimized down etc
I also liked the writing style guides that Microsoft and Google put out in recent years:
https://techcrunch.com/2019/05/31/targeted-ads-offer-little-...
Surely the fact that 'disabling SELinux' is the top result on the subject in Google or StackOverflow will tell you that you would be in the minority of developers that like working with it and find it easy to do so.
I think there's more to it than just simply running an app without receiving an AVC complaint in auditd, you need to be able to test that the controls you put in place actually protect the application in some way, this does not come for free with audit2allow and other such generative tools.
& AWS are active in this area moreso with bottlerocket-os https://aws.amazon.com/blogs/opensource/security-features-of...
The recent release even incorporating the use of a feature I had previously dismissed as useless (MCS) is really quite neat https://github.com/bottlerocket-os/bottlerocket/discussions/...
Enabling it won't in itself secure your company's applications, as the default policies in Fedora only apply to installed services (e.g ssh) that have a policy written for them.
This is probably right on the boundary of the shared-security-model, but I think it would be great if they also offered easier ways for application developers to leverage the advertised feature.