Request for snap name "ares" - registered but unused

store-requests transfer-ownership
1

Hello,

I would like to request the transfer of the snap name ares to my account (syl21).

Current situation:

  • The name ares is registered but has no revisions published and no snap available in the store
  • I have already published a working snap under the name ares-emu on the stable channel (version 147, amd64 + arm64)
  • I initiated a name dispute via the Snapcraft dashboard about a week ago but have not received any response

Why this name:

  • ares is a well-known open-source multi-system emulator focusing on accuracy and preservation
  • The name ares directly matches the upstream project name
  • My snap packages the official upstream releases of ares

My published snap:

Thank you for your help.

2

Is Snap Project DEAD ???

3

Why do you specifically want the name ares?

4

Because I package Ares

5

You don’t specifically need the name ares to make the ares emulator available to users.

1 Like
6

I don’t understand. A guy as lock ares name and do nothing with and the problem is that I request ares name to publish ares packages ?

7

If you really wanted to make Ares available on the Snap Store, you would have already done so.

The name ‘ares’ isn’t necessary for this to be possible.

1 Like
8

I understand that the name isn’t strictly required, but my request follows Snapcraft’s naming guidelines:

  • The name ares is registered but has never been used (no published revisions)

  • I’m packaging the official upstream project (https://github.com/ares-emulator/ares)

  • Users expect ares to be the ares emulator

Could a @store-team member please review this transfer request?

Thanks!

9

Speaking of things users expect


I tried testing your Snap app, ares-emu, and it doesn’t even open. It gives an error that in English must be: Illegal instruction (core dumped).

And besides that, your Snap doesn’t have a defined .desktop file, so users would need to create their own or run it via the terminal.

It doesn’t seem like you test what you publish.

1 Like
11

@Kyuyrii

Let me clarify a few things:

  1. The snap you tested is an old version that was depublished precisely because it was buggy. It was temporarily made public again during a rebuild cycle. The new build with proper configuration is currently in progress.
  2. The “Illegal instruction” crash and the desktop file issue are already known and fixed in the current pipeline. You tested a version that was never meant to stay published.
  3. Flagging my request as spam is completely unjustified. I’m an active developer working on packaging ares for the Snap Store with a fully automated CI/CD pipeline building for amd64 and arm64. The project is public and verifiable:
  4. The uploads to the ares name happened because I was waiting for the name transfer to go through. Since you seem impatient, I’m currently building under ares-emul so you can test a working version right now.
  5. You are not a moderator or an admin. The name transfer request is addressed to the Snap Store team, not to you. If you have nothing constructive to add, please don’t block the process by flagging legitimate requests as spam.

I’m simply asking for a name that has been registered and never used, to publish a real package for a real project. That’s exactly what the name dispute process is for.

12

I didn’t mark your post as spam.

It makes no sense for you to use another name just to publish a new version; you should just publish a new revision on ares-emu.

It’s a bit excessive to request access to a snap without even having a minimally functional version.

Requesting a Snap name without even having a functional Snap example is a clear demonstration of how anxious and unprofessional you are.

1 Like
14

Hello @syl21 and @Kyuyrii ,

Please keep the discussion civil.

This topic was automatically unlisted due to repeated links to the ares project occurring in multiple topics. The automated checks are intended to prevent spam, but those links were for legitimate interface requests, and this is a legitimate post about a name transfer request, so I have restored the post.

For some context, it seems you are both trying to publish snaps of the ares project, and that may be leading to feelings of competition:

ares-emu                     147                               sylvain-gargasson-b         -        Multi-system emulator focusing on accuracy and preservation
ares-emulator                147                               kyuyrii                     -        Multi-system console emulation suite

I am not a member of the store team, so I have no authority on this matter. However, my general advice would be that you should do what is best for the upstream project. Ideally, snap packaging would be merged into the upstream codebase and published officially by the upstream. Otherwise, it is generally best (or at least courteous) to indicate that your 3rd party snaps of the project are unofficial and not endorsed or supported by the upstream project.

Furthermore, it’s not clear to me that the name ares should be claimed solely by the ares-emulator project. The current registrant of the ares snap name has some say in the matter, though it is ultimately up to the store team.

In my opinion, ares-emulator and ares-emu are perfectly good names for 3rd party snaps of the ares-emulator/ares project. See, for example, snap search minecraft, where there are many 3rd party snaps of various launchers, mod managers, and servers related to Minecraft. As Microsoft does not publish an official snap of Minecraft, there is no snap called minecraft. And that is okay.

Again, I am not on the store team, I have no say in this request. I would just ask you to act respectfully, assume good intentions, and do your best to work help each other, in the interest of making the best snap package of the upstream project.

Thank you,

Oliver

4 Likes
15

I simply found it absurd that it would immediately ask for the name of a Snap that already has an owner, without needing the name of that particular Snap, and then, not getting a response, send: “Is Snap Project DEAD???”

I care as much about Snapd as I do about the user experience. It’s been 12 days since the last update of ares-emu. I’m mentioning this because ares-emu doesn’t even open; I tested it, and the error in English was something like “Illegal instruction (core dumped)”.

The situation worsens because ares-emu is public; any user can easily find and download a Snap that doesn’t even work. There isn’t even a warning that it’s unstable, in testing, or unofficial.

Furthermore, the link added in “Report a bug” leads to the issues in the Ares repository, and the “Contact” link leads to the Ares Discord server, implying that the Ares developers are responsible for handling problems with the Snap version.

1 Like
16

Thanks for your concern Kyuyrii, truly touching.

A few factual clarifications:

My snap ares-emu works perfectly fine, I just retested it. It also includes shaders and all required dependencies, unlike yours. The links to the upstream project are intentional: the ares developers gave me their blessing to manage this package, and my GitHub workflow automatically publishes every new release.

Quick timeline reminder: my transfer request was posted on February 6th. Your snap ares-emulator miraculously appeared
 on February 8th. Impressive reaction time — if only the Store team could match that.

Because the real issue remains: the name “ares” has been squatted for years by someone who never published anything, my name transfer request has been waiting for almost 3 weeks, my joystick auto-connect request too, and absolutely no admin has responded to any of it. The only person who replies quickly on this forum is you — to criticize other people’s work.

At this point, I’m seriously starting to wonder if the Snap Store is still actively maintained at all. No moderation, no decisions, no admin presence — just users left talking to themselves. If this is what community support looks like, it speaks volumes about the state of the project.

17

The problem is not that snaps are so unloved, it is quite the opposite, they are such a big commercial success that the store team is overly busy handling requests from enterprise customers and while ramping up the staffing is in progress since a while it doesn’t go as fast as it should which in the end causes delays, please try to be patient, the shortcomings are known and being fixed, some things simply take time :slight_smile:

3 Likes
18

The ares-emu available on the stable channel, which is the only channel currently in use, continues to give an error when trying to open, revision 11.

It’s no use saying your version has the shaders if it doesn’t open.

From what I saw, the reviewers responded to your requests for automatic connection, or did the translator I’m using distort what you meant?

Is this the discussion you opened about a Snap version?

From what I saw, it said:

It is clear to me you care a lot about providing a build of the Ares emulator on Snap; if the process is so simple and automated, why not just keep providing this service yourself as an unofficial release, ensuring that it works correctly on Ubuntu along the way? This would be a great contribution to the emulator's ecosystem.

What I found that is publicly available is this, about making the version unofficial.

1 Like
19

Well, that settles it.

On one hand, we have a Store team apparently too busy with “enterprise customers” to process a simple name transfer or auto-connect request in over 3 weeks. Fair enough, I can understand being understaffed.

On the other hand, we have Kyuyrii claiming my snap doesn’t work
 without ever opening a single bug report. Not on my GitHub, not anywhere. Just a comment thrown on a forum. That’s your contribution? Instead of being constructive, reporting an actual issue with logs, a config, anything useful, you’d rather spend your time digging through my GitHub issues and the upstream project to check whether I’m “legitimate” enough to maintain this package. How is that any of your business exactly?

The ares developers gave me their approval. My snap works, includes shaders and all required dependencies, and automatically updates with every new release. Meanwhile, you published a half-baked snap 2 days after my transfer request and now you’re lecturing me.

I’m done. Between a ghost admin team, a squatted name that will apparently stay squatted forever, and a freeloader with nothing better to do than play inspector on other people’s work, I have better things to do with my time.

I’m pulling my snap from the Store. Congratulations, you’ve successfully discouraged yet another contributor. The Snap ecosystem is in great hands.

20

Why did you mention your Github? The link you provided indicates that you want users to report any problems they are having with your Snap version to the Ares developers.

Captura de tela de 2026-03-02 13-56-27
Captura de tela de 2026-03-02 13-56-27347×155 15.5 KB

https://youtu.be/hqgj2IVF7_I?si=cNkAhwOszyMQ8r-J

No one here is to blame for you wanting to give up.

Nothing ever prevented you from publishing a working version of Ares on the Snap Store.

1 Like