For the most part, Threads content just wouldn't appear on Lemmy at all. It's like how you can't see Mastodon users' timelines on Lemmy. e.g. Jeri Ryan from Star Trek is on mastodon.world, but you can't read her blog from Lemmy because it just doesn't display microblog content, only stuff that's sorted into groups (communities).
The one exception is that Jeri Ryan can track down the equivalent group on her Mastodon instance and "microblog" directly into the group. Mastodon has some hacky tweaks to do things like reading the first sentence as a heading, the second line as a URL, and the third line as the post body, so if you're especially dedicated you can post to Lemmy from Mastodon. If Threads cares enough, they could add similar functionality to Threads to make it technically possible to post to Lemmy as long as you try hard enough, but just regular people's blog posts on Threads won't display on Lemmy at all.
Thanks, I appreciate it! It took a stupidly long time. :V
On some level, it's probably not that important that people understand all this stuff, but I think the most dangerous thing is people believing that their data will be protected if Threads gets defederated. Any other confusion is basically harmless, but that's the one thing where people have a false sense of security, because Meta has exactly the same access to your data whether or not they get defederated.
There are literally, not exaggerating, over one billion Instagram accounts in existence. It's self-evidently not the case that they have just silently registered everybody a Threads account and are counting those numbers.
Meta is categorically evil, but the pretty obvious gain from federation is the same as it is federating with anything else: content. Threads has people posting on it, some of those people say interesting things ... the end.
That's not to say that outweighs the downsides, like some of that content will also undoubtedly be hateful bigoted trash, and the moderation load of suddenly dealing with an order of magnitude more posts will be a huge strain on fediverse admins who choose to federate, but there's undeniably something to gain.
Definitely. Meta is studiously only sharing the number of accounts registered. We have no idea how many of those are active. If we go with the old 1-9-90 rule, only about 10 million of those 100 million will become active users. Although, the rule obviously isn't a universal constant. On the fediverse, for example, it's closer to ⅓ of registered users that are active.
You already got a solution to this, but an alternative mechanism for people who use uBlock Origin is to add this filter to your custom list:
kbin.social##^style
That assumes you're on kbin.social, obviously substitute in your home kbin instance.
This is untrue. Threads accounts are reserved for the matching Instagram user, but those users have to actually choose for that account to be opened. If all Instagram accounts were auto-converted to Threads accounts there'd be over 1 billion Threads accounts. The 100 million Threads users are all people who have specifically opted to have a Threads account.
In fairness, I think we might already be the rest who don't matter. Threads has just passed 100 million users in like three days. The entire fediverse, in about ten years (it's tough to pin down an exact start date because "When did it become the fediverse?"), has accrued around 12 million users, of which less than 4 million are active. There's any number of things Meta might want, but I don't think greater access to 4 million geeks is at the top of their list.
I do think the embrace, extend, extinguish concerns have some merit. Meta isn't threatened by the fediverse now, but maybe they do want to kill it before it becomes a problem. In the short term, though, we're not overtaking Threads. Personally, I think another plausible theory is that Threads is using ActivityPub to demonstrate that they're not running a monopoly or gatekeeping control of social media (which the EU's new Digital Markets Act now regulates) by pointing to the fediverse--which will soon also include direct competitors Tumblr--and saying "See, we're all on equal footing! We don't control social media! Look over there at those 4 million geeks and whatever number of Tumblr users."
It comes from Fortune, they can't conceive of something that's not a business.
Hard to tell. It's been in decline since January though, so some of it is just Twitter being a place people want to be less and less.
Here's the graph, as posted by CloudFlare CEO Matthew Prince:
If nobody has ever subscribed to a foreign instance's community/magazine before, it won't show up on your home instance. Currently, the best way to pull it into your local instance is to copy its web address on the other site into your local search.
e.g. If you wanted to pull in kbin.social's AskKbin from lemmy.world you'd find its URL, https://kbin.social/m/AskKbin, and paste that address into your home instance's search box. As long as somebody has done this once, AskKbin will now show up in regular community lists, searches, etc.
Get us a photo of the popsicle stick skyscraper before it burns down.
Lemmy communities are "groups" in ActivityPub parlance, and groups do exist on the microblogging platforms. Using Mastodon as an example for now, a Masto user could find the group equivalent to a Lemmy community and make a post and/or comment there and it would show up on lemmy.world and anybody else who federates with that Masto instance. In reality, the groups experience is kind of terrible and a poor interface to these thread-style communities, and you lose all kinds of features like the recency/score sorting algorithm, the ability to downvote things, etc.
It would take a true masochist to post to lemmy.world from Mastodon, which is why you almost never see it. I've seen one Mastodon user in my time on the threadiverse so far. Most people who are already on the microblogging side of the fediverse have just chosen to register a separate account on a threadiverse instance so they can have an actual usable interface rather than stuffing a link aggregator through a blog-shaped hole.
Groups don't even exist on Threads currently. Maybe they will by the time they implement ActivityPub, but they may not consider that to be a core goal as a microblogging, Twitter-style platform which has no obvious use for them. This would currently make Threads an even worse interface to the threadiverse (kind of ironic) than Mastodon, which I can't stress enough is already awful. You would just have to search for individual posts by browsing somewhere like lemmy.world directly, copying and pasting the URLs into the Threads app or web site to populate the conversation in their interface in order to reply to the posts and comments there.
In short, using Lemmy via Threads is probably going to be such a nightmare that only turbo-nerds will try to do it, and turbo-nerds are more likely to realize "This is awful and I should just go join Lemmy or kbin or something," than persist with that hassle long-term. Now, kbin users have more justification to be concerned about how Threads will impact their communities, because kbin supports microblogging directly--in corporate terms, it's like if Reddit and Twitter combined into one site that you could tab between on the fly. This means kbin users will be more likely to see Threads content and vice versa.
The other problem here is that I don't think a lot of people actually know how defederation works. There's lots of takes like "I don't want Meta to get my data, so we have to defederate." But defederating stops you from receiving their content, not the other way around. Once Threads actually is federating, defederating it will stop people seeing posts from Threads users. That has its own merits, but it doesn't protect your data in any way. If you don't want corporate entities to access your online posts, either send them via some private end-to-end encrypted system where only you and the direct recipients can see them, or don't post them online at all. The Internet is on the Internet.
Now, a bit more of an explanation on what defederation is: while the decentralized nature complicates things (since different servers will have different defederation lists), defederation is closer to a Reddit shadow-ban than whatever it is people are imagining. If literally everybody defederated Meta/Threads, they would still see our content, but from their (Threads users') perspective, it would just seem like we're all giving them the silent treatment, because we never respond to their posts or comments.
Yeah, they can vote and reply and all of that and others who remain federated will see their interactions, but you or any other server who defederates them won't.
Yeah, my understanding is that defederation prevents any incoming communication, so you won't see any posts or comments that come from lemmy.bullshit, however users from lemmy.bullshit will still see all of your comments and posts from lemmy.world unless they choose to defederate you back.
> > > I'm always seeing "first CD-ROM game" citations that are totally inconsistent, or which cite games like Myst, so I decided to put together a timeline of all the candidates - and ended up calling into question the point of "firsts" lists in the first place. > >
Fun article on retro CD-ROM games put together by @misty
Get a unique look at how controllers evolved into intricate devices, transforming games into immersive tactile adventures. Join our virtual CT scan journey through Xbox, PS5, and SNES gamepads.
> > > Get a unique look at how controllers evolved into intricate devices, transforming games into immersive tactile adventures. Join our virtual CT scan journey through Xbox, PS5, and SNES gamepads. > >
While you could achieve a lot of this with my new invention the screwdriver (patent pending), these scans look pretty cool and you can also non-destructively inspect parts like the batteries, which it would otherwise be unwise to disassemble and reassemble.
Before I get started, I want to be clear that this has been my first time ever doing pixel art. I'm more interested in talking about the tech than my (lack of) artistic skill.
Background
Everybody knows QR codes; even if they didn't before 2020, they do now. But for an extremely quick rundown, they're just a bunch of data encoded using pixels as binary 0s and 1s, with some extra stuff used for orientation and tracking so that scanners know how to find the code in a larger image, etc. They come in many different resolutions, from 21x21 all the way up to 177x177, with a total of 40 available code sizes. They mostly look like a square of random pixels.
No doubt, you've seen custom QR codes before; usually somebody slapping their company logo in the middle or something. The way this works is that QR codes set aside some of their pixels for error-correction data. If the code is damaged in some way (such as somebody slapping their company logo in the middle), the error correction data allows your scanner app to reconstruct the damaged part of the code so that it can scan anyway. It's fine, I'm not criticizing anybody who does that, it's just that it grosses me out super hard to deliberately corrupt some data and be like "Robot will get it." Maybe there's a better way?
Each size of QR code has a set capacity in terms of how many bytes of data it can carry. Most QR codes are not completely filling their capacity: for example, the smallest QR code (version 1) can fit at most 25 characters of text, but if you e.g. make a QR code that links to https://kbin.pub/, you've only used 17 characters. Even if you increase the error correction level, you still have space for 20 characters, which leaves three characters worth of data that are empty. To cope with this situation, QR codes need to be able to fill any free space with a bit of "meaningless" padding data.
Going by the QR code specification, this padding data is technically supposed to have a specific repeating sequence, but in practice, QR code scanner tools don't actually care what the padding values are--after all, it's just padding. That means we're finally getting to the fun part: what if we could arrange that padding in such a way that it forms a small piece of 1-bit pixel art? The result would be a customized QR code which has all of its data intact, without having to rely on error-correction like some feral animal.
Setup
@revk has created an app, simply called QR, which can perform this function, and can be built and operated from the Linux console. Personally, my Linux proficiency ranks at "I have used Linux before, no further questions please." Mostly, I just run Windows, although my Wii U runs Linux. That said, if you're a pleb like me, modern Windows (10+) makes it pretty easy to use a virtual Linux machine. You can open the Microsoft Store and download a Linux distro to run like a Windows app. Personally, I use Debian, but these instructions should also work for any of the Ubuntu flavors. If you're already a Linux user, you probably know what you're doing. On Mac, I have no idea.
First, you'll need to set up your Linux user and passwords, which I won't cover here. After that, the following lines can be typed or pasted into the Linux console. As always, don't trust some Internet jerk telling you to paste things into the console. Except this once. Note that the line cd /mnt/c assumes that the Windows C:\ drive is where you want to do your QR code work. You can change the path as appropriate to your needs, e.g. in real life, I used cd /mnt/c/Coding/revk. Note that you can't cd to a directory without creating it first, but I'm not explaining all of that here. Let's go already!
First up, install the dependencies:
``` sudo apt-get update && sudo apt-get install build-essential git libpopt-dev libz-dev
```
Then, enter the super-user password you set up earlier. Eventually, you'll get a prompt like this:
``` Need to get 101 MB of archives. After this operation, 361 MB of additional disk space will be used. Do you want to continue? [Y/n]
```
At this point, press Enter/Return to continue, or don't if you've changed your mind. It will probably take a few minutes to complete these package installs, then you can go back to entering these commands:
``` cd /mnt/c git clone --recurse-submodules https://github.com/revk/QR.git cd QR make
```
If everything has gone to plan, you now have a Linux executable called qr in your C:\QR directory (or wherever you chose instead). If you like, you can move that executable to somewhere more convenient to you, do what you want. As a quick test, let's make a sample QR code by typing/pasting something like this into the console. Make sure you include the ./ on the front.
``` ./qr "Hello world!"
```
Ideally, this will have printed a QR code directly into the Linux console which looks something like this:
``` █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ ████ █ █ ████ ████ █████ ██ █ ██ █████ ████ ████ █ █ ██ ███ █ █ ████ ████ █ █ ██ ██ █ █ ████ ████ █ █ ███ █ █ █ █ ████ ████ █████ ████ █ █████ ████ ████ █ █ █ █ ████ ████████████ ████████████ ████ █ █ ██ █ █ █████ ████ ██████ ██ █ ████ ███ ██████ ████ █ ██ ██ ██ ████ ████ ████ ███ █ █ ██ ██████ █████ █ █ ██ █████ █ █████ ████████████ ███ █ ████ ████ ██ █ █ █ ██████ ████ █████ ███ █ █ ████ ████ █ █ █ █ ██ █ █ █████ ████ █ █ █ █ ██████████ ████ █ █ ███ ████ ████ █████ █ █ █ ████ ████ █ ██ ██████████ █████████████████████████████ █████████████████████████████ █████████████████████████████ █████████████████████████████
```
If not, I guess start regretting you ever read this thread.
Example
Now that you have the tool set up, it's time to start making pixel art for it. You enter the padding as plain text, like kind of janky ASCII art. You can pass it in as a console argument directly, but I find it easier to do it using a text file. For example, here's a text file I used to make one of my QR codes. I saved this file to the same folder as the qr executable for ease-of-access. For reference, Xs are black pixels, .s are white pixels, and (spaces) mean for the tool to handle filling those padding areas. Note that RevK's tool expects this file to have Unix line endings (LF), not Windows CRLF. Windows line endings are treated as black pixels, so they will interfere with your art.
mastodon.txt
``` .............. ................ ....XXXXXXXXXX.... ...XXXXXXXXXXXX... ..XXX...XX...XXX.. ..XX..........XX.. ..XX..XX..XX..XX.. ..XX..XX..XX..XX.. ..XX..XX..XX..XX.. ..XX..XXXXXX..XX.. ..XX..XXXXXX..XX.. ..XXXXXXXXXXXXX... ...XXXXXXXXXXX.... ...XXXX.......... ...XXXXXXXX.... .....XXXXXX.. ............ ..........
```
Then, you can create your QR code with a command like this:
``` ./qr -v 5 --mm=4 --random https://joinmastodon.org --png --right --overlay=@mastodon.txt --outfile=mastodon-qr.png
```
To briefly explain these arguments
-v 5: use a QR code version (size) of 5 (37x37 pixels)--mm=4: upscale the result 4x--random: fill any "unused" padding with random datahttps://joinmastodon.org: the payload when you scan the code--png: save the file as a PNG--right: rotate the code to the right--overlay=@mastodon.txt: use the padding layout stored inmastodon.txt--outfile=mastodon-qr.png: save the file asmastodon-qr.png
You can get a full list of the possible arguments with the following:
``` ./qr -?
```
Canvas sizes
An extremely useful argument to use when figuring out your canvas size is to replace --png with --png-colour. This will output your QR code overlaid with colors to indicate which areas are data (blue), padding (green) and red (error correction). Also remember that depending on the orientation of your artwork, you may want to change the code rotation with --up, --down, --left or --right.
The size of the padding area will vary based on a) the length of your payload and b) the code version (1-40). Try to keep your payloads short, and use a QR version of about 5 (37x37 pixels). If you don't set a code version manually, the tool will generate as small a code as possible for your payload, which is not conducive to pixel art. In my experience, version 5 is the ideal compromise of canvas size and code readability. For reasonably short URLs like a bare domain or e.g. link to a social media profile, a version 5 code should net you at least a 16x16 pixel area for your pixel art to inhabit. Version 6 is larger (total size of 41x41 pixels), but the padding is intermingled with the encoded data, so it's not really going to give you one contiguous canvas to work with, making it sort of break-even against version 5 but (very) slightly harder to scan. You might be able to find a use for it, though.
Version 7 and above place alignment blocks (3x3 blocks of hardcoded squares) all over the code to make it easier for scanners to orient themselves, but these are going to infringe on your canvas as well. If you really want to push out the boat, you can use a massive version 40 code to get a giant canvas, but nobody wants to scan those awful hogging messes in real life, and you'll basically be refusing people who use budget smartphones, etc. because they can't reliably focus and resolve such large codes with their cheaper camera sensors. Plus, you'll have like 30 alignment blocks to either work around or try to incorporate into your art.
Color
All right, earlier in the thread, I said we'd be creating 1-bit pixel art, but in practice I've hideously violated that restriction in all but one of my examples (the Matrix logo). While you can set your light and dark colors in RevK's tool, this kind of color fudging is not something it supports or intends; I've just gone in and hand-painted in some extra color to try to make things pop a bit more. I've basically tried to keep sort of within a luminance range to make sure the colors still read as "black" and "white" even though they sometimes vary by a lot in hue (e.g. the Jack-o-Lantern with its yellows, oranges and purples).
Credits
Obviously, the bulk of the credit here belongs to @revk for developing the tool I used here.
I will also credit Igara Studio for the Aseprite logo used in one of my examples, and Brandon James Greer for his monkey avatar in another (I will also note that both codes when scanned lead to the aforementioned links). Lastly, the MacPaint icon is a modification of a graphic included in legacy versions of Apple's MacPaint for Classic Mac computers.
PS
Hi, threadiverse! This was originally posted to kbin.social while federation was down. Apologies to kbeans who already saw it, but I figured it was worth reposting now that we're all connected again.
