[ SECRET POST #6814 ]

Sep. 1st, 2025 17:48
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets

⌈ Secret Post #6814 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.


More! )


Notes:

Secrets Left to Post: 01 pages, 25 secrets from Secret Submission Post #973.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

(no subject)

Aug. 31st, 2025 23:43
skygiants: clone helmet lit by the vastness of space (clone feelings)
[personal profile] skygiants
Sometimes you hit the end of a book and immediately think 'I'd like to read that over again' because there's some sort of big twist that you know will make you experience the whole thing differently, and sometimes you hit the end of a book and think 'I'd like to read that over again' not because of any Major Plot Reveals, but because the book is woven together in an interesting enough way that you want the chance to fully appreciate how all the pieces fit now that you've seen the full puzzle.

This second case was my experience with The Fortunate Fall, a cyberpunk novel from 1995 that came back into print last year and that I did not quite manage to read in time for the Readercon book club (so I extremely appreciate [personal profile] kate_nepveu's extensive notes on it including the intertextuality with Moby Dick.)

The book is narrated by Maya Andreyeva, a 'camera' -- a cyborg news-reporter modified to provide not just full sensory experience but also associated memories, context, etc. to the viewing public. When the book begins -- well, when the book begins, it has already ended, as Maya tells us; her whole audience has already experienced all the relevant events through her eyes, and now she's telling it to us again, in a narrative that she can control and that's on her own terms, contextualizing only what she wants to contextualize and hiding what she wants to hide. Which is a very fun way to begin a book, by consciously keying you into its distortions and elisions, and for the most part I think the text lives up to it.

Anyway, when not the book but the story begins, Maya has decided to put together a series commemorating the anniversary of a major [future]-historical tragedy, and has just gotten assigned a new screener for the project -- a sort of editorial figure who sits in between the camera and the audience, filtering out bodily functions and bad words and anything else that could be trouble for the network. Because of the amount of time they spend immersed in the heads of their cameras, screeners tend to become rapidly very enthusiastic and romantic about them! Maya's new screener Keishi is a beautiful and mysterious young woman who is, indeed, very enthusiastic and romantic about her! And definitely not keeping any secrets about her skills, her identity, or her reasons for being there working with Maya, no sir.

In true noir mode, Maya's initially normal-seeming historical research into a tragedy that's as long-ago and terrible and world-shaping for her as the Holocaust is for us ends up leading her increasingly out of the bounds of conventional society down a dangerous rabbithole, at the end of which lies forbidden knowledge about the world, forbidden knowledge about her own past, and forbidden knowledge about a really sad whale. And, following along with her, we as readers gradually start to piece together not only the particular dystopian shape of the world -- the parts that Maya already knows and the parts that Maya doesn't -- but also the shape of the story, the themes that it cares about and that have actually been driving the plot this entire time: embodiment, censorship, the atrocities we commit to end atrocities, and the power and beauty and absolute hard limits of queer love, just to name a few.

I don't know that everything about the book has fully aged well. I understand the well-meaning failure mode in cyberpunk that leads an author to posit a Monolithic Utopian Isolationist Africa when the rest of the world has gone to dystopian shit, but I think it is a failure mode. I also admit that I thought the entire grayspace digital-world sequence was a little bit boring. But for the most part the book is not at all boring, it's interesting in the way that only a book that actually trusts its readers to be doing an equal amount of work as they go is interesting. I did not in fact actually then read the book over again, upon hitting the end, because it was extremely overdue at the library [and I had five more equally overdue books on the pile] but I expect I will do so sometime in the nearer rather than the further future. Maybe I'll have the chance to hit another book club.

Code deploy happening shortly

Aug. 31st, 2025 19:37
mark: A photo of Mark kneeling on top of the Taal Volcano in the Philippines. It was a long hike. (Default)
[staff profile] mark posting in [site community profile] dw_maintenance

Per the [site community profile] dw_news post regarding the MS/TN blocks, we are doing a small code push shortly in order to get the code live. As per usual, please let us know if you see anything wonky.

There is some code cleanup we've been doing that is going out with this push but I don't think there is any new/reworked functionality, so it should be pretty invisible if all goes well.

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise posting in [site community profile] dw_news

A reminder to everyone that starting tomorrow, we are being forced to block access to any IP address that geolocates to the state of Mississippi for legal reasons while we and Netchoice continue fighting the law in court. People whose IP addresses geolocate to Mississippi will only be able to access a page that explains the issue and lets them know that we'll be back to offer them service as soon as the legal risk to us is less existential.

The block page will include the apology but I'll repeat it here: we don't do geolocation ourselves, so we're limited to the geolocation ability of our network provider. Our anti-spam geolocation blocks have shown us that their geolocation database has a number of mistakes in it. If one of your friends who doesn't live in Mississippi gets the block message, there is nothing we can do on our end to adjust the block, because we don't control it. The only way to fix a mistaken block is to change your IP address to one that doesn't register as being in Mississippi, either by disconnecting your internet connection and reconnecting it (if you don't have a static IP address) or using a VPN.

In related news, the judge in our challenge to Tennessee's social media age verification, parental consent, and parental surveillance law (which we are also part of the fight against!) ruled last month that we had not met the threshold for a temporary injunction preventing the state from enforcing the law while the court case proceeds.

The Tennesee law is less onerous than the Mississippi law and the fines for violating it are slightly less ruinous (slightly), but it's still a risk to us. While the fight goes on, we've decided to prevent any new account signups from anyone under 18 in Tennessee to protect ourselves against risk. We do not need to block access from the whole state: this only applies to new account creation.

Because we don't do any geolocation on our users and our network provider's geolocation services only apply to blocking access to the site entirely, the way we're implementing this is a new mandatory question on the account creation form asking if you live in Tennessee. If you do, you'll be unable to register an account if you're under 18, not just the under 13 restriction mandated by COPPA. Like the restrictions on the state of Mississippi, we absolutely hate having to do this, we're sorry, and we hope we'll be able to undo it as soon as possible.

Finally, I'd like to thank every one of you who's commented with a message of support for this fight or who's bought paid time to help keep us running. The fact we're entirely user-supported and you all genuinely understand why this fight is so important for everyone is a huge part of why we can continue to do this work. I've also sent a lot of your comments to the lawyers who are fighting the actual battles in court, and they find your wholehearted support just as encouraging and motivating as I do. Thank you all once again for being the best users any social media site could ever hope for. You make me proud and even more determined to yell at state attorneys general on your behalf.

[ SECRET POST #6813 ]

Aug. 31st, 2025 15:06
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets

⌈ Secret Post #6813 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.


More! )


Notes:

Secrets Left to Post: 02 pages, 31 secrets from Secret Submission Post #973.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

[ SECRET POST #6812 ]

Aug. 30th, 2025 14:13
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets

⌈ Secret Post #6812 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.


More! )


Notes:

Secrets Left to Post: 02 pages, 37 secrets from Secret Submission Post #973.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

[ SECRET SUBMISSIONS POST #974 ]

Aug. 30th, 2025 14:08
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets
[ SECRET SUBMISSIONS POST #974 ]




The first secret from this batch will be posted on September 6th.



RULES:
1. One secret link per comment.
2. 750x750 px or smaller.
3. Link directly to the image.

More details on how to send a secret in!

Optional: If you would like your secret's fandom to be noted in the main post along with the secret itself, please put it in the comment along with your secret. If your secret makes the fandom obvious, there's no need to do this. If your fandom is obscure, you should probably tell me what it is.

Optional #2: If you would like WARNINGS (such as spoilers or common triggers -- list of some common ones here) to be noted in the main post before the secret itself, please put it in the comment along with your secret.

Optional #3: If you would like a transcript to be posted along with your secret, put it along with the link in the comment!

[ SECRET POST #6811 ]

Aug. 29th, 2025 18:41
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets

⌈ Secret Post #6811 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.


More! )


Notes:

Secrets Left to Post: 00 pages, 00 secrets from Secret Submission Post #972.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

[ SECRET POST #6810 ]

Aug. 28th, 2025 18:45
case: (Default)
[personal profile] case posting in [community profile] fandomsecrets

⌈ Secret Post #6810 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.


01.


More! )


Notes:

Secrets Left to Post: 01 pages, 06 secrets from Secret Submission Post #972.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Profile

hafl: (Default)
hafl

January 2013

M T W T F S S
 123456
78910111213
1415161718 1920
21222324252627
28293031   

Most Popular Tags

Style Credit

Page generated Sep. 2nd, 2025 21:14
Powered by Dreamwidth Studios