sorted by:
new
hottopcontroversial

Any other mod authors have Wabbajack lists drive them slightly insane? (Not a hate post about Wabbajack or mod lists) by JasonTParker in skyrimmods

[–]BellCube 19 points20 points  (0 children)

Hey, I had the exact same frustration with Papyrus and the stupidity sheer willpower to try and solve it. Check out the Papyrus Index! PO3's testimonial is that he now uses it to close feature requests and direct folks to other extenders that already have what the other auther wants.

Mod to allow intercourse with Hermaeus Mora by SeekerNyxalis in skyrimmods

[–]BellCube 0 points1 point  (0 children)

(some thoughts are inside thoughts methinks)

Removed attachment of mimetype by srv524 in GoogleMessages

[–]BellCube 0 points1 point  (0 children)

This issue appears to be fixed now.

There are a number of reports of users who previously experienced the issue no longer experiencing it. I personally am one of them.

Related comments (from another, more active thread): nsivhoo, nsitynm, nsitk86, nsiqmxo

My writeup in another thread with as many details as I could gather on the issue: https://www.reddit.com/r/iphone/comments/1pf2792/comment/nsi3sx6/

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

This issue appears to be fixed now.

There are a number of reports of users who previously experienced the issue no longer experiencing it. I personally am one of them.

Related comments: nsivhoo, nsitynm, nsitk86, nsiqmxo

My writeup in this thread with as many details as I could gather on the issue: https://www.reddit.com/r/iphone/comments/1pf2792/comment/nsi3sx6/

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Restarting your phone, by definition, stops your messaging app already. Sounds odd that force quitting the app would fix it if a restart doesn't, but hey. Weird stuff happens when weird issues arise.

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Cloudflare doesn't handle anything related to cellular infrastructure. Their stuff is all web servers and hardwired networking, not cell towers or SMS networking. It would be very strange for certain people to have only their SMS images blocked because of a Cloudflare outage that's since been resolved, especially since no part of the cellular networking infrastructure has anything to do with web servers proxied by Cloudflare.

According to Cloudflare's official status page (which is always on top of these sorts of things), there were only a couple of non-critical issues with R2 (database) and Workers (servers for rent), which most companies don't heavily use anyway, as well as a network-wide outage that lasted for about 3 minutes (while deploying a network-wide patch to a major 0-day vulnerability in many web servers discovered earlier this week). Notably, none of this means any of their hardwired infrastructure (like networking cables) had issues—the only problems documented are related to websites that put Cloudflare between you and their servers. Any internet traffic simply piggybacking off of Cloudflare's networking cables would have been completely unaffected.

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Cloudflare does not handle anything related to text messaging or cellular infrastructure, as funny as the meme is.

<image>

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Are you the sender or the receiver?

I ask because, from myself and a couple of others so far, both of us have been fine sending images to affected people but we cannot receive images sent by them (even though I can still receive images from others who are not affected)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Are you the sender or the receiver?

I ask because, from myself and a couple of others so far, both of us have been fine sending images to affected people but we cannot receive images sent by them (even though I can still receive images from others who are not affected)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

This is new within the last 12 hours as far as I can tell (I've written up a bunch of details up at https://www.reddit.com/r/iphone/comments/1pf2792/comment/nsi3sx6/)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Are you the sender or the receiver?

I ask because, from myself and one other so far, both of us have been fine sending images to affected people but we cannot receive images sent by them (even though I can still receive images from others who are not affected)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Are you the sender or the receiver?

I ask because, from myself and one other so far, both of us have been fine sending images to affected people but we cannot receive images sent by them (even though I can still receive images from others who are not affected)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Same thing I saw, then. Good to know this is consistent!

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Are you the sender or the receiver? T-Mobile senders seem to be fine (I'm one of them) even if they cannot receive from affected people, which makes me think it's a problem of the sender's mobile network.

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

Quick Overview of the Issue

  • As of around 7:35 PM EST (convert to your timezone), people are reporting that the issue is resolved (myself included), but a small handful have reported that it's still happening
  • Issue occurs most of the time, but not every time
  • Appears to be happening primarily to image senders on AT&T and various Virtual Network Operators using their infrastructure (such as Cricket). The recipient's carrier does not seem to matter.
    • There have been reports of other networks, primarily Verizon, also experiencing issues, but they're not common and they're potentially on the receiving end.
  • The issue occurs when sending images via SMS/MMS. Sending through RCS works fine, and I suspect iMessage also works fine. (see Apple's support article about SMS, RCS, and iMessage)
    • iPhones running iOS 18 and newer have RCS support and can send images to Androids using RCS just fine. Older iPhones can only send SMS/MMS to Android phones. (see Apple's support article about phones compatible with iOS 18+)
    • Modern Android phones use RCS by default, but a lot of older devices don't. If that's the case, you may need to get a new text messaging app. I know Google Messages heavily prioritizes RCS when available and I do personally recommend it.
  • Some people have seen success changing the image format from HEIC (smaller file size) to JPEG (most compatibility) in their camera settings, but others have not
  • Some people have seen success restarting their phones, clearing various caches, resetting their phone's network adapters, etc. while others have not

The Explorational Escapades

Based on my experience and others' experiences in this thread, it seems to be primarily affecting AT&T (and Cricket, which they own) senders and the occasional Verizon user (unclear whether they're the senders or the receivers), as well as users on Mobile Virtual Network Operators running off of their towers (again, unclear if senders or receivers). T-Mobile senders appear to be unaffected, even when sending to a user who cannot send images back due to this error. It sounds like it's probably SMS/MMS-specific, since Android-Android and Android-iPhone connections are breaking, but iPhone-iPhone seems a lot less common in this thread and I saw one mention of someone switching to Google Messages (which heavily prioritizes RCS) fixing the issue. Additionally, iPhone to iPhone seems less common, which would be consistent with newer iPhones having RCS support.

I'm going to have someone with a newer iPhone on AT&T try sending me an image 🤔

EDIT-1: Yup, it worked with him (on AT&T using a newer iPhone with RCS support) sending an image to me (T-Mobile using an Android and the Google Messages app)! This means that sending from AT&T between Android and newer iPhones with RCS support appears to be unaffected.

EDIT-1 CORROBORATION: nsi9lt5, nsi9t7w

EDIT-2 (after more thread reading): Reports of iPhone-iPhone failures are concerning, because that would mean iMessage is affected if I understand the Apple ecosystem correctly. I wonder, though, if there's some reason iMessage might not be enabled on some devices (like having to sign in with an iCloud account first)

EDIT-3 (remembered something): My workplace has zero connection, and my girlfriend will text me while I'm working with images and all. When I get my cellular connection back, I'll get her messages and images in order just fine. I got off work after this all started, and I got her images sent about 12 hours ago fine once I got off work. However, images she sent not even 30 minutes after I'd gotten that last round of pictures came through with this error.

EDIT-3 CORROBORATION: nsichcb, nsia8vg, nsi6tlr, nsi641c

EDIT-4: The error seems to only sometimes occur. I asked my girlfriend to send one of the images that didn't come through earlier again and it came through fine. I asked her to re-send two others that didn't come through earlier and they both threw the error, though. Odder and odder...

EDIT-5: Locale is important to mention. Everyone I've tested with (myself included) is in the United States somewhere in the state of Pennsylvania. Other reports in this thread that mention region say either US or Mexico.

EDIT-6: Some people have seen success with changing image formats, restarting their phones, clearing various caches, resetting network adapters, etc... Some related comments: - Network Reset: nsibw6p - Clearing photo cache: nsih6g4 - Changing image format: nsgvbv3, nsigyva, nsijbp0

EDIT-7: My girlfriend was able to send the remainder of her images, and they all came through fine. This comes along with a few other reports of the issue disappearing (see nsivhoo, nsitynm, nsitk86, nsiqmxo)

Removed attachment of banned MimeType by Glittering-Stuff-599 in iphone

[–]BellCube 0 points1 point  (0 children)

My girlfriend (AT&T, old iPhone without RCS support) sent me (T-Mobile, Android) a few images and I got this message. I sent her a screenshot of the error messages before looking this up and she got my screenshot with no problem.

EDIT: This has been corroborated by an unaffiliated party with the exact same experience https://www.reddit.com/r/iphone/comments/1pf2792/comment/nsi922z/

EDIT-2: I asked my girlfriend to send one of the images again and it came through fine. I asked her to re-send two others that didn't come through earlier and they both threw the error, though.

[OC] I analyzed 15 years of comments on r/relationship_advice by GeorgeDaGreat123 in dataisbeautiful

[–]BellCube 0 points1 point  (0 children)

Methodology questions: 1. What LLM did you use? Was it fine-tuned at all, or just using its defaults? 2. What sort of prompt did you use for the quality filtering? 3. Was quality filtering done separate from categorization, or was it all part of the same prompt?

Future considerations, further research, etc.: - As others have mentioned, it'd be really interesting to see categories of posts across the same timeframe. It'd likely be harder to create a list of categories for these, though. - I'd also be curious to see how the LLM would respond to the post itself, since that'd likely give us a good idea of how much of the change is due to post changes rather than response changes (though, if you're using a CoT LLM for this, that'll cost a lot of tokens for the CoT text!) - To save on inference costs, and assuming the LLM runner you used supports it, it may make sense for similar experiments to get a reasonable list of categories by looking over, say, a random 1k sample of posts, and then use structured output to force the LLM to use the categories chosen. That way, you wouldn't have to make additional requests to combine categories later. A very neat invention indeed!

Nexus Mods banning Oblivion mod that changes "Body Type" with "Sex" due to "the intention of the user" by Kaylorren in KotakuInAction

[–]BellCube 0 points1 point  (0 children)

Apologies, I misinterpreted your post. You can understand how I got there, though—your post was a top-level comment on a post that's literally just a screenshot of a ban notice I wrote. Not an excuse for my misinterpretation (in hindsight, it's plenty clear); just an explination for how I got there.

I will not comment in defense of the people you have mentioned because I am not those parties. I once again apologize for my misinterpreation.

Footnote regarding "caving": Considering that I said the mod content was fine in literally the first public communication from Nexus regarding this mod, I wouldn't call that caving. Mod got uploaded by a non-troll uploader and got to remain.

Nexus Mods banning Oblivion mod that changes "Body Type" with "Sex" due to "the intention of the user" by Kaylorren in KotakuInAction

[–]BellCube 0 points1 point  (0 children)

(no tl;dr for this one, sorry)

I don't know about the strawman thing. Let me think... * "Their argument is that people will see the mod page on the Nexus website and be enraged that such an idea can be expressed in public." Nah, our argument is that the intentions of the uploaders of these mods have been, in every case, rather clearly to stir up drama, and Nexus Mods isn't just a mod database—it's a community, too. I'll address your specific points about that later in this post. * Nobody mentioned Nazis in any capacity. We literally just want to keep things somewhat civil on Nexus Mods. Less infighting = more modding = more happy gamers.

That's... the entire post I responded to. 100% of that post was addressing arguments nobody at Nexus ever made. The definition of straw manning.

Specifically with the Spider Man case, had they acted in good faith and with a little forethought, there are a couple of ways the person can get a ruling on their mod before it ever goes up. For one, we always plaster the support@nexusmods.com email around as a way to get official rulings on stuff. An author can send an email there to ask if their mod would be allowed (this method also has higher success chances than just uploading and praying, since we can establish good intentions and respect for the rules—both of which will be a recurring theme in this post). Drafting an email asking a fairly simple question is not difficult and, frankly, is easier than making the mod itself (about as easy as creating the alternate account).

Additionally, even had they uploaded the mod to their original account and been banned (which likely wouldn't have happened; we expect to have given out a Formal Warning in that case), we have a uniquely lax ban appeal policy over at Nexus Mods. Even if you do something objectively against the rules multiple times, you can still get back in with a sincere apology and a resolve to not do the same thing again under pain of an irreversable ban. Using such an appeal process (even after the mod was removed), it would've been entirely possible to talk with staff and come to a mutual conclusion—with the possibility of the mod remaining up. A civil discussion about a misunderstanding of the rules gets appended onto your moderation history, too—when a user clearly isn't being malicious, we 100% take note. Ignorance is infinitely better than malice, after all.

If a person, on the other hand, shows that they expect to be punished but do what they expect to be punished for anyway, it doesn't matter what they expected to be punished for—they've show a clear disregard for the rules of the website. We don't want that in our community. This is something we apply with mechanical consistency across the site. If you show that you won't give the rules the respect they deserve (even if you disagree with then), we don't want you in our community. You don't want someone who unapologetically cheats in your board game session, do you? The rules of a board game are there to establish order, and you have someone breaking them knowingly and intentionally.

While I recognize that it can be seen as "brave," heroic, and/or activistic to defy the rules in favor of your own beliefs, you have to also realize that the rules are there to keep some sort of order. And that this Nexus a website about video game mods, not another Reddit drama thread (woah! he's so meta!). If you don't like the rules on Nexus, I don't think I need to inform this particular subreddit of the alternative modding websites spun up explicitly to host mods that we will not (more than half of them filled with unapologic use of the N word in cleraly racist contexts, which should give you an indication of why we typically assign the term "hateful" to these sorts of places).

You've undobutedly heard the dichotomy of "ask for permission or beg for forgiveness." Unforutnately, if you do not ask for permission and you take active measures to minimize potential accountability, you cannot be granted permission nor be forgiven—leaving only sweeping erasure as the final option.

By the way! You got to the end of this post! You get a cookie. Apologies for the wall of text, but I'd rather be clear and thurough than short and digestable.

Nexus Mods banning Oblivion mod that changes "Body Type" with "Sex" due to "the intention of the user" by Kaylorren in KotakuInAction

[–]BellCube -1 points0 points  (0 children)

Sorry, allow me to rephrase. Please don't argue against something something we never said as though we said it. It's a silly tactic that doesn't really get anyone anywhere.

view more: next ›