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. "7d31595d31a5cea30b83c6da9d731aa5750d1c4e" and "6a58b5a747b6df5c8f1274dcacff742abc243528" have entirely different histories.

3 changed files with 0 additions and 8 deletions

View file

@ -48,11 +48,8 @@ These are roughly in descending order of importance:
### June 2024 ### June 2024
- Added support for [No-Vary-Search](https://wicg.github.io/nav-speculation/no-vary-search.html) - Added support for [No-Vary-Search](https://wicg.github.io/nav-speculation/no-vary-search.html)
- Added humans.txt. - Added humans.txt.
- Added my badge to the site footer. This also helps make it easier for projects like [EightyEightThirty.One](https://eightyeightthirty.one/) to scrape.
### May 2024 ### May 2024
- Wrapped `details` elements in borders to distinguish them in print media and to emphasize that the contents can be toggled. - Wrapped `details` elements in borders to distinguish them in print media and to emphasize that the contents can be toggled.

View file

@ -6,9 +6,6 @@ replyTitle: "The outer layer will be via FlatPak"
replyType: "SocialMediaPosting" replyType: "SocialMediaPosting"
replyAuthor: "Adrian Cochrane" replyAuthor: "Adrian Cochrane"
replyAuthorURI: "https://adrian.geek.nz/" replyAuthorURI: "https://adrian.geek.nz/"
syndicatedCopies:
- title: 'The Fediverse'
url: 'https://pleroma.envs.net/objects/9a1fcc96-1fef-4521-83a5-0b267f144c11'
--- ---
You might want to provision namespace-based isolation for your browsers. But that could throw a wrench into Flatpak-based distribution. You might want to provision namespace-based isolation for your browsers. But that could throw a wrench into Flatpak-based distribution.
@ -20,4 +17,3 @@ Firefox's sandboxing isn't entirely dependent on user namespaces, but it is weak
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. 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.
<ins datetime="2024-06-18" cite="https://forum.vivaldi.net/topic/33411/flatpak-support/192?lang=en-US">Update <time>2024-06-18</time>: [This is also the reason why the Vivaldi team won't publish a (verified) Flatpak of Vivaldi](https://forum.vivaldi.net/topic/33411/flatpak-support/192?lang=en-US).</ins>

View file

@ -4,7 +4,6 @@
"buttons": [ "buttons": [
{ {
"id": "seirdy.one", "id": "seirdy.one",
"animations": "none",
"alt": "Square icon of a colon and semicolon, next to the word “Seirdy”.", "alt": "Square icon of a colon and semicolon, next to the word “Seirdy”.",
"link": "https://seirdy.one/", "link": "https://seirdy.one/",
"sha256": "042c185929296eada5f38ea5dd9e8c1b51e9e4bdee6283bb92697dc4d7516100", "sha256": "042c185929296eada5f38ea5dd9e8c1b51e9e4bdee6283bb92697dc4d7516100",