Daeraxa

And I wasn’t aware of the Elementary thing with Flatpak! Admittedly I hadn’t really thought of it in that way, I was thinking something more akin to F-droid where there are a couple of extra repos you can add which have applications not on the main one due to slightly looser requirements. But making it specifically for apps for that ecosystem in particular makes a lot of sense.

Not officially but people have managed to reverse engineer it before in order to host their own - https://forum.snapcraft.io/t/lol-an-open-source-snap-server-implementation/27109

Whilst I do get the sentiment (and in no way do I support Canonical in keeping it proprietary), how likely is it that alternative Snap repos are going to show up if they did make it possible? Even with Flatpak where it is encouraged and documented I don’t think I’ve heard of anyone setting up a Flathub alternative of any significance.

(except snap, but they seem too Ubuntu specific).

For what it is worth you can install Snap on most distros. https://snapcraft.io/docs/installing-snapd

From the conversation it seems to be a similar situation to the project I’m with is in. The flatpak is essentially community maintained rather than being directly supported by the team. To become verified it needs to be done so by a representative of the maintainers of the software. To be verified it doesn’t have to have a team member involved in it but this is a requirement Inkscape seem to have imposed.

For us we just aren’t in a position to want to support it officially just yet, we have some major upgrades coming to our underlying tech stack that will introduce a whole bunch of stuff that will allow various XDG portals etc. to work properly with the Flatpak sandboxing model. To support it now would involve tons of workarounds which would need to be removed later.

Yeah this has been our (well, my) statement on requests to put out ARM binaries for Pulsar. Typically we only put binaries out for systems we actually have within the team so we can test on real hardware and replicate issues. I would be hesitant to put out Windows ARM builds when, as far as I know, we don’t have such a device. If there was a sudden clamouring for it then we could maybe purchase a device out of the funds pot.

The reason I was asking more about if it was to do with developer licences is that we have already dealt with differences between x86 and ARM macOS builds because the former seems to happily run unsigned apps after a few clicks, where the latter makes you run commands in the terminal - not a great user experience.

That is why I was wondering if the ARM builds for Windows required signing else they would just refuse to install on consumer ARM systems at all. The reason we don’t sign at the moment is just because of the exorbitant cost of the certificates - something we would have to re-evaluate if signing became a requirement.

I can’t say I’m one who shares that sentiment seeing as the only two projects I’m involved with happen to be Electron based (by chance rather than intention). Hell, one of them is Pulsar which is a continuation of Atom which literally invented Electron.

Is that a developer licence thing? I know GitHub recently announced Windows Arm runners that would be available to non-teams/enterprise tiers later this year.

Electron apps using older versions that don’t support the 16k page size are probably the biggest offenders

Are there any stats to suggest that? I don’t mean in a “prove it or gtfo” kind of way but I maintain a community for the Pulsar text editor on lemmy.ml (back before it was cool /hipster) when there weren’t really any other (popular) instances. We have no political ideology (as a group, not speaking for individuals within it) and it is meant to be a Fediverse alternative to our Subreddit for discussion and support. The last thing I want is for people to not have access to it because instances are blocking it or people are shying away from lemmy.ml in general.

I wonder if it probably wouldn’t (or at least wouldn’t have) done any harm to do so seeing as if you look at Flatpak, its most obvious comparison, although it can have multiple remotes, Flathub is the only one that is realistically used and is the de-facto standard.

I think a lot of the flak directed towards snap would be mitigated if they made the backend open source. I know there are some efforts to produce alternative backends (although the one I knew about lol / lol-server seems to have gone dark).

Another issue is Canonical’s rather strong armed and forceful approach to making people use snaps rather than the OSs native packaging system, again, not something that should be an issue in theory but when people already have a negative view of the format to start with…

Personally I don’t really have an issue with Snaps. I’ve had more luck with them and fewer issues than Flatpaks (which I also tend to avoid like the plague) but that is probably just because I prefer to use appimages or native packages rather than having to fight the sandbox permissions and weird things it can do to apps that don’t take Snaps and Flatpaks properly into account.

Its the leaves that have a lot of oxalic acid, the stems are edible raw, just utterly unpalateable. Although if you have a miracle berry first it is apparently delicious - https://youtu.be/hgvRoCY0hNA?t=10m26s

Halloy

I’m using Fedora on a second hand x380 Yoga and it works rather nicely.

It is only really in the states where ‘liberal’ means left wing. Nearly everywhere else liberalism is centre or centre-left.

Magazines are Kbin’s name for communities

The moment I see the same question popping up more than a couple of times is an indication that it should be documented by somewhere that is actually indexed by search engines, normally the website/faq/docs/wiki as it is clear there is something missing.

To me, as part of a small team/project, it feels so much better to be able to use chat for every day communication just as I would at work. It allows a lot more expression in communication than forum posting. It has really helped us have a good sense of community and teamwork we might have not otherwise had.

I don’t think much in this is specific to Discord so much as it is to chat/IM in general. Honestly we use both chat (yes via Discord although I’d love to move to Matrix) and forums. They just serve completely different roles. Traditional style forums (whatever it is, Discourse, Flarum, Github Discussions) work really well for “long form” topics and asynchronous conversations. i.e. if there is something to discuss that is complex and can attract valid conversation over the course of days/weeks/months then it is ideal.

Chat on the other hand is great for co-ordinating and asking quick one-off questions that will get you an answer really quickly. We use it all the time to just discuss general plans, ideas etc. and answer simple questions like “how do I do x?”.

I think most of the (justified) hatred is to those projects that only have a community via chat which is valid - on big projects it can be somewhat difficult to get a word in and get noticed if you have a “simple” question which wouldn’t be a problem on a forum.

I understand the mentality but depending on the project it can be a struggle. If I was going to set up a brand new software project then sure, I’d be going all in on Fediverse and open source platforms. Forge? Codeberg. Chat? Matrix. Forum? Discourse/Flarum or maybe just Lemmy. Microblog? Mastodon.

However it isn’t easy to be that idealistic all the time and sometimes there is a degree of needing to do stuff against your ideals. I’m part of the Pulsar editor team which is a fork of the Atom text editor that got discontinued and we had to get things moving as quickly as possible in the time period that GitHub set until they pulled their services completely (along with their package backend). We needed the least friction possible to get things in motion and get as many people from the community involved as possible.

We needed GitHub - unsurprisingly Atom had close ties with GitHub anyway so moving away wasn’t ever going to be quite that simple and we would have needed to migrate an awful lot of repos within the org. The entire Atom package system relies on GitHub - people published their packages to atom.io but the actual code was on GitHub - something not fixable in the short period we had. We also needed it because this is where the Atom community was gathered around - at a period where we needed things to be as simple as possible for people to find out about and get involved with the project, moving to another forge may have just been the end of it.

We also use GitHub Discussions for our forum - as we are already tied to GitHub for the time being we might as well use that platform as well - it is a lot easier than trying to maintain our own forums which wouldn’t be seeing that much activity. The team behind Zed found this out; they set up a Discourse forum and barely anyone used it so they just went back to GitHub Discussions.

We needed Discord because it was simply the most commonly used platform. Pulsar split off from Atom-community which was already on Discord so it was a natural move that meant little disruption or friction to anyone wanting to get involved with the new project. We have been looking to make a Matrix bridge but honestly there doesn’t seem to be all that much desire for it - we had some initial enthusiasm to create a Lemmy community but when we did it barely sees any activity (other than me posting updates there).

Would I love to move off of these platforms? Absolutely. However we simply have bigger fish to fry at this point in time for the project itself so it is going to be slow.

So whilst I love to be idealistic about what platforms we should be using I also heavily sympathise with those who use those “less than ideal” ones - there could well be some very good reasons behind it that might not be obvious to you.

Pulsar (i.e. active fork of Atom) has a pretty comprehensive snippets package that comes bundled with the editor. Can be configured with some fairly simple cson, for example with Markdown:

'.source.gfm':
  'Hello Lemmy':
    'prefix': 'helem'
    'body': 'Hello Lemmy!'

You type helem then press tab and it will expand to Hello Lemmy! when using the Markdown grammar (source.gfm).
It can handle custom tab stops too so you can make a longer preformatted sentence with gaps to insert words which you can just tab through (the $1, $2, $3).

'.source.gfm':
  'My custom snippet':
    'prefix': 'mcs'
    'body': 'My snippet stops here $1 and then here $2 and then continues $3'

You can even do multi-line snippets. For anyone wanting to try it out the docs are here