1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-23 21:02:09 +00:00

Compare commits

..

No commits in common. "5cd1899f9820d024b33bfaa8601899b362dbf335" and "65c6841f6ad6bf813deb08720d989e07ab597fc9" have entirely different histories.

6 changed files with 21 additions and 76 deletions

View file

@ -157,22 +157,3 @@ Content on this site also appears on <a rel="alternate" href="gemini://seirdy.on
I have a [Tor hidden Web service](http://wgq3bd2kqoybhstp77i3wrzbfnsyd27wt34psaja4grqiezqircorkyd.onion/ "{rel='alternate' class='u-syndication'}") which mirrors this site's contents, except for the fact that it replaces some SVGs with PNGs.
Meta: featured in directories
-----------------------------
This site is featured in some cool directories.
### Website minimalism
- [10 KB Club](https://10kbclub.com/)
- [no-JS Club](https://no-js.club/)
- [XHTML Club](https://xhtml.club/)
- [Hyperlinked Text](https://sjmulder.nl/en/textonly.html)
### Other directories
- [Indieweb Webring Directory](https://xn--sr8hvo.ws/directory)
- [Writer's Lane, Nightfall City](https://nightfall.city/writers-lane/)
- [Just Another Useless Page](https://www.geocities.ws/jaup/jaup.htm)
- [Webrings Fanlisting](https://fanlistings.nickifaulk.com/webrings/)

View file

@ -1,19 +0,0 @@
---
title: "Flatpak and web browsers"
date: 2022-06-12T16:24:49-07:00
replyURI: "https://floss.social/@alcinnz/108466919900074368"
replyTitle: "The outer layer will be via FlatPak"
replyType: "SocialMediaPosting"
replyAuthor: "Adrian Cochrane"
replyAuthorURI: "https://rhapsode.adrian.geek.nz/"
---
You might want to provision namespace-based isolation for your browsers. But that could throw a wrench into Flatpak-based distribution.
When distributing browsers through Flatpak, things get a bit...weird. Nesting sandboxes in Flatpak doesn't really work, since Flatpak forbids access to user namespaces.
For Chromium, they worked around this by patching Chromium zygote process (the process that provisions sandboxes) to call a Flatpak supervisor to create additional sandboxes. This is called the "spawn strategy". Chromium uses a two-layer sandbox: layer-2 is a syscall allow-list and layer-1 is everything else. The only problem is that Flatpak's layer-1 sandboxes are more permissive than Chromium's native layer-1 sandboxes, so the Chromium Flatpak has weaker sandboxing.
Firefox's sandboxing isn't entirely dependent on user namespaces, but it is weakened a bit without them; there's no "spawn strategy" implemented at the moment. More info is [on Bugzilla](https://bugzilla.mozilla.org/show_bug.cgi?id=1756236).
Now, whether this matters is something I can't decide for you. My personal opinion is that Flatpak serves as a tool to package, deliver, and sandbox native applications; Web browsers are tools that deliver and sandbox Web applications. Distributing a browser through Flatpak is like distributing Flatpak itself through Flatpak. Web browsers are an _alternative_ to Flatpak; they have their own sandboxing and updating mechanisms.

View file

@ -287,13 +287,11 @@ I'm unable to determine if these engines are independent; help would be apprecia
=> https://infinitysearch.co Infinity Search
=> https://infinitydecentralized.com/ Infinity Decentralized
## Search engines without a web interface
## Upcoming engines
Some search engines are integrated into other appliances, but dont have a web portal.
These engines arent ready yet; their indexes are either in a proof-of-concept phase with a handful of sites or arent available yet.
* Apples search engine is usable in the form of “Siri Suggested Websites”. Its index is built from the Applebot web crawler. If Apple already has working search engine, its not much of a stretch to say that theyll make a web interface for it someday.
* Amazon bought Alexa Internet (a web traffic analysis company, at the time unrelated to the Amazon Alexa virtual assistant) and discontinued its website ranking product. Amazon still runs the relevant crawlers, and also have a bot called “Amazonbot”. While Applebot powers the Siri personal assistant, Amazonbot powers the Alexa personal assistant “to answer even more questions for customers”. Crawling the web to answer questions is the basis of a search engine.
* Apple: given the activity of the AppleBot crawler lately, their index will almost certainly grow to a size large enough to power a general search engine soon. Check your servers access logs; theres a good chance its crawled your site if you have a few backlinks.
## Gemini search engines

View file

@ -14,6 +14,7 @@ evergreen: true
featured: 1
title: A look at search engines with their own indexes
---
<section role="doc-preface">
<h2 id="preface">Preface</h2>
@ -264,14 +265,12 @@ Misc
- Partially evaluated: [Infinity Search](https://infinitysearch.co): young, small index. It recently split into a paid offering with the main index and [Infinity Decentralized](https://infinitydecentralized.com/), the latter of which allows users to select from community-hosted crawlers. I managed to try it out before it became a paid offering, and it seemed decent; however, I wasn't able to run the tests listed in the "Methodology" section. Allows submitting URLs and sitemaps into a text box, no other work required.
Search engines without a web interface
--------------------------------------
Upcoming engines
----------------
Some search engines are integrated into other appliances, but don't have a web portal.
These engines aren't ready yet; their indexes are either in a proof-of-concept phase with a handful of sites, or aren't available yet.
- Apple's search engine is usable in the form of "Siri Suggested Websites". Its index is built from the Applebot web crawler. If Apple already has working search engine, it's not much of a stretch to say that they'll make a web interface for it someday.
- Amazon bought Alexa Internet (a web traffic analysis company, at the time unrelated to the Amazon Alexa virtual assistant) and discontinued its website ranking product. Amazon still runs the relevant crawlers, and also have [a bot called "Amazonbot"](developer.amazon.com/support/amazonbot). While Applebot powers the Siri personal assistant, Amazonbot powers the Alexa personal assistant <q cite="https://developer.amazon.com/support/amazonbot">to answer even more questions for customers</q>. Crawling the web to answer questions is the basis of a search engine.
- Apple: given the activity of the AppleBot crawler lately, their index will almost certainly grow to a size large enough to power a general search engine soon. Check your server's access logs; there's a good chance it's crawled your site if you have a few backlinks.
Graveyard
---------

View file

@ -12,11 +12,11 @@ This site may look simple on the surface, but I put a _lot_ of thought into it.
Accessibility statement
-----------------------
I've made every effort to make seirdy.one as accessible as possible. More information about the accessibility-related work for seirdy.one is in my post {{<mention-work>}}{{<cited-work url="https://seirdy.one/posts/2020/11/23/website-best-practices/" name="Best practices for inclusive textual websites" extraName="headline">}}{{</mention-work>}}.
I've made every effort to make seirdy.one as accessible as possible.
### Conformance status
The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. I've made sure seirdy.one is **fully conformant with WCAG 2.2 level AA.**
The [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. I've made sure seirdy.one is fully conformant with WCAG 2.2 level AA.
<dfn>Fully conformant</dfn> means that the content fully conforms to the accessibility standard without any exceptions.
@ -107,4 +107,3 @@ Privacy
-------
This site is **privacy-respecting.** Its CSP blocks all scripts, third-party content, and other problematic features. I describe how I go out of my way to reduce the information you can transmit on this site in [my privacy policy](../privacy/).

View file

@ -56,40 +56,27 @@ while getopts "hd" flags; do
esac
done
trim_trailing_comma() {
sd ',$' ''
# values for the GEORGE webring
george() {
echo GEORGE
curl -s 'https://george.gh0.pw/embed.cgi?seirdy' | htmlq -a href 'main p a'
}
values_to_csv() {
tr '\n' ',' | trim_trailing_comma && echo
}
# values for the GEORGE webring
george() {
printf 'GEORGE,'
curl -sSL --compressed 'https://george.gh0.pw/embed.cgi?seirdy' \
| htmlq -a href 'main p a' \
| values_to_csv
}
endless_orbit() {
printf 'Endless Orbit,'
curl -sSL --compressed https://linkyblog.neocities.org/onionring/onionring-variables.js \
| grep -C 1 https://seirdy.one/ \
| sd https://seirdy.one/ https://linkyblog.neocities.org/webring.html \
| sd "\n|'" '' | trim_trailing_comma
echo
tr '\n' ',' && echo
}
print_csv_values() {
george
endless_orbit
printf %s "$(george)" | values_to_csv
}
if [ -f "$webrings_dest" ]; then
echo "webrings file already generated"
exit 0
fi
if [ "$dry_run" = '1' ]; then
print_csv_values
elif [ -f "$webrings_dest" ]; then
echo "webrings file already generated"
else
print_csv_values | cat "$webrings_src" - >"$webrings_dest"
fi