-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathfeed.xml
98 lines (57 loc) · 11 KB
/
feed.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.2.1">Jekyll</generator><link href="http://localhost:4000/feed.xml" rel="self" type="application/atom+xml" /><link href="http://localhost:4000/" rel="alternate" type="text/html" /><updated>2022-01-02T23:11:42+08:00</updated><id>http://localhost:4000/feed.xml</id><title type="html">ZhaoCloud</title><entry><title type="html">SearX changed to SearXNG</title><link href="http://localhost:4000/to-searxng" rel="alternate" type="text/html" title="SearX changed to SearXNG" /><published>2022-01-02T00:00:00+08:00</published><updated>2022-01-02T00:00:00+08:00</updated><id>http://localhost:4000/to-SearXNG</id><content type="html" xml:base="http://localhost:4000/to-searxng"><p>My SearX changed to SearXNG.</p>
<p>It’ll report an error if you changed the settings before.</p>
<p>You can remove the cookies or go to preferences, then click save. (Yes, just click save, it’ll be okay)</p>
<p><img src="g:\Desktop\jekyll-theme-leaf\assets\220103.png" alt="" /></p></content><author><name></name></author><summary type="html">My SearX changed to SearXNG.</summary></entry><entry><title type="html">WE’RE ON MASTODON!</title><link href="http://localhost:4000/mastodon" rel="alternate" type="text/html" title="WE’RE ON MASTODON!" /><published>2021-11-20T00:00:00+08:00</published><updated>2021-11-20T00:00:00+08:00</updated><id>http://localhost:4000/mastodon</id><content type="html" xml:base="http://localhost:4000/mastodon"><p><a href="https://mastodon.social/@zhaocloud">mastodon.social/@zhaocloud</a></p>
<p><strong>In the future, I will post news and updates at Mastodon.</strong></p>
<p><strong>Only important articles (ex:privacy policy, TOS and new projects) will be listed at home page.</strong></p>
<hr />
<p>If mastodon.social is blocked by your ISP, school, company or government:</p>
<ol>
<li>If you’re a Mastodon user, search @[email protected] on your server.</li>
<li>Else, use a proxy, VPN or Tor</li>
<li>Or, use my proxy https://s.zhaocloud.net/morty/?mortyurl=https://mastodon.social/@zhaocloud (I don’t promise it’ll always online) (fair use PLEASE!)</li>
</ol></content><author><name></name></author><summary type="html">mastodon.social/@zhaocloud</summary></entry><entry><title type="html">Searx Updating@27 Oct.</title><link href="http://localhost:4000/update-2021-10-27" rel="alternate" type="text/html" title="Searx Updating@27 Oct." /><published>2021-10-27T00:00:00+08:00</published><updated>2021-10-27T00:00:00+08:00</updated><id>http://localhost:4000/update-2021-10-27</id><content type="html" xml:base="http://localhost:4000/update-2021-10-27"><p>Searx is updating!</p>
<p>Temporarily replaced by Azure.</p>
<p>No promise of its quality today! Sorry.</p></content><author><name></name></author><summary type="html">Searx is updating!</summary></entry><entry><title type="html">Searx Provider Changed</title><link href="http://localhost:4000/searx-provider-changed" rel="alternate" type="text/html" title="Searx Provider Changed" /><published>2021-10-20T00:00:00+08:00</published><updated>2021-10-20T00:00:00+08:00</updated><id>http://localhost:4000/searx-provider-changed</id><content type="html" xml:base="http://localhost:4000/searx-provider-changed"><p>before: Microsoft Azure</p>
<p>now: OVH</p></content><author><name></name></author><summary type="html">before: Microsoft Azure</summary></entry><entry><title type="html">Server Downtimes</title><link href="http://localhost:4000/server-down-times" rel="alternate" type="text/html" title="Server Downtimes" /><published>2021-10-20T00:00:00+08:00</published><updated>2021-10-20T00:00:00+08:00</updated><id>http://localhost:4000/server-down-times</id><content type="html" xml:base="http://localhost:4000/server-down-times"><p>My Searx server down many times. The reason is RAM isn’t enough.</p>
<p>So I bought a better VPS today.</p>
<p>Problems should be fixed.</p>
<p>Sorry</p></content><author><name></name></author><summary type="html">My Searx server down many times. The reason is RAM isn’t enough.</summary></entry><entry><title type="html">Privacy Policy and Terms of Use v2</title><link href="http://localhost:4000/privacy-policy-and-terms-of-use210917" rel="alternate" type="text/html" title="Privacy Policy and Terms of Use v2" /><published>2021-09-17T00:00:00+08:00</published><updated>2021-09-17T00:00:00+08:00</updated><id>http://localhost:4000/privacy-policy-and-terms-of-use210917</id><content type="html" xml:base="http://localhost:4000/privacy-policy-and-terms-of-use210917"><blockquote>
<p>main changes: <br />- <a href="https://zhaocloud.net/homepage-cdn">homepage provider changed</a>
<br />- <a href="https://zhaocloud.net/update-2021-09-14">logs?</a></p>
</blockquote>
<h2 id="data-i-collect">Data I collect:</h2>
<p>Home page &gt; It’s hosted on GitHub now. It depends on their privacy policy.</p>
<p>Searx &gt; no log</p>
<h2 id="data-i-share">Data I share:</h2>
<p>(in fact, I have nothing to share now)</p>
<p>I won’t sell your data forever.</p>
<p>Only in one situation, I may share the data with governments or others. You broke the terms of use heavily, and I work with them can prohibit injuries that haven’t occurred. There must be enough reason to believe their request is sincerely and necessary.</p>
<p>I’ll make these requests public. (I haven’t gotten yet)</p>
<h2 id="terms-of-use">Terms of use:</h2>
<p>Do not hurt anyone for malicious intent.</p>
<p>That’s all.</p>
<hr />
<p><strong>Please understand, ZhaoCloud values your data and tries our best to protect your privacy. But in case of attacking, spying and intimidating, I can’t make any promise!</strong></p></content><author><name></name></author><summary type="html">main changes: - homepage provider changed - logs?</summary></entry><entry><title type="html">Homepage Provider Changed</title><link href="http://localhost:4000/homepage-provider-changed" rel="alternate" type="text/html" title="Homepage Provider Changed" /><published>2021-09-16T00:00:00+08:00</published><updated>2021-09-16T00:00:00+08:00</updated><id>http://localhost:4000/homepage-provider-changed</id><content type="html" xml:base="http://localhost:4000/homepage-provider-changed"><p>My home page server is totally broken. In order to make it more stable. It’s hosted on GitHub now.</p>
<p>repo: <a href="https://github.com/ZhaoCloud-net/ZhaoCloud-net.github.io">ZhaoCloud-net/ZhaoCloud-net.github.io</a></p></content><author><name></name></author><summary type="html">My home page server is totally broken. In order to make it more stable. It’s hosted on GitHub now.</summary></entry><entry><title type="html">Searx Update @2021.9.14</title><link href="http://localhost:4000/update-2021-09-14" rel="alternate" type="text/html" title="Searx Update @2021.9.14" /><published>2021-09-14T00:00:00+08:00</published><updated>2021-09-14T00:00:00+08:00</updated><id>http://localhost:4000/update-2021-09-14</id><content type="html" xml:base="http://localhost:4000/update-2021-09-14"><p>My server’s RAM isn’t enough. I gave up using Docker. And reinstalled Searx at all.</p>
<p>For normal users. You wouldn’t realize anything. Nothing changed for you.</p>
<p>But there’s one thing I must tell you. Today, I found something that maybe against my no-log policy. Some parts of Searx, have the possibility to record log. Like Filtron, which protects my instance from bots, can record illegal requests after blocked them.</p>
<p>Especially, I’m running Searx in a new way. I’m not really sure that I’m using the best config. I need time to understand how everything working.</p>
<p>I don’t think your search and proxy logs are being recorded.</p>
<p>What I can promise to you is, this is 100%-pure Searx code. I don’t do anything bad on purpose.</p></content><author><name></name></author><summary type="html">My server’s RAM isn’t enough. I gave up using Docker. And reinstalled Searx at all.</summary></entry><entry><title type="html">DNSSEC and IPV6</title><link href="http://localhost:4000/dnssec-ipv6" rel="alternate" type="text/html" title="DNSSEC and IPV6" /><published>2021-08-13T00:00:00+08:00</published><updated>2021-08-13T00:00:00+08:00</updated><id>http://localhost:4000/dnssec-ipv6</id><content type="html" xml:base="http://localhost:4000/dnssec-ipv6"><p>Dnssec is enabled.</p>
<p>Ipv6 at Searx is disabled temporarily.</p></content><author><name></name></author><summary type="html">Dnssec is enabled.</summary></entry><entry><title type="html">Privacy Policy and Terms of Use v2</title><link href="http://localhost:4000/privacy-policy-and-terms-of-use210805" rel="alternate" type="text/html" title="Privacy Policy and Terms of Use v2" /><published>2021-08-05T00:00:00+08:00</published><updated>2021-08-05T00:00:00+08:00</updated><id>http://localhost:4000/privacy-policy-and-terms-of-use210805</id><content type="html" xml:base="http://localhost:4000/privacy-policy-and-terms-of-use210805"><blockquote>
<p>main changes: <br />- <a href="https://zhaocloud.net/homepage-cdn">Homepage with CDN</a></p>
</blockquote>
<h2 id="data-i-collect">Data I collect:</h2>
<p>Home page &gt; I don’t record logs. My CDN provider, Cloudflare, can see the traffic and log the data. It depends on their privacy policy.</p>
<p>Searx &gt; no log</p>
<h2 id="data-i-share">Data I share:</h2>
<p>(in fact, I have nothing to share now)</p>
<p>I won’t sell your data forever.</p>
<p>Only in one situation, I may share the data with governments or others. You broke the terms of use heavily, and I work with them can prohibit injuries that haven’t occurred. There must be enough reason to believe their request is sincerely and necessary.</p>
<p>I’ll make these requests public. (I haven’t gotten yet)</p>
<h2 id="terms-of-use">Terms of use:</h2>
<p>Do not hurt anyone for malicious intent.</p>
<p>That’s all.</p>
<hr />
<p><strong>Please understand, ZhaoCloud values your data and tries our best to protect your privacy. But in case of attacking, spying and intimidating, I can’t make any promise!</strong></p></content><author><name></name></author><summary type="html">main changes: - Homepage with CDN</summary></entry></feed>