bmlzootown

The point is, as others have pointed out, that the changes they're making hurts developers, moderators, and users. Use a popular 3rd party app? Good luck -- they're all basically shutting down due to upcoming API pricing changes. Use moderation tools? Good luck -- only those tools that hijack your current session (think Chrome extensions) are safe... for now. Develop a 3rd party client? Good luck -- pricing for API usage is worse than Twitter. Not to even mention the whole Spez/Apollo situation where Steve quite literally lied about the dev (of Apollo) threatening Reddit in an extortion attempt. If you're really curious as to why this is happening, and what led to this situation, simply read the news -- there are no shortages of articles from most major tech outlets at least briefly covering this controversy. But per the title of this thread, /r/explainlikeimfive has you covered already:

An unintended bug caused by the adoption of channels. If you select the main listing (left) rather than channel (right) for LTT, it should work. I haven't been able to work on the fix just yet, but such will be present whenever the next update is pushed.

Well, now it's turned into a $50 credit to buy a new band.

Got an email earlier today in response about having no band and they've agreed to send me a new one. I did buy one of the elastic bands off of Amazon for use in the mean time, however. Works well, but it's just not the same as the original.

Unfortunately, the instructions that I received via email for the initial (cancelled) repair didn't mention removing the band: It does say to remove accessories, but in no sane world is a watch band an accessory -- such is necessary for the device to properly function/be used. The instructions that I received with the box that they sent for the repair didn't mention removing the band either. If there were instructions to do so elsewhere, I didn't see it. Each communication about how to ship the product to them contained slightly different instructions.

Replacement watch has arrived. Had no band with it. Old watch hasn't been shipped back, which had my band. Now I have a working watch but cannot wear it.

Yet Another Update: After contacting the Extra Care representative who reached out after my BBB complaint, they've responded with the following: They've finally offered to replace the device, thankfully, and I've accepted. Hopefully, once I update after receiving it, the new watch doesn't decide to brick as well.

Update: I got an update 2 days ago saying that the repair was on hold due to part unavailability, and now I've received an email stating that my unrepaired device is being returned. \ The ticket itself confirms that the repair has been returned. I've sent a follow-up email to the customer service associate that prompted me to reship the device for said repairs post-BBB complaint. Hopefully answers will follow. Does anyone know what "ENR REFUND" entails, exactly (second image, in place of "tracking")?

My apologies, I meant an additional $128 on top of the total $400+ I spent only a year ago for the device itself, given that its lifespan has been very... short. I've corrected that in the above. That said, as an update, Samsung just called me back in response to my BBB complaint and have offered a one-time free repair for the device. Since it was shipped out this morning (as per the cancellation of the $128 repair), they've opened a new ticket and have issued me a new shipping label so that I can send it back once it arrives. I understand that life is often unfair, but the issue primarily seems to be older near-launch devices and it's just bad business to go, "oh well, you guys are just screwed". Those devices, given their age, are more than likely out of warranty as well now, so refusing repairs unless we all fork over even more money for something that is entirely Samsung's fault is a bad take no matter how you look at it. That's just bad business.

Just thought I'd post this here for some increased visibility. After update GVI3, it appears that some Galaxy Watch4's have been bricking (and such has continued even with their latest update -- GVK4). General consensus is that the older the device, the more likely it is to brick [1][2]. [5] [4] I, unfortunately, was affected. My device updated the morning of the Nov. 10th, was fine when I left for work. Sometime during the middle of the day, I noticed that my phone had a notification that my watch had disconnected, but didn't think much of it at that point because I was busy. Went to flick my wrist to turn my watch screen on, check the time, make sure I had alarms set for deadlines that we have throughout the day, and I noticed it was off and wouldn't turn on. After a bit more research, I learnt that the latest update(s) had been bricking devices and was unable to revive the device once I got home [3]. After sending the watch in for repairs, I was informed that I was going to be charged $128.82 for the PBA to be replaced. I contacted support via phone this morning and they were unable to tell me anything other than I'd have to pay the fee, or they would ship me back my $400 brick. Tried reaching out to support via Twitter just a few minutes ago and they responded with a request to DM them, but their final response was essentially the same. Only other option is to visit an in-person repair shop, but I can't currently do that as my watch is still at their repair facility (which it was shipped to prior to them requesting even *more* money to fix an issue they caused): Granted, my device is out of warranty, but how is it that they justify charging for repairs like this where the issue was caused by their faulty update? I need some sort of watch for work (alarms, time, steps taken, etc.), and the added benefit of having access to phone notifications is nice given that I can't always whip my phone out. At this point, though, I'm absolutely disgusted that I've essentially spent over $400 USD on a device that, only one year later, is a paperweight. [5] Sources: https://www.androidpolice.com/new-samsung-galaxy-watch-4-update-out-might-brick-watch/ [1] https://www.reddit.com/r/GalaxyWatch/comments/ysww4r/galaxy_watch_4_brick_info_database/ [2] https://www.google.com/search?q=galaxy+watch4+brick+site%3Areddit.com&iflsig=AJiK0e8AAAAAY3aj43E3-ela-sgxEcKw-DbqTq9qLtuA [3] https://doc.samsungmobile.com/sm-r880/dbt/doc.html [4] https://doc.samsungmobile.com/sm-r890/dbt/doc.html [5]

Developer here! I get where you're coming from, as the final package that's uploaded to the Roku store can't be decompiled on the end-user's side, thus you never know 100% for sure what's in the final code. That said, nothing phone's home on my end, and the app itself doesn't save any user data other than cookies -- there was a short period where Cloudflare was causing issues and users had to manually grab the CF token from the FP site itself and send it to their device (via a custom-written REST API on my server that made it easier for users to copy/paste the token rather than manually having to type it in via remote/phone), but that was phased out shortly after once another solution was found. The source is also available via Github if you would like to read through it. If you have any questions/concerns/feedback, I'm always available here, via Discord (link in the thread that Logical linked above), or on most any other platform where a "bmlzootown" exists (Twitter, Reddit, etc.).

This is interesting. I myself am partially red-green colorblind, but I've never really had such an issue. What type of colorblindness do you have?

The old private channel code for Roku is now gone; beta period is up! The actual release is available via the channel store. Updated info in the OP about tvOS. TL-DR -- Jamamp (Jman012) has written a very nice client. If you have an Apple TV, you should go check it out!

As an update/reminder, the old version of Hydravion on Roku, per recent changes on Roku's behalf, will expire in roughly 40 days. The OP has been updated with the current link to the release on the Roku channel store. It can also be found by searching said channel store for "Hydravion". I was going to add a popup notifying users to the existing beta channel, but their dev portal won't let me publish the update for whatever reason. Will continue looking into it.

New update, 1.3.5, for AndroidTV is available via GitHub -- fixes an issue where, under specific circumstances, a value would be added to an ArrayList at index 1 when 0 did not yet exist, causing the channel to crash. Big thanks to Sherlock in the Discord for providing logs!

Just pushed an update, precompiled APK is available on Github, per usual. Let me know if there's any issues.

I bought water bottles. They were more than worth it.

Did it crash immediately after logging in? In the video, it looks like you've already authenticated (as you mentioned) -- first it should grab all the creators you're subscribed to and then it will grab the latest 20 videos for each. Without logs, however, I can't really do more than guess as to what could be the issue. Do you have ADB (Android Debug Bridge) installed, by chance? If so, you should be able to follow this to enable debugging and connect. From there, run: adb logcat > logcat.txt Open the app once the command is running, wait for it to crash, and then close the terminal/command prompt window. From there, look for any errors, identified by the following (notice the capital E, which stands for error) toward the end of logcat.txt and either report them here/Discord, or PM me (preferred option as output may contain sensitive cookies/tokens used for account/content authentication): 07-11 21:56:26.208 4580 4745 E Volley : [319] NetworkUtility.shouldRetryException: Unexpected response code 404 for https://example.com

This should be fixed as of v1.3.1. I had originally set it to replace the default "1080" with whatever resolution the user selected, but if they went to change the resolution again, it would still look for "1080" (which no longer existed as part of the video URL). This was entirely my bad, and I'm surprised that the issue hasn't come up before now, so thanks for pointing it out! I tried to reproduce this issue to no avail, both before and after the aforementioned fix. If you experience this again, let me know (along with the exact steps you took to cause it). The livestream button in the settings (3rd row, bottom of the screen) are a leftover feature from before I added background livestream checks. I had left this to allow users to manually force-test/-play a stream if necessary in case the livestream check broke. If you attempt to play a livestream when the creator isn't live, it'll present you with the black video screen, followed by the "livestream not found" message, but that should only occur when you've attempted to force-play a stream that isn't live. When a stream is live, it should now show up in the video feed as the first available video (with "LIVE" in the title).

I'll look at this when I get home tonight. Sorry about that!

The latest video featuring Linus was released earlier today on YouTube (May 17), but yesterday on Floatplane (May 16). By that logic alone, it should be safe to assume that there was no intended drop there, since that'd give FP subscribers an unfair advantage. And I'm assuming you don't mean the latest video of theirs in general, from TechLinked, as you're responding to a post over 5 hours old (unless I've missed a more obvious video that would fit the description). I doubt they'd have someone try and gain unauthorized access to an email account, anyhow. The whole idea is flawed given that, after a certain number of unsuccessful login attempts, everyone would be locked out of the account (had this happen personally in the past when trying to get into an old account of mine). Not to mention how, er, shady such would be. I could be wrong, granted... But I doubt it.

Per the current pinned post/solution at the top of the page:

Floatplane

This was my exact takeaway as well, since they are acting as a 3rd party retailer at this point. The only difference is their methodology when it comes to actual transactions with customers. No matter the intention, people will always find something to gripe/nitpick about.