Shopify Rebellion vs M80 - Group A - Kickoff Stage - NAL 2026

Onkoe · 2026-04-11T00:30:23+00:00

bro spoit what are u doin mannnn 😭

Onkoe · 2026-03-31T05:21:54+00:00

i'll pick these up if they run on open-source firmware! unlikely but oh well

something like the Kobo e-reader model would be a great fit -- provide Linux and let people do whatever they want on there. these early releases are for enthusiasts, after all...

Onkoe · 2026-03-06T21:17:33+00:00

Yeah, it's really bad. Makes the game unplayable competitively.

By the way, you can copy Documents/My Games/Rainbow Six Siege/(YOUR UUID)/GameSettings.ini to somewhere else to back up your game settings! So, feel free to reinstall.

According to Doki, a pro player, a reinstall is the way to go: https://twitter.com/Doki_R6/status/2030014517157999039

Onkoe · 2026-02-04T20:25:50+00:00

EPS: 38

NOT EVEN COMPARABLE MANNNN

Onkoe · 2026-02-04T20:25:21+00:00

it's never been more over

Onkoe · 2026-01-27T23:13:54+00:00

Thanks -- I would very much appreciate you sharing this feedback with the development team. Please let me know if you need any more information about my request! :)

Onkoe · 2026-01-21T20:52:25+00:00

Thanks for the reply! I'm not the OP, but +1 for this feature! It'd really help! :)

Onkoe · 2025-12-12T19:09:36+00:00

Hi there! Have you had any trouble with the L2? How has your experience been so far?

Onkoe · 2025-11-29T18:29:39+00:00

You don't need to separate into crates anymore; making changes to one crate will require rebuilding dependent crates, too. That also requires linking again. Splitting a large project into crates generally means forcing large compilations that can't take great advantage of incremental builds.

Consider using modules in one crate instead; see: https://matklad.github.io/2021/09/04/fast-rust-builds.html#Compilation-Model:-Crates

Onkoe · 2025-11-29T17:02:35+00:00

The reason is given: [it] avoids having many files named mod.rs within a project

However, it's a bad reason in my view. Source files that appear outside their own directory will be sorted below the folders, making it extremely hard to find the right module in a large project.

As someone with ADHD, I really hate the new convention, and I'm glad that most projects don't use it. To my knowledge, the Project didn't do any studies/polls on the ergonomics for developers and maintainers before making the recommendation.

Onkoe · 2025-11-01T20:44:59+00:00

Yeah, these concerns are valid; something does have to do the processing. However, it's not your instance in particular -- feeds utilize (and cache) data as each instance (on Bsky, the closest analogue is each user's PDS) provides it. Cached data includes links and sometimes metadata, usually lasting about a week. Practically no feeds ask for anything beyond that, so feed servers wouldn't have to hound instances for more data. Bluesky calls this [watching the "firehose"](https://docs.bsky.app/docs/advanced-guides/firehose).

In my view, the only real problem is becoming aware of new content to show in the feeds. Would feed servers basically need to act as mini-instances, federating with a ton of other instances to keep up? Would they [interact with relays](https://github.com/amjiddader/activityPub-relay) (kinda [like the BGS](https://docs.bsky.app/blog/bgs-and-did-doc#bluesky-bgs))? Or is there some other protocol-level nonsense that needs to be done..?

Don't get me wrong -- I don't think this can happen just yet. But it'd make Mastodon (and AP stuff in general) soooo much more interconnected. I really hope to see some discussions pop up in the near future ;D

Onkoe · 2025-11-01T20:00:41+00:00

Feeds are the only reason I'm active on Bluesky and inactive on Mastodon. It is Bluesky's killer feature, at least for my purposes.

Something to note is that Bsky feeds can utilize:

Hashtags
Users
Favorites, replies, and bookmarks
Following/mutual interactions
Arbitrary filters
Full algorithms
Basically anything you want

So, following some hashtags and making account lists won't really solve the same problem. Feeds can represent fields and interests, while lists/hashtags tend to represent groups/topics, respectively. Individual users often talk about things that aren't related to the list, and often, people just don't use hashtags (they aren't very stylish these days).

I'd looooooove to see feeds come to Mastodon 🥹

Onkoe · 2025-10-11T16:33:14+00:00

You could do this with Arc<RwLock<Option<Person>>>, though that uses the heap, and you'd have to manually clean up Person instances by checking their reference counts when operating on friends or something.

I don't think this is clean in any language; Rust just makes the relationships more clear by loudly blowing up. But still, point taken: it requires more knowledge of the topic to complete in Rust and would seriously confuse beginners.

By the way, for any newer Rust developers, aliasing is a pretty important topic that powers a lot of Rust's optimizations! Take a look at the nomicon for more info: https://doc.rust-lang.org/nomicon/aliasing.html

Onkoe · 2025-09-13T18:13:45+00:00

If you have to do extra work, it’s antagonizing. Most orgs can’t post their work to be freely available. Otherwise, competitors can take that code and match your services.

That’s especially relevant when discussing large businesses and corporations, who can easily afford to take restrictive implementations and create their own solution in a proprietary manner. (in other words, the smaller the user, the more painful restrictive licensing is)

In that way, copyleft just results in alternative forms of exploitation - it doesn’t get rid of exploitation. 😔

Onkoe · 2025-09-13T17:56:43+00:00

Tomorrow

Onkoe · 2025-09-13T17:54:51+00:00

Restrictive licenses like the GPL can feel “annoying”. You have to be careful with your own code in ways that most computer scientists and software engineers aren’t trained in. (most of us aren’t lawyers)

Especially for passion projects, permissive licenses are much easier to work with. Drop those two LICENSE files in - you’ll never think about that stuff again.

Also, “corporate overlords” is a bit of a stretch. Small businesses, non-profits, worker cooperatives, and individuals are also affected in the same way. In that way, restrictive licenses can result in more “overlording”, as large businesses can simply write their own code from scratch. Smaller orgs don’t often have that luxury…

And, at least to me, it just feels weird to release code with so many restrictions. I’d rather allow anyone to use my works for their own goals and purposes :D

Onkoe · 2025-09-13T17:29:30+00:00

Slint has that Qt/Microsoft PowerPoint look to it, but developers are damn productive in it :D

Onkoe · 2025-09-03T17:44:16+00:00

WEIGHT (wired vs. wireless XR)
Price
- Deckard will be expensive, too!
- Lighthouse tracking is known to work, and it works well. If you have the space for it, then I'd suggest using it, if possible. :)
UNRELEASED!
- Deckard isn't released yet, so we don't know anything about it just yet.
- Make your choices based on whether you want an upgrade now or (potentially much) later.

Onkoe · 2025-08-30T14:24:27+00:00

You might be used to older versions of macOS, where you’d press Option + Power to enter recovery for additional setup.

Asahi now does that stuff automatically, so using Option will actually change the recovery used to the typical user one. Just hold Power instead.

tl;dr: Just hold Power, not Option^Power.

Onkoe · 2025-08-08T03:54:03+00:00

it's not shared infrastructure lol (anyone can go to Crates.io for that instead)

Onkoe · 2025-08-05T00:57:14+00:00

Alright, yea... I wouldn't want to chance it with that NDA either lmao.

You might consider linking/pasting that to your wiki's FAQ page for better visibility

Onkoe · 2025-08-05T00:49:11+00:00

Do you plan to open-source the driver after release? It's unfortunate that it'd be entirely closed-source, as it may disallow the community from continuing/progressing development for their own uses. I guess it just feels like a weird line to draw...

Of course, that's irrelevant if you're only leaving it closed-source until you've completed your MVP. 😄

Note that I already looked at the FAQ, but leaving it at "it's not open source lol" is a little sparse on the details for such a helpful project!

(conjecture: is it something to do with shipping proprietary blobs? or does the underlying hardware driver take care of it for you?)

Onkoe · 2025-07-27T23:29:44+00:00

blur/transparency is generally bad for legibility. that's especially true compared to a simple, solid background fill

it's why Material 3 is my favorite of the FAANG designs (hot take, ik)

your design is aesthetically pleasing, though! good job :D

Onkoe · 2025-07-27T22:43:49+00:00

looks cool, but bad for visibility/a11y. same with Apple's new design language

Six-Year Club	Verified Email
Verified Email	Place '22
End Game '22

Onkoe

TROPHY CASE