Package Details: wootility-appimage 5.0.6-1

Git Clone URL: https://aur.archlinux.org/wootility-appimage.git (read-only, click to copy)
Package Base: wootility-appimage
Description: Utility for configuring Wooting keyboards
Upstream URL: https://wooting.io/wootility
Keywords: configuration keyboards wootility wooting
Licenses: unknown
Conflicts: wootility
Provides: wootility
Submitter: Freso
Maintainer: AlphaLynx
Last Packager: AlphaLynx
Votes: 15
Popularity: 1.00
First Submitted: 2018-07-14 18:07 (UTC)
Last Updated: 2025-06-28 23:57 (UTC)

Pinned Comments

AlphaLynx commented on 2025-06-29 03:27 (UTC) (edited on 2025-06-29 03:50 (UTC) by AlphaLynx)

I try my best to always follow all of the Arch package guidelines.

If you think I've missed something or have suggestions, you can:

Latest Comments

1 2 3 Next › Last »

AlphaLynx commented on 2025-06-29 03:27 (UTC) (edited on 2025-06-29 03:50 (UTC) by AlphaLynx)

I try my best to always follow all of the Arch package guidelines.

If you think I've missed something or have suggestions, you can:

AlphaLynx commented on 2025-06-29 00:06 (UTC) (edited on 2025-06-29 00:06 (UTC) by AlphaLynx)

@Quokka after this was orphaned (this request), I've adopted and updated it to the latest v5, and I'll continue to update it going forwards. I think we should now merge wootilty5-appimage into this package

shaybox commented on 2025-03-07 11:23 (UTC)

Please create and merge this to wootility4-appimage so wootility5-appimage can be merged into this package.

Quokka commented on 2025-02-20 23:24 (UTC)

Hi! v5.0.0 Stable was released yesterday. Are you planning on updating this package to v5.0.0 and upwards?

BigBrainAFK commented on 2024-07-15 12:13 (UTC)

@Freso We don't actually return a 403 Forbidden anywhere in the route handlers for that api. We also have no blocklist of Tor nodes or other such things. The best I can imagine is that DigitalOcean has some IPs blocked that may also be Tor Nodes which we can't influence.

Freso commented on 2024-07-05 15:46 (UTC)

@BigBrainAFK I’d love to switch to using your API for this! Is there a chance you’d stop 403’ing requests from Tor exit nodes (at the very least for this endpoint)?

Micha commented on 2024-06-28 04:22 (UTC)

That version query parameter seems a lot nicer to me than directly accessing the S3 bucket. At the very least it's obviously trustworthy while reading the PKGBUILD with no verification needed. Thanks @BigBrainAFK!

I'd personally vote for changing the URL in the PKGBUILD to the api.wooting.io one.

@Freso / @shaybox, thoughts?

BigBrainAFK commented on 2024-06-27 13:06 (UTC)

@Micha @Freso @shaybox

Not entirely sure who to tag here but our API does support fetching specific versions of Wootility without a raw AWS URI.

You can use the query parameter version to specify which version you want from our API. This way you don't have to use some AWS URI that people can only verify by curl-ing or downloading it themselves from us at Wooting and then checking if the AWS URIs match or not.

For example: https://api.wooting.io/public/wootility/download?os=linux&branch=lekker&version=4.6.20

Another example https://api.wooting.io/public/wootility/download?os=linux&branch=lekker&version=4.6.6

xaizone commented on 2024-06-27 08:55 (UTC) (edited on 2024-06-27 08:56 (UTC) by xaizone)

@Micha Wooting stores their AppImage inside a S3 bucket, you can verify it yourself by following the link from their website. e.g. curl -i https://api.wooting.io/public/wootility/download?os=linux&branch=lekker

1 2 3 Next › Last »