<feed xmlns='http://www.w3.org/2005/Atom'>
<title>xavi/slcl/page.c, branch v0.2.1</title>
<subtitle>Small and lightweight cloud storage written in C99 and POSIX.1-2008.
</subtitle>
<id>https://gitea.privatedns.org/xavi/slcl/atom?h=v0.2.1</id>
<link rel='self' href='https://gitea.privatedns.org/xavi/slcl/atom?h=v0.2.1'/>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/'/>
<updated>2024-02-19T22:35:09+00:00</updated>
<entry>
<title>page.c: Use open(2) fdopen(3) and fstat(2)</title>
<updated>2024-02-19T22:35:09+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-19T22:20:25+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=6c3bfa270b1de6cdea0da8e351f92ec65e90c4f0'/>
<id>urn:sha1:6c3bfa270b1de6cdea0da8e351f92ec65e90c4f0</id>
<content type='text'>
Now, the same file descriptor can be reused for all of the operations
above, instead of calling stat(2) and fopen(3) separately.
</content>
</entry>
<entry>
<title>page.c: URL-encode href</title>
<updated>2024-02-19T22:35:09+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-19T22:09:58+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=78c8c4dabb62a6669cfd4eca231e39fd7fd4567a'/>
<id>urn:sha1:78c8c4dabb62a6669cfd4eca231e39fd7fd4567a</id>
<content type='text'>
Otherwise, files with special characters, such as '%', could not be
downloaded or previewed.
</content>
</entry>
<entry>
<title>Implement HEAD support</title>
<updated>2023-10-13T23:08:02+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-10-02T22:09:37+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=472b4ddbf151b44f5fc01c4c1752ce5529a0cf85'/>
<id>urn:sha1:472b4ddbf151b44f5fc01c4c1752ce5529a0cf85</id>
<content type='text'>
</content>
</entry>
<entry>
<title>List number of files and directories</title>
<updated>2023-10-10T22:08:44+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-10-10T21:53:42+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=1d2ce3f9c235f0b6524bbedad0b2ff0abb838888'/>
<id>urn:sha1:1d2ce3f9c235f0b6524bbedad0b2ff0abb838888</id>
<content type='text'>
Sometimes, users want to know how many files and/or directories reside
on a directory. Now, slcl prints such information below the logout form.
</content>
</entry>
<entry>
<title>page.c: Force whitespace rendering</title>
<updated>2023-10-10T22:08:44+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-10-10T21:53:05+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=91f1a38d5cf33e9a5c9fcc81a9e55984d576f1c8'/>
<id>urn:sha1:91f1a38d5cf33e9a5c9fcc81a9e55984d576f1c8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Apply slweb renaming to libweb</title>
<updated>2023-10-10T22:08:40+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-10-10T21:43:47+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=28ae865e5ecad9b398ac21fa148fc4b93c987226'/>
<id>urn:sha1:28ae865e5ecad9b398ac21fa148fc4b93c987226</id>
<content type='text'>
</content>
</entry>
<entry>
<title>page.c: Update project URL</title>
<updated>2023-09-08T22:19:07+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-09-08T22:19:07+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=7471da3886355199185a3b05a45b4c9b845d5a89'/>
<id>urn:sha1:7471da3886355199185a3b05a45b4c9b845d5a89</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do some minor rebranding</title>
<updated>2023-08-01T00:25:30+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-08-01T00:13:52+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=75f1f223d45d00629ed0866bf8bed726b60d8215'/>
<id>urn:sha1:75f1f223d45d00629ed0866bf8bed726b60d8215</id>
<content type='text'>
Despite designed around portability and minimalism, I feel slcl no
longer aligns with the philosophical views from the suckless project.
Therefore, I think it was appropriate to unlink its branding from it.
</content>
</entry>
<entry>
<title>Adapt to slweb's include paths</title>
<updated>2023-07-20T23:40:55+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-07-20T23:24:10+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=e49f1da7aed6894c8893cf29c33c4ca839d74976'/>
<id>urn:sha1:e49f1da7aed6894c8893cf29c33c4ca839d74976</id>
<content type='text'>
slweb puts its header files into its own directory in order to avoid
potential name clashing.
</content>
</entry>
<entry>
<title>Limit amount of search results</title>
<updated>2023-07-11T11:27:49+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-07-11T11:11:50+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/slcl/commit/?id=38f3f82a77ed4782a9c4e1b4e5a6d9d4c71390a2'/>
<id>urn:sha1:38f3f82a77ed4782a9c4e1b4e5a6d9d4c71390a2</id>
<content type='text'>
When a user enters a search term that is too generic, slcl would
generate a long list of search results, where this generation could have
a big impact on the server performance and its available resources.

Therefore, it is reasonable to limit the number of search results to an
arbitrary limit, so that users are forced to enter a more specific
search term in order to achieve more relevant results.
</content>
</entry>
</feed>
