Notices by Ted Gould (ted@social.gould.cx), page 19

Thinking about making a "sexy home office worker" costume for Halloween.

It'll be a t-shirt, flannel pants and coffee mug that say "I'm Sexy" on them.

We now have a website at Axiom!

https://axiom.co/

I can spend less time trying to explain what we do and more time giving people a URL. Now, just to finish all those features...

@oletedstilts I will become a Scrabble champion!

@mathieu @federicomena the link on Flathub says it is "Flathub maintainers"

https://flathub.org/apps/details/org.gimp.GIMP

And then points this repository:

https://github.com/flathub/org.gimp.GIMP/

Which contains distro patches among other config. It doesn't seem to be in the main GIMP repos, which don't have any flatpak info in them.

https://gitlab.gnome.org/GNOME/gimp/

@paperdigits people trust different sources. But having defined interfaces that are restricted and the applications are designed for is the key.

The problem is that you can't just generically sandbox an app that wasn't configured for it, otherwise we could just sandbox debs, the apps need to be aware of the restrictions they have and show them correctly to the user.

@federicomena would be an interesting conference talk.

I'm not sure how many of the older formats that I'm willing to publicly admit using 😉

@paperdigits @federicomena AppImage doesn't provide any sandboxing last I checked, so it is kinda scary. I wouldn't recommend it.

But that's basically what Ubuntu is becoming. The base system is all debs but the software install tool shows and prefers to install snaps.

I'm only using Debs for a couple of apps now.

@n8 Raph Levien?

@ng0 @federicomena I would say that's not a big deal and an upgrade. A large number of Debian packages have switched to being linked to the upstream VCS and are maintained that way. It makes maintaining any patches much easier.

For the packages that aren't managed that way Launchpad attempts to build up Git branches for all them as well. Super handy for diagnosing problems and bisecting issues.

@csoriano @n8 @federicomena they could be "build times" if that was the reason to use them. Then you wouldn't have to worry about ABI stability, only API stability, of the package of libraries.

@n8 @federicomena I'd argue that the runtimes are generally a bad idea. They're about optimizing disk space, which in most cases, no user is actually worried about in the scale that they save space.

But, what I've also learned is that *developers* are really worried about that disk space and "duplication." Especially OSS devs. I'm generally confused at why.

@brion @federicomena I think that your comment gets to the core there at the end, it really is about trust. Needing to trust another group, or trust between groups, makes things more difficult. And the lack of trust is what has always driven application developers and distros apart.

@federicomena yes, but it's also a social thing. Both "flathub maintainers" and "snapcrafters" are basically distro teams with another name and really should be discouraged. Better to patch projects and their CI than to encourage out-of-tree packaging.

I think this is where Flathub has run amok, I haven't been able to find any packages there that were maintained by the upstream projects.

@federicomena while I think that it is a great idea to give application writers a direct path to users, I think that's an ideal that the next gen packaging formats are having trouble realizing.

Unless the applications are maintaining the packaging as part of their normal release and development process, you're effectively introducing a new set of distro packagers in the middle.

@bgcarlisle it could be, but really it was more that it was thrown together by people who didn't care about the UX, just the underlying data structures.

Became defacto because it was used by celebrities. And then everyone.

There were/are better DVCSes, but nothing has been able to get that level of endorsement.

@n8 clearly you should just read all text in monospaced fonts. I bet that'd help.

@kensanata had not heard of it, but interesting.

The business model of bundling social networking and online storage and chat may not be crazy. People are used to paying for disk space. Wonder if it could ever create enough revenue.

It has all the closed source and merky security story problems, but the business model is kinda interesting.

@sil I think that the multi-accounts will come from multiple tools that solve different problems. For instance, your blogging software could appear as an account, Gitlab, your social network, news feed reader, etc.

The result is that you'll be pushing and consuming the messages in different ways, even if they're all AP based.

@sil I believe that Tootdon can do it, but I've not used it: https://itunes.apple.com/us/app/tootdon-for-mastodon/id1282283934

I'm using Tusky which can not though. Seems like a cool feature.