Fredy 25.0.0
Fredy bridges the summer lull by watching prices instead of the sun.
Nobody moves in August. Landlords know it, and they start quietly nudging their asking prices around to see what sticks. Fredy now notices.
Price tracking
Fredy can re-read the price of listings you already found, keep the history, and tell you when one moves. You get the old price, the new price, and the percentage, delivered through whichever notification adapter you already use. All seventeen of them learned to speak price change, from Telegram down to the SQLite adapter.
In the listings overview, a changed price gets a small green or red badge. On the listing itself there is a chart of how the price actually developed, so you can tell a genuine reduction from a landlord who raised the price last week and "reduced" it back today.
Thanks to Alpha63 for [#384](#384).
Turned off, and it stays off until you say otherwise
Reading a price means opening a real browser page for every tracked listing. That is a considerably heavier knock on the portal's door than the existing "is this still online?" check, and portals notice people who knock too often.
So it is off by default, it lives under Settings -> Execution. The defaults check every seven days, at most a hundred listings per run, and you have to go out of your way to make them more aggressive. There is also a notification threshold, set to 1%, so a landlord rounding 1.201 down to 1.200 does not wake you up.
Fair warning about the parts that are not covered: ten of seventeen portals can be price tracked today. The rest either hide the price somewhere no extractor can safely reach it, or aggregate so many landlord sites that any extractor would be guessing. Guessing is exactly what you do not want here, because a wrongly read price does not fail loudly, it just quietly writes a fiction into the history of every listing from that portal. When in doubt, Fredy reads nothing at all.
Docker starts again on a fresh install
If you ran Fredy in a container without bringing your own config, it crashed on startup with ENOENT: no such file or directory, open '/fredy/conf/config.json'. The code that creates a default config was there all along. It simply ran one step too late, right after the step that already needed the file. Nobody developing locally ever saw it, because the repository ships a config.
Thanks to TomErnst1972 for [#389](#389).
Previous Release: Introducing ÖPNV to Fredy
https://github.com/orangecoding/fredy/releases/tag/24.0.1