All those folks in the 50+ age group that grew up with "Russia is enemy #1" are probably cycling through waves of intense work and prolonged orgasm.
I wouldn't be surprised if one of the first things considered in strategizing any armed conflict is whether they want Russia and China to know that we have X or are capable of Y. Russia has shown their hand. If they could do more, they would have by now.
It has also taught NATO that Russia is still in the barbaric tactics mindset. Hospitals, schools, churches, shipping centers - they're all valid targets. If Russia wants a position, they'll level the entire town. That certainly changes the plans, of anyone thought they would abode by the Geneva Conventions.
It's like a watermelon on a toothpick. I bet he was going home to cry on his oversized pillow.
Ugh, you just had to say "anti-vax" for most people to know he's a certified stooge or a turbo-dumbfuck.
I think it's hard to go wrong with Murakami. I don't remember much TEV specifically, but I remember enjoying it.
Thanks.That's kinda what I thought, but assumed I was missing something with the amount of attention the transfer of this one weapon platform has received. I guess it's also symbolic of the level of commitment by NATO, since it's not just a few planes, but also ammo plus training plus support framework.
I'm glad we're not just throwing ammo at the situation and wishing Ukraine the best of luck, though I do wish we were doing more.
One thing I've missed in the discussion of sending F-16s is the role they'll play.
From what I've seen, Russia still has significant air defense capabilities, and they launch air fired weapons from deep in their own territory. So, if the F-16s can't get too far upfield, due to defenses, and there isn't much they can do in air-to-air combat, what advantage do they have over longer range artillery?
I... I'm speechless.
Although, as a professional internet nitpicker, I have top s say I'm surprised he didn't go into color theory more. Easy 45 minutes of additional content there. (I guess he touched on it, but there's so much more.)
Now I remember why I looked at lasagna cat a few years ago and, after a minute or two, decided to set it aside. There's a whole lifetime's worth of content to drown in.
I use this one. There are probably better ones, but now I have holders and cases for them, so there's no going back now.
I do the same thing with low poly brains (and a swatch card). I'm tempted to order one roll of each filament I used before starting this, but that would be hard to justify. My collection shall be forever incomplete.
Generally, if someone's being a total asshole so severely that they have to be yeeted with several thousand other unaware bystanders, I expect to see a bunch of examples within the first... 2, maybe 3, links.
If someone can point me to a concise list of examples (actual data), I find it more disturbing that an admin on another server can yeet my account because they make noise on a discord server.I mean, yes, federating is a feature, but why even offer the ability to enroll users? Maybe for a group of friends, or something, but just rando users is nothing but a liability to everyone involved.
Oh, I understand the tactics being used. I was implying that person c was obviously stalking person a and pounced the moment they did something less than perfect.
My guess is there isn't anything of substance, so person c's sensitivity got amplified with time and obsessing over whatever is going on, leading them to overreact. But, not c has to double down if they want any chance of being taken seriously if a significant cause to defederate occurs.
I got around 5 links deep for each of the links in the admin's post, and fuck if I know. There was an argumentative user, but they were articulate and thoughtful. Not dropping slurs or wasting space nonsense, but still bordering on "edgy". The person pushing the defederation appeared to be bullying them and on a power trip.
It was embarrassing. That's all I took away. (My opinion can change if someone digs through the shitpiles of nothingness to pull up some actual naughty posts, but that's not going to be me.)
I almost thought I had written your comment and completely forgot about it. No, I just almost made the exact comment and want that hour of my life back.
If there was some over the top racist rant, I sure didn't see it. And the admin pushing for the defederation sounds so bizarre. Bizarre is the best word I could come up with because "petty" makes me think it was like high school politics. This is closer to a grade school sandbox argument.
The worst I saw was "defedfags" and it was used in a way that was meant to highlight how they never said anything offensive. Like saying, "If you thought what I said before was offensive, let's see how you respond to something intended to be negative."
The crazy thing is that the decision is being made because the admin just liked a post. It's not even because of the post content - which has nothing controversial and appeared maybe 8 times in my Lemmy/kbin feed yesterday.
Editing to add that this is the article: https://kbin.social/search?q=wakeup+call
I'm not sure if it helps, but I wonder if this is linked to the inactivity error.
Load up any kbin thread or main page, open a new browser tab in the foreground, me around in the non-kbin tab for 15-30 minutes, and return to the kbin tab. Now any clicks on 'actions' (voting, posting, basically sending info to the server) sends you to an error page. Whatever info you were sending doesn't register (vote count or highlight, posts don't show up, etc.
I didn't have any logout problems at all until maybe a week ago. Since then I've been logged out 5+ times.
Not a big problem for me, but I could see it annoying others.
Agreed. I'm in my 40s, and I've never seen anywhere near the level of subsurface signaling and intentional complacency we're experiencing now.
Well, terrorists became boring, and they still want the loony wing of the GOP's clicks, so best to back off on Nazis and pro-Russians, leaving pedophiles as the safest bet.
At first glance, I probably thought JXL was another attempt at JPEG2000 by a few bitter devs, so I had ignored it.
Yeah, my examples/description was more intended to be conceptual for folks that may not have dealt with the nitty gritty. Just mental exercises. I've only done a small bit of image analysis, so I have a general understanding of what's possible, but I'm sure there are folks here (like you) that can waaay outclass me on details.
These intermediate-to-deep dives are very interesting. Not usually my cup of tea, but this does seem big. Thanks for the info.
(fair warning - I go a little overboard on the examples. Sorry for the length.)
No idea on the details, but apparently it's more efficient for multithreaded reading/writing.
I guess that you could have a few threads reading the file data at once into memory. While one CPU core reads the first 50% of the file, and second can be reading in the second 50% (though I'm sure it's not actually like that, but as a general example). Image compression usually works some form of averaging over an area, so figuring out ways to chop the area up, such that those patches can load cleanly without data from the adjoining patches is probably tricky.
I found this semi-visual explanation with a quick google. The image in 3.4 is kinda what I'm talking about. In the end you need equally sized pixels, but during compression, you're kinda stretching out the values and/or mapping of values to pixels.
Not an actual example, but highlights some of the problems when trying to do simultaneous operations...
Instead of pixels 1, 2, 3, 4 being colors 1.1, 1.2, 1.3, 1.4, you apply a function that assigns the colors 1.1, 1.25, 1.25, 1.4. You now only need to store the values 1.1, 1.25, 1.4 (along with location). A 25% reduction in color data. If you wanted to cut that sequence in half for 2 CPUs with separate memory blocks to read at once, you lose some of that optimization. Now CPU1 and CPU2 need color 1.25, so it's duplicated. Not a big deal in this example, but these bundles of values can span many pixels and intersect with other bundles (like color channels - blue can be most efficiently read in 3 pixels wide chunks, green 2 pixel wide chunks, and red 10 pixel wide chunks). Now where do you chop those pixels up for the two CPUs? Well, we can use our "average 2 middle values in 4 pixel blocks" approach, but we're leaving a lot of performance on the table with empty or useless values. So, we can treat each of those basic color values as independent layers.
But, now that we don't care how they line up, how do we display a partially downloaded image? The easiest way is to not show anything until the full image is loaded. Nothing nothing nothing Tada!
Or we can say we'll wait at the end of every horizontal line for the values to fill in, display that line, then start processing the next. This is the old waiting for the picture to slowly load in 1 line at a time cliche. Makes sense from a human interpretation perspective.
But, what if we take 2D chunks and progressively fill in sub-chunks? If every pixel is a different color, it doesn't help, but what about a landscape photo?
First values in the file: Top half is blue, bottom green. 2 operations and you can display that. The next values divide the halves in half each. If it's a perfect blue sky (ignoring the horizon line), you're done and the user can see the result immediately. The bottom half will have its values refined as more data is read, and after a few cycles the user will be able to see that there's a (currently pixelated) stream right up the middle and some brownish plant on the right, etc. That's the image loading in blurry and appearing to focus in cliche.
All that is to say, if we can do that 2D chunk method for an 8k image, maybe we don't need to wait until the 8k resolution is loaded if we need smaller images for a set. Maybe we can stop reading the file once we have a 1024x1024 pixel grid. We can have 1 high res image of a stoplight, but treat is as any resolution less than the native high res, thanks to the progressive loading.
So, like I said, this is a general example of the types of conditions and compromises. In reality, almost no one deals with the files on this level. A few smart folks write libraries to handle the basic functions and everyone else just calls those libraries in their paint, or whatever, program.
Oh, that was long. Um, sorry? haha. Hope that made sense!
(As part of the Reddit migration, any time I'm only able to find info on Reddit, I'm reposting it to kbin/Lemmy.)
TL;DR - To get the page's OCR text from Newspapers.com, replace /image/ with /newspage/ in the url with the thumbnail.
EDIT: @godless Pointed out that some libraries have access to Newspapers.com through a Library Edition portal. My local library has several newspaper archives, and I figured the first couple would be the most complete. Nope, but there was Newspapers.com Library Edition access buried under the fold. That worked!
Bonus tip - Also search for current info of close family members. The spokeo hit was due to searching his mother's name, and spokeo is too dumb to understand that deceased people don't move with their families to future homes. It treated his records like he was living ("Current" address, phone numbers, etc were listed, even though they were for his sister, who's still alive).
And here's my rant/vent/story...
I was looking for an obituary in that nebulous early 90's time period where only some info is digitized. Hi s family's having a memorial for him next week and I was hoping to bring a pic of the newspaper from his birthday and deathday, along with the obit. I had a general idea of the date of death, knew the city and funeral home, and his name minus middle initial. Sites like legacy.com refused to return a match. Even the state and county records sites were useless.
After a couple hours, I had only 2 partial hits. Bing Chat (yeah, I was surprised, too) said it found the obit, but it was locked behind a paywall. The newspaper that had it (which I checked earlier) said nothing was there. It appears that the obits are available going back to 2004. Dates before that were supposedly available in the paper's archive. The archive was 404. Or, rather, the entire domain was 404.
The second hit was on spokeo - one of those obnoxious sites that gives partial info and then wants you to subscribe to 3 different levels of services. But, from there I got his middle initial and the exact birthday and death date. That info helped.
I eventually made it to Newspapers.com, which threw up a paywall, but indicated it had the info. I did the usual checking the source and css, reader mode, incognito, etc. It was clear that the image was probably there, judging by the css. Nope. The only info I could find on getting through that barrier was on Reddit. It doesn't lead to the paper image, but the OCR text. Just replace /image/ with /newspage/ in the url with the thumbnail.
Good. It existed and was exactly where I was expecting through the whole search. Now to get the paper image that the text was extracted from... nope. Gotta sign up.
One last thing to try again, since Newspapers.com gave me the exact PAGE NUMBER.
I tried looking into the archives of the paper available in the library's database. It appears most obits (non-newsworthy ones) were excluded. My hypothesis is that the paper sold the archives to a site that stipulated that they must be excluded from other sources. It's the only explanation.
So, looks like I'll be visiting the library Monday to see if they have microfiche of the paper. WTF is going on that I can't find a major metropolitan newspaper's obit section in 2023? I can find 15 million pictures of influencers' breakfasts, but a 2x2 inch shred of paper is completely inaccessible. Not even a torrent out there of this stuff because who the fuck would make it hard to find an old newspaper?
(Forgot to mention that I used Google, Bing, DDG, and SearXNG. Bing was the most helpful, Google the least helpful.)
This shit right here is why I pirate - "great" business models. If there was a torrent of the entire decade's worth of that newspaper, it would have been easier to download that, compared to jumping through all these hoops.
Hey all,
I know many of us have avoided Reddit entirely, while others have been working to ween themselves off the toxic bot nest. Speaking for myself, I know I've had a few technical problems whose solutions were only found on Reddit.
The migration dust has settled a bit and it's pretty clear that bots mass migrating subreddits isn't the direction the kbin/Lemmy community wants to go.
I propose that these explicit recommendations be mentioned at signup and as part of the user's profile page:
- If Reddit is the easiest to access or only source of information you're searching for during regular browsing, please consider reposting that information to the relevant Fediverse community.
- Begin these title of these posts with "[RX]" so that Fediverse users know why a seemingly random post has been added.
- Please tag these posts with "RDX" (or "RedditExtraction") and the subreddit name it came from for easy filtering.
- This is especially important for technical and detailed posts, as liberating this information will prevent it from disappearing at a corporate goon's whim, and it helps other users transition off Reddit.
- Use whatever method you prefer for the format of the body. It's more important that the info is extracted than any rigid format be followed. You can:
- Link to the original Reddit post.
- Copy-paste the text, only mentioning the authors' screen names.
- Simply summarizing the info.
---
General Example:
- You search Fediverse posts for a solution to a computer problem, but find nothing.
- A search from Google yields nothing useful except a post on r/TechSupport.
- Create a new thread on kbin/Lemmy titled:
- [RDX] (the question you searched)
- Description of problem, including why it was hard to find.
- Description of solution, preferably including some indication of time in the original post. (Was this post 1 year old or 10 years old?)
- Any additional information you deem relevant.
- Tags: RDX, RedditExtraction, TechSupport, troubleshooting, etc.
---
Specific Example:
[RDX] Do PCIE to PCI slot conversion adapters require the PCIE or PCI version of drivers?
I have an old PCI card that I would like to use on a current PC. I've seen adapters that should work, but my particular card had both PCI and PCIE versions released. Which driver should I install, or does it even matter?
Response by u/..... in 2013:
> > > Install the PCI version. > Since the card itself is PCI, that is the "language" the PC needs to speak for it to understand. PCIE should be backward compatible, just not physically compatible. > >
I performed the steps recommended and it solved my problem.
Tags: RDX, TechSupport, PCI, PCItoPCIE, PCHardware
---
With proper identification (title or tags), it should be easier to add features to the website and apps for filtering out such posts.
I would be even more helpful if there was an option on the New Thread page that auto-filled some of this info or redirected to a form page with separate entries for each element.
Another, more complicated, possibility would be to include a user editable wiki with each community, with extracted data listed as a section. New entries and notes can be submitted, but require moderators approval. Unapproved entries would still show, but with a warning that it hasn't been approved yet.
Thoughts?
Everyone seems to be pointing to the Microsoft EEE model without explaining how it has changed since the 90s. Here's what it will look like in today's tech climate. (I forgot to mention in this wall of text that there will probably be a name change or two. Especially if there's a major controversy.)
Meta will play nice for a year or 2. They'll cordon off the Meta instances, respond to complaints from Mastodon users, hell, they might even open source some of their code. It'll seem alright.
All your FB and IG followers will one day appear. Meta flipped a switch and integrated ActivityPub into their apps. You'll be annoyed, but hey, more traffic = support for the technology, etc. Now you don't have to log into your FB account and have a little more control over your FB and IG feeds, so it doesn't seem too bad. That wasn't worth all the debate. Just block or defederate and move on.
Maybe you go to check out Threadscon a fun event with special panels and contests. They even highlight the great Mastodon contributions and influencers. They really value their Mastodon partners!
A few months later...
You get a notification from a relative - they want to Splork over Threads. Wait, WTF is Splork? Oh, it's the hot, new video messenger that also tracks your heart rate, or some shit. But, you can't Splork from Mastodon and it'll never be added because it's closed source and encrypted for 'Security' and 'The Children'.
You figure, "Fine, it's the same content. I'll try to only use Threads for Splorking and use Mastodon for everything else." You feel guilty, but you continue to promote Mastodon when you can. Meta even seems supportive. Oddly, there's more people on Mastodon that are all for Meta's move into the space. At least, I think they're people. I guess some could be bots. Haha! How pathetic, if Meta stooped so low. At least I'm not gullible enough to fall for that. Ding! Oh, a notification about that 4,984 page argument I'm having with that definitely real, flesh and blood, human person over Meta's influence on the Fediverse. They make some good points, but I'm Ride or Die with my Purple Pachyderm.
Several months later...
It's Splorkcon! (They changed the name from Threadscon.) Back is the special section, just for Matodoms! Wait, what's a Matodom? "Oh, oops," the Meta rep chuckles dismissively. "Our bad." Your badges get you into and Mastodon section. There's free watered down Crystal Light and a shallow foam pit. Well, that was a downgrade. But, the Meta rep said it was an oversight. You find out the event coordinator came down with a nasty case of missing lung syndrome. You should try to be understanding. They're people, too. I'm sure there's a good reason none of the 1.4 billion employees couldn't take up the mantle. Besides, you doubt you could lose the support of ALL the jilted con-goers to a ton of swag and giveaways.
A few months later...
You start to notice Mastodon slowing down... Meta doesn't have to worry about their data budget like Captain Spanky of the USS Toke and Joke (your home instance). Meta's transfers have gotten a bit... verbose... with their contributions to the codebase. You could set up your own instance of pure Mastodon for the community. You know, for the health of the network, because you sure as shit aren't going to use a non-Splorking instance. (Also, the plugin you use to cross post between the two instances broke 3 weeks ago and you didn't notice.)
A few months later...
Good news, everyone! Meta's going to donate $1,000,000 to the Mastodon Consortium over the next 2 years! See, I told you that whole Splorkcon thing was an honest mistake. Hey, is it just me, or is Mastodon really, really getting slow?
You get curious. I mean, do you even know what you're protesting anymore? It would be irresponsible for you to NOT to explore Threads more. You know. To see why people use it; for competitive intelligence. Let's see if that Splorkified app is slo.... oh wow. It's very speedy. Maybe I'll use it a little more. After all, it's still supporting my beloved (mostly) open sourced protocol, even if it is Meta's app. I'll make my icon the Mastodon logo and try to minimize my use of the splorking feature. That will matter.
A few months later...
Even more good news! Meta's going to allow any instance to join their high speed interconnect. They'll even pay you $0.0005 for each petabyte you transfer. No obligations, cancel anytime, if you don't like it, you can return it within 30 days for a full refund, no questions asked. In return, they only want us to allow them to add a teensy tiny advertisement to each post. Nothing fancy, no images or animations. Hell, you could probably block it with a single line of CSS. You're suspicious, but ultimately conclude it's a reasonable request. They DO have to make SOME money to justify all the help they're giving us.
A few months later...
Meta flips another switch. They announce, "You can now feel assured that your voice is heard even louder, thanks to Weavle. Weavle leverages the power of the Fediverse to connect you with others discussing your favorite topics! It synergizes across all Meta's apps to bring you a complete experience." Translation: You're now autosubscribed to all the users on every instance within Meta's instance empire because your aunt and 2nd cousin liked getting in political debates about Joe Biden's left sock. In comes the flood of engageme... I mean, conversations. However this happened, it caused a bunch of chaos with no simple solution. Well, except THAT.
The Mastodonians start to chatter about how they'll address the Meta problem. Once they get through the told-ya-sos, finger pointing , and copy-pasting the wall of text you're currently reading, they start to defederate Meta instances. When will then be now? Soon.
Not everyone follows. Admins of high population instances would lose access to the high speed network if they leave (that was considered a solved problem, so no one really concentrated on an open solution). Some users cultivated followings of thousands of definitely real, non-bot, Turing Test passing if grading on a curve, human people. They can't leave their community. How would they find out about RAIDDDD Shadow Leg... um, they have sponsors. Go with the nerds, they get $2. Go with Meta, they get $15. The difference in platforms to them are Splorking and the color of the icon.
All your contacts are scattered, 75% still not fully understanding what a 'browser' is, let alone a federation. They just know they're cut off from some of their friends. Splork isn't working because of something those "evil hackers" did. At least Meta released a new Splork filter that lets you sing a duet of "Hurt" with an AR cartoon stalk of broccoli. You start to explain to your contacts how they can set up their own instance. 30 minutes in, they ask, "So, do I have to turn the computer on, or...?"
A few months later...
Fuck it! You knew Meta couldn't be trusted! Time to refocus on your instance. Be the change you want to see in the world.
You tell your family to join your instance and they do. Excellent! "So, how do we Skrank again?" "You mean Splork?" Yeah, that's it." Ruh roh! That's not a Mastodon feature. You can install the Splorktastic Upgrade Package, but then the Mastodon folks will defederate from you. Oh, and your instance users are piiiiiissed that a whole bunch of shit changed when they abandoned their old accounts. Important things, like the button on the right is now on the left. They are now skeptical of your advice on the topic. You're too techy. They want something simple and return to Threads. You resolve to be that one weird family member/friend that's difficult to get ahold of. This is a win. You were even able to resist the siren's call of the cartoon broccoli. Fight the power!
Maybe you can win one of those 20,000 different promo contests and giveaways for Splork users. You could show your support by donating the winnings to Mastodon! Surely that's effective, and not like trying to stop a bulldozer by throwing a gummy bear at it. In fact, you get 1,000 other Mastodonians to pledge their gummy bears, I mean contest prizes. (None of you end up winning.)
At the same time as all of the above...
The Mastodon developers are having a little trouble. Apparently, 50 core devs working 12 hrs/day solely on Mastodon can't keep up with the 2,000 hand selected specialists working on Meta's fork. Who would have thought Mastodon would need more than the $95,000/yr they currently have. Why that's a whole... 0.0000136% of Meta's value. If you really zoom in, you see that's a whopping 0.0033% of their Q1 2023 revenue. The $1,000,000 donation? No one knows exactly, but it appears on the books as "expenses". Coincidentally, everyone at the Mastodon Consortium is sporting custom, limited edition Heelys. Nobody else has time or the knowledge to deal with the massive codebase.
Finally, it all comes to a head. Meta experiences the most devastating data breach in history and videos of the top brass leak, letting the world catch a glimpse at their weekly "throw puppies into a pit of lemon juice coated spikes" meetings. You know what that means... big new product press release time!
"Regrettably, we are going to have to end our partnership with Mastodon. They've been great, but we see so much potential in the Fediverse that we've carved out our own little corner, based on our vision. We've been innovating too fast for even the passionate and capable open source community to keep up and we wish them the best in this new chapter of their Fediverse. Don't worry - we'll try to keep the confusion to a minimum. We even have a name for our new virtual space. We'd like to show you today... our Metaverse"
Wait, did he just say Metaverse? (Yes.) I thought that was a VR thing? (It was. No one bought it.) Well, clearly this was the plan all along. (It wasn't.) I have renewed confidence in Meta. (You shouldn't.) Give them more money. (You will.)
In the end, only a handful of people knew the game plan. Everyone else worked with the best of intentions. Maybe there were a few false starts, mini controversies, or sacrificial firings. It doesn't really matter.
Mastodon sticks around for a while with 0.000011% of the "Fediverse" users. Good! You got rid of the riff raff. If the codebase was fucked beyond recognition, things will start to break, security issues will increase, and it'll be a fondly remembered footnote within a year. If the codebase can be cleaned up or rolled back, you could Weekend at Bernie's this shit forever. Every feature suggestion will get shot down for fear it resembles Threads too much, or because it leaves the "platform" (25 people and 7 bots.) vulnerable to more Meta instigating. No one wants to be the one to take Old Yeller behind the barn because everyone's egos, memories, and trauma are tied to it.
Years pass. Your Mastodon instance is going strong. You're talking to a colleague and they mention a Threads post. You tell them you didn't see it because you use Mastodon. "Isn't that, like, the super old version of Threads?" You say, "Yes..." but stop before going into the summary you've recited 1000 times. This person doesn't care. A social network is neither with only one user.
I mean, all this MIGHT happen. I could be totally wrong. (I'm not.)
