dgw
The latest release workflow failed for some reason: https://github.com/P3TERX/GeoLite.mmdb/actions/runs/12308514546 ``` 👩🏭 Creating new GitHub release for tag 2024.12.13... ⬆️ Uploading GeoLite2-Country.mmdb... ⬆️ Uploading GeoLite2-City.mmdb... ⬆️ Uploading GeoLite2-ASN.mmdb... Error: Request body...
#18 merged; the 2024.12.19 release has been updated with the assets. This seems to be resolved now.
#18 merged; the 2024.12.19 release has been updated with the assets. This seems to be resolved now.
Amended because of bug in new `I300` check as described at PyCQA/flake8-import-order#214
> One thought would be to unlock the "advanced" logistics warehouses (active provider, buffer, requester) by crafting a requester chest since you can have research unlock with items This unfortunately...
> * Plan C is to inject warehousing into logistic robots and construction robots during the data-final-fixes .. but that's nasty, and feels worse than making something dependent on something...
Having not made any progress on other alternatives that I like, I present #113 (simple option) and #114 (complicated, maybe-overengineered option). Downside to #114 is it adds 8 (!) new...
> Why not make the tech unlock be this Because I don't like `craft-item` unlocks, and they still have the same problem as prerequisites re: multiple/alternate pathways to the same...
The tooltip appears if I tap the timestamp, at least on my particular phone/browser combo. Seems usable.
It continues: https://privacysandbox.com/news/update-on-plans-for-privacy-sandbox-technologies/ > After evaluating ecosystem feedback about their expected value and in light of their low levels of adoption, we've decided to retire the following Privacy Sandbox technologies:...