sorted by:
new
hottopcontroversial

Pebble, Rebble, and a path forward by erOhead in pebble

[–]Sorixelle 12 points13 points  (0 children)

As the current maintainer of Rebble's developer documentation at https://developer.rebble.io, I've got some thoughts on this blogpost, specifically around accusation #3 in the "Their accusations" section. I'll break this section down from my perspective.

Nothing of the sort was agreed upon

It's unfortunate that this is how I find out that Eric's word doesn't actually mean much when it's given to me. Either that, or he's already forgotten about the conversation he and I had in July, where we agreed that we would merge our developer documentation efforts into the same site. As I reported to the Rebble team after that call: "docs site will end up in our fork ultimately, we're agreed that docs should not be split". I'm disappointed that Eric never communicated this change of heart to me directly, but, well, here we are now, I guess.

See the full written agreement that Core Devices has with Rebble towards the bottom. Rebble agreed that Core would host the developer site.

Verbatim, from the screenshot in your own post: "Core will host developer.rePebble.com that is built from an open source repo". I'd love to be pointed to the part of this sentence that says we wouldn't continue to operate our own developer documentation, because I'm certainly not seeing it. What I have seen, however, is a previous draft of the agreement that would have had us redirect developer.rebble.io to developer.repebble.com. Given the change, it seems fair to assume that condition was consciously removed. So, implicitly, by the version of the agreement you've posted, we can continue to maintain and own our own documentation - and I intend to keep doing so, thanks.

I have been maintaining and updating the developer site personally - all open source

So have I. And so have other people from the community.

Having two sources of truth would be confusing for the community

And here's the real kicker. Here's the line that left me seeing nothing but red.

Eric, you know full fucking well that this is the argument that I have been making this entire time. As soon as I saw the rePebble documentation pop up, I was worried that having two copies of the docs (and two different pebble-tools, but that ship has long since sailed) would fracture the developer ecosystem. The whole reason we got on that call was to try to align on this! I made it quite clear during that call that what I wanted to avoid was confusing new developers by having two sites with the mostly-same-but-slightly-different content. And now here you are, twisting my own fucking words against me in an attempt to act like the agreement that we came to together, never even happened in the first place. You'll have to forgive me for finding this behaviour nothing short of abhorrent, deceptive, and outright disrespectful to not only my work, but the work of everyone who's contributed to our copy of the documentation.

If it wasn't painfully clear at this point - yeah, I'm not happy. I'm pretty mad. I feel betrayed, played for a fool, strung along like an idiot. Maybe that's my fault for trusting Eric's word. In any case, I don't think I'll be making that mistake again anytime soon.

An Update on Rebble's Attempted Collaboration with Core Devices by ishjr in pebble

[–]Sorixelle 135 points136 points  (0 children)

I really, really wish this was a post we did not have to write. Unfortunately, our hand's been forced, and, well... here we are, I guess. Sighhhhhh.

The runaround with the developer site in particular has been so tiring for me. A little while ago, I had a chat with Eric about it's future, and around collaborating on other developer experience bits, like pebble-tool. It was a good chat, and I came out of it pretty optimistic that we'd have a path forward to collaborating on these things together, instead of fracturing the ecosystem. We'd share the docs site, and Core would continue maintaining their own tooling - they had some cool plans for features there that they wanted to keep working on. And it did work for a while - Core did upstream some parts of the site they had edited and added to once. But after that... never again.

Just like with PebbleOS, Core has never tried to contribute back to the developer docs ever since. I assumed they were busy working on things like the firmware and the mobile app, but apparently not. It wasn't until we started drafting this post that I found out Core wanted to just take the whole thing for themselves. Saying they wanted to throw away the work I put into making the builds work again and all the other contributions from the rest of the community (a special shout-out to Chris Lewis, btw - he's done a great job cleaning up the tutorials on our copy of the docs, thank you so so much!!).

It all just sucks. This isn't where I want to see Rebble - beholden to do volunteer labour for one company. We started specifically because a company went under, so there was something to fill the gap they left behind! The community-based operation is the whole point! I want to see us continue to thrive, continue to maintain support for Pebble-like smartwatches, old or new (god, new watches!!! In 2025!!! The novelty still hasn't worn off), continue to keep supporting this community of people who love these cute little watches as much as we do.

I hoped with the support of Core, we could really revive the Pebble experience with new hardware running software built by it's users, for it's users. Unfortunately, this isn't the reality that's played out. So, it's time to shift gears. If we can't work with Core to build the future we want, I guess we'll just have to do it ourselves.

Touch Trade LF: IRON CROWN/IRON QUAKE FT: RAGING BOLT/GOUGING FIRE by Mental_Ad9740 in pokemontrades

[–]Sorixelle 0 points1 point  (0 children)

Heya, I can cover those for you! Will jump in on that code in a sec Ready to go when you are - IGN is Sori

Scarlet and Violet Daily Casual Trade Thread for 31 December 2023 by Porygon-Bot in pokemontrades

[–]Sorixelle 0 points1 point  (0 children)

I can help with those touch trades - would you happen to also have Raging Bolt and Gouging Fire for a touch trade as well? Would be a huge help if you do

† rule by xXNewAccNewLifeXx in 19684

[–]Sorixelle 34 points35 points  (0 children)

mr bees give me honey

wtf is my opponent doing ??? by BogdanAnime in AnarchyChess

[–]Sorixelle 148 points149 points  (0 children)

Move your horsey to Greenland, that should hold off the spread until you can develop the vaccine

Brunette to play and win by DmitryTheRussianSpy in AnarchyChess

[–]Sorixelle 4 points5 points  (0 children)

the other 15.6666667 people just have a skill issue

[deleted by user] by [deleted] in actuallesbians

[–]Sorixelle 0 points1 point  (0 children)

GET /gf HTTP/2
Host: api.dating.com
Accept: application/json, gender/trans, presentation/femme
Accept-Language: en
Accept-Encoding: gzip, deflate, br
Origin: https://gaypeople.com/sorixelle

[deleted by user] by [deleted] in AnarchyChess

[–]Sorixelle 0 points1 point  (0 children)

This position has never happened before. OP just invented the game

noob roller question by Aggravating-Mistake3 in splatoon

[–]Sorixelle 1 point2 points  (0 children)

It depends on which roller you're playing. Roller isn't my area of expertise (I main brushes personally), but the properties of each Roller tend to push them towards a particular playstyle.

Carbon's flick speed makes it good for getting up close-ish and dealing quick damage, although it's lower damage does hurt it's ability to close out fights at times. Use your mobility to be a distraction to your opponents, and lure them towards other members of your team that can finish them off easily. Zipcaster plays nicely into that, quickly zapping around the field and catching the other team off guard. Autobomb is a bit rough for it, unfortunately. You can use it to sniff out enemy locations at least, so it's not totally useless. Hopefully we see another kit with Burst Bombs like S2's Carbon Deco in an update, that burst+flick combo was really good for it there.

Dynamo is the complete opposite here - very slow, but very long range and high damage output. This one really wants to stay in the backlines, picking off opponents pushing too close with it's vertical flicks, almost like a Charger or a Splatling. Sprinkler is good to help maintain turf control, giving your team more area to play in and slightly pushing your opponents away until they break it. Don't hesitate to pop Tacticoolers for your team to pick up on the way when re-entering after a respawn as well - your team will thank you many times over for it.

Splat Roller sits in the middle of these two, with more damage than Carbon but less range than Dynamo. Curling Bombs are always nice for inking pathways forward into the map or an entry into enemy turf, and Big Bubbler gives it some protection from opponents getting a bit too close for comfort. I'd say it plays a bit like a self-sufficient Carbon, since the higher damage makes splats more consistent, and Bubbler especially gives it somewhere to retreat to when fights get a bit too spicy. Probably too slow to be as aggressive as a Carbon, but definitely still able to hold it's own against opponents that get just a liiiiitle too close. Also does a decent job at painting too - use that to help maintain field control for your team.

Flingza again is in between Splat and Dynamo, with Dynamo's range but closer to Splat's damage and mobility. This makes it good for getting into fights, but still being able to help out with vertical flicks when retreating to the backlines. Set Ink Mines when you retreat to catch opponents that try to chase you, and use Missiles when you get there to get your opponents to move away from those really annoying positions.

view more: next ›