Fr0sT.Brutal

Good point! Probably I had found it but it didn't fit my needs. In my case it was my personal smartphone with thousands of SMS's stored so "Read all" would likely die in agony 🙂

I use Booleans as options for functions from time to time. Yes they add some guess work but defining a special enum type for every function is too hard for me. I hope I'll never deal with a library that would force me to do something like FindFiles('c:\', TFindFilesOptions.Subdirs)

Well, you're like "If a thief is managed to get into your house, it's already game over". But that's not true and "Home alone" proves it earnestly 🙂 Jokes aside, different cases require different measures. Your sentence asserts that any kind of software running on machines which limited users could access is a priori will be hacked. I don't think so.

1 - When using WinAPI editors (and Delphi VCL editors are WinAPI wrappers) for bulleting passwords, single SendMessage is enough to reveal them (at least it was in WinXP). 2 - Storing a password in memory in readable form makes it elementary to grab it by reading process' memory 3 - Signing a binary won't protect from #1 & #2 at all 4 - Just including protection library won't do any reasonable protection. Protection must be wisely integrated in the code level.

This is what RTL should've had since the early stage but recalling some really stupid bugs in RTL seems Emba/Idera uses customers for this purpose xD I remember to see a very very tiny project with unit tests but it was not more than v0.0.0.0.0.1

I'd extract metadata as SQL and try to create DB from it, then use DataPump to transfer data

If these files only need to be read by users, then any network storage (G drive, Dropbox etc), shared links to files and access via HTTPS is the simplest option

AT modem commands is good old way to send. There's also option to send via ADB (Android only of course, Apple sucks here). I didn't found a way to read messages from PC so I configured a task scripter on phone to catch messages and write them to a file which is accessible from PC

Before doing any deep optimizations, run benchmark to ensure that serialize really is the source of slowdown. Otherwise you could spend hours achieving nothing in the end

It's not always an equivalent. In our network, pings are routed by gateway so any PC without internet is able to ping any remote host

Generally it's true but timezone could be "global" per-app / per-DB (ideal case is UTC) I still can't get what you're checking. Global variables are bad practice anyway and in your case they appear useless. If StrToDateTime haven't risen any exception, you're already sure the date string is valid.

Generally, no AFAIK. But you can emulate some sort of this depending on what exactly you need

This really starts making sense in case of intensive user additions. If they are rare, sending patches aka diffs is the good-old way proved by decades.

+1 to the post above. Storing dates as strings is bad idea in most cases. Just don't do it. If you really REALLY have to do it, then use carved in stone format that won't depend on current locale settings. And don't forget the timestamps could contain timezones

In addition to things above, don't forget you can easily add "shortcut defines" just like temporary variables and use them instead of several IF's {$IF defined(cpu32) and defined(MSWindows) and not defined(Purepascal)} {$DEFINE UseAsm} {$IFEND} ... $ifdef UseAsm ...

I've solved this issue recently for console git, seems generating a token (described in details in GH help) and using it instead of password is well enough.

Try with HunSpell and this wrapper https://sourceforge.net/projects/nhunspelldelphi/files/

For example the same way as registry files do

Check the list of nice Delphi projects in my signature

Server has sent a response and broke the connection forcibly. I wouldn't bother as long as response being sent is complete

https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol and UPnP Alternatively, "dumb way" - get WiFi adapter IP and scan addresses in its subnet

Well you can't be sure client request has reached a server from client side until client starts receiving request. Usually client doesn't need anything more than "connect failure" (means server is unreachable or the whole network is down), "request-response network failure" (any network issues during communication) and "request payload failure" (message is correct but issued error on server)

So you receive garbage. You'll have to debug that stage

Just save the _stream to disc and see what it contains