diff --git a/journals/2026_01_18.md b/journals/2026_01_18.md
new file mode 100644
index 00000000..9aa5e92e
--- /dev/null
+++ b/journals/2026_01_18.md
@@ -0,0 +1,12 @@
+progress:: {{renderer :todomaster}}
+icon:: 📅
+boox-notes:: ![BOOX Notes](../assets/../../onyx/TabUltraCPro/Notepad/JOURNALING.pdf)
+
+	- ### Tasks
+		- {{query (and (task TODO) [[18-01-2026]])}}
+		  query-table:: true
+		  query-properties:: [:block]
+		- ...
+	- ### Notes
+		- ⌛Generating....
+		-
\ No newline at end of file
diff --git a/pages/JSSOFTWARE-D-25-01678.md b/pages/JSSOFTWARE-D-25-01678.md
index fb2c7389..e04007c8 100644
--- a/pages/JSSOFTWARE-D-25-01678.md
+++ b/pages/JSSOFTWARE-D-25-01678.md
@@ -21,5 +21,4 @@ todoist:: https://app.todoist.com/app/task/jssoftware-d-25-01678-6fGCW438gGXcpFR
 			- The paper is not entirely self-contained, which may hinder its accessibility for readers outside the specialized privacy engineering community. From a software engineering perspective, it remains unclear how these findings can be operationalized in practice. The authors should clarify how a development team can employ these results to improve system design in a real-world context.
 			- The generalizability of the analysis is questionable; the authors should discuss whether the simplifications made during the DFD modeling phase significantly skewed the assessment results or if the findings remain robust across different system architectures
 		- Please give a frank account of the strengths and weaknesses of the article: This paper provides a critical, transdisciplinary evaluation of a leading privacy framework (LINDDUN) applied to a high-impact societal shift. However, as a practical guide for software engineers, its utility is limited by its abstraction from implementation details and its heavy reliance on external framework knowledge.
-			- 🦙Generating ...
 -
\ No newline at end of file