00:00:55<fireonlive>me to chatgpt: make a depressing story
00:01:02<fireonlive>chatgpt to me: here's something but the ending is happy
00:01:09<fireonlive>:|
00:02:58<fireonlive>speaking of sad, are people able to reach https://dl.fireon.live/irc/e4d2d1cb79ad4206/test.gif via IPv6?
00:25:53<nstrom|m>I can
00:27:46riku quits [Quit: WeeChat 4.2.1]
00:28:40<fireonlive>thanks!
00:33:41riku (riku) joins
00:34:05<fireonlive>"Hold on there: WPA3 connections fail after 11 hours" https://rachelbythebay.com/w/2024/01/24/fail/ https://news.ycombinator.com/item?id=39135487
00:34:13<fireonlive>>My conclusion: this entire ecosystem is deeply cursed.
00:34:19<fireonlive>agreed lol
00:39:11missaustraliana joins
00:49:45jasons (jasons) joins
00:58:01missaustraliana quits [Client Quit]
01:48:47jasons quits [Ping timeout: 272 seconds]
02:07:44missaustraliana joins
02:08:15missaustraliana quits [Client Quit]
02:11:06<fireonlive>https://charlottebuff.com/unicode/misc/rejected-emoji-proposals/
02:50:34<fireonlive>-+rss- Nitter Shutting Down: https://nitter.d420.de https://news.ycombinator.com/item?id=39161194
02:50:48<fireonlive>one instance has thrown in the towel (with graphs)
02:50:53<fireonlive>s/graphs/graph/
02:51:38jasons (jasons) joins
03:00:46<thuban>was there a fork that logged in with real account credentials? or is it just privacydev's nsfw workaround
03:52:55jasons quits [Ping timeout: 272 seconds]
04:11:21<fireonlive>hmm I can’t recall
04:12:02<fireonlive>https://dl.fireon.live/irc/504cc8cf200a65cd/colour-tv.mp4
04:12:19<fireonlive>neat
04:14:13BlueMaxima quits [Read error: Connection reset by peer]
04:53:52<nicolas17>I'm making some nice new findings for https://theapplewiki.com/wiki/Codenames :)
04:56:23jasons (jasons) joins
05:05:30HackMii quits [Ping timeout: 255 seconds]
05:05:44<fireonlive>https://www.theverge.com/2024/1/26/24052067/mozilla-apple-ios-browser-rules-firefox
05:05:44lukash98 joins
05:06:37HackMii (hacktheplanet) joins
05:12:15HackMii quits [Remote host closed the connection]
05:12:35HackMii (hacktheplanet) joins
05:23:25HackMii quits [Remote host closed the connection]
05:24:58lukash98 quits [Client Quit]
05:25:02HackMii (hacktheplanet) joins
05:34:07HackMii quits [Remote host closed the connection]
05:34:28HackMii (hacktheplanet) joins
05:34:52lukash98 joins
05:39:21monoxane quits [Quit: Ping timeout (120 seconds)]
05:39:34monoxane (monoxane) joins
05:53:15jasons quits [Ping timeout: 272 seconds]
06:01:24DogsRNice quits [Read error: Connection reset by peer]
06:56:34jasons (jasons) joins
07:05:59@arkiver quits [Remote host closed the connection]
07:06:15arkiver (arkiver) joins
07:06:15@ChanServ sets mode: +o arkiver
07:06:16Chris5010 quits [Remote host closed the connection]
07:06:34immibis quits [Remote host closed the connection]
07:07:34immibis joins
07:26:31<fireonlive>pls PM me your passwords for safe keeping
07:26:38<fireonlive>tks ~ fol
07:45:51dave (dave) joins
07:56:20jasons quits [Ping timeout: 240 seconds]
09:00:20jasons (jasons) joins
09:56:50jasons quits [Ping timeout: 240 seconds]
10:00:03Bleo18260 quits [Client Quit]
10:01:22Bleo18260 joins
10:09:47<Exorcism>:3
10:09:52Exorcism uploaded an image: (47KiB) < https://matrix.hackint.org/_matrix/media/v3/download/mint.lgbt/A7BcO0z8zSD9QMziV6JfG7sfrgoBDgHZ/image.png >
10:10:18<fireonlive>:o
10:14:13<Exorcism>if someone is interested https://escargot.chat/
11:00:22jasons (jasons) joins
11:06:20ScenarioPlanet quits [Ping timeout: 240 seconds]
11:06:20Pedrosso quits [Ping timeout: 240 seconds]
11:06:20TheTechRobo quits [Ping timeout: 240 seconds]
11:09:21Pedrosso joins
11:09:53ScenarioPlanet (ScenarioPlanet) joins
11:09:54TheTechRobo (TheTechRobo) joins
11:29:50TheTechRobo quits [Ping timeout: 240 seconds]
11:29:50ScenarioPlanet quits [Ping timeout: 240 seconds]
11:29:50Pedrosso quits [Ping timeout: 240 seconds]
11:33:16Pedrosso joins
11:33:17ScenarioPlanet (ScenarioPlanet) joins
11:33:27TheTechRobo (TheTechRobo) joins
11:54:20Pedrosso quits [Ping timeout: 240 seconds]
11:54:20TheTechRobo quits [Ping timeout: 240 seconds]
11:55:48ScenarioPlanet quits [Client Quit]
11:56:17Pedrosso joins
11:56:22ScenarioPlanet (ScenarioPlanet) joins
11:56:41TheTechRobo (TheTechRobo) joins
11:58:41jasons quits [Ping timeout: 272 seconds]
12:45:23jacksonchen666 (jacksonchen666) joins
12:49:13jacksonchen666 quits [Remote host closed the connection]
12:49:44jacksonchen666 (jacksonchen666) joins
13:00:20Arcorann quits [Ping timeout: 240 seconds]
13:01:14jacksonchen666 quits [Client Quit]
13:01:52jasons (jasons) joins
13:41:24<f_>:o
13:43:03<f_>Exorcism: what does this use? XMPP?
13:59:39jasons quits [Ping timeout: 272 seconds]
14:10:57qwertyasdfuiopghjkl quits [Remote host closed the connection]
14:17:35<joepie91|m>f_: it uses the old MSN protocol
14:17:47<f_>Sure
14:17:50<joepie91|m>Escargot is a protocol-compatible MSN server implementation
14:23:58qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
15:02:30jasons (jasons) joins
17:07:07f_ quits [Ping timeout: 272 seconds]
17:18:41f_ (funderscore) joins
17:42:23<SootBector>nitter news :( what's a good channel to follow discussion on that? I see comments that this fork works with credentials for a standard account https://github.com/PrivacyDevel/nitter https://nitter.privacydev.net/
17:48:50jasons quits [Ping timeout: 240 seconds]
17:50:43<Exorcism><joepie91|m> "Escargot is a protocol-compatibl..." <- Exactly :3
17:53:31<SootBector>neat, should work with Trillian then
17:58:24SootBector reads nitter discussion in -bs
18:17:29sec^nd quits [Remote host closed the connection]
18:17:53sec^nd (second) joins
18:28:48<Barto>:-)
18:29:16<@JAA>> Nitter Shutting Down
18:29:32<@JAA>Person 18429 who doesn't understand that it's one instance of Nitter, not Nitter in general.
18:31:15<SootBector>how much effort was it to get running Barto ?
18:31:35<SootBector>I am tempted to try the account-using fork
18:32:01<SootBector>wondering if the original has any gotchas to be aware of first
18:43:25<hexa->https://github.com/zedeus/nitter/issues/1155#issuecomment-1913361757
18:52:46jasons (jasons) joins
19:04:02lizardexile joins
19:04:52<fireonlive>no
19:04:56<fireonlive>:(
19:04:58<SootBector>no
19:05:14<SootBector>how's your weekend fireonlive ?
19:05:55<fireonlive>it’s a weekend 😅
19:05:59<fireonlive>how’s yours?
19:07:10<fireonlive>discmaster: experimental archive.org backup site, who knew! (https://old.reddit.com/r/opendirectories/comments/1ad8avx/archiveorg_experimental_backup_site/)
19:14:42<SootBector>full of food and some good music on, it's OK :)
19:15:02<SootBector>have you run a nitter instance?
19:16:57<fireonlive>:)
19:17:06<fireonlive>not personally no, just a consumer of them
19:17:17<fireonlive>i meant to but never got around to it
19:18:35<SootBector>I guess your bot doesn't pull anything direct from twitter?
19:41:26<Barto>SootBector: effort was low, guest token management is kinda the most finicky subject. I plan to document what we did in the wiki once everything is gone to shit
19:45:46<Barto>SootBector: also, make sure you're following any change in the git code, as they're often following changes to fix breakages
19:46:00<SootBector>thanks, I'll let you know if I try the fork
19:46:12<Barto>SootBector: example: https://github.com/zedeus/nitter/commit/52db03b73ad5f83f67c83ab197ae3b20a2523d39
19:47:36<SootBector>I'm mainly using nitter to search for a handful of keywords once a day
19:51:20jasons quits [Ping timeout: 240 seconds]
19:55:33<fireonlive>SootBector: ahh nah, that’s IFTTT
19:56:15<fireonlive>they pay the musk so it should be more reliable over time
19:56:53<SootBector>can you run searches through that?
19:58:13<fireonlive>it’ll only send you new results up to 30 tweets every time it decides it’s time to run
19:58:57<SootBector>that'd be enough for me if I could have it run every few hours
19:59:34<fireonlive>atm a from:x or from:y -filter:replies kinda thing is being users for #archiveteam-twitter (not sure if it’s “filter” but something like that)
19:59:56<fireonlive>can’t schedule it yourself but it seems to run often enough
20:00:09<fireonlive>being used*
20:02:49<SootBector>is that on a paid plan?
20:07:41<fireonlive>indeed
20:08:04<fireonlive>they limited it i guess due to having to pay twitter the stupid high fees
20:13:39lizardexile quits [Client Quit]
20:27:06<SootBector>where's the petition to have everyone move/crosspost to mastodon
20:28:08<SootBector>I don't believe me or my eighty-seven very similar looking siblings have signed it
20:39:25<joepie91|m>I think that petition is called a 'sign-up form' :p
20:41:20<fireonlive>:p
20:41:59<fireonlive>there’s a very annoying nerdfight in the nitter issue about such atm
20:43:42<SootBector>do I need to make a twitter account so I can then leave?
20:44:01<SootBector>yeah, someone give me mod access to clean up the thread
20:50:00<joepie91|m>more seriously: treating mastodon as a 1:1 drop-in twitter replacement will end in tears
20:50:07<joepie91|m>for everyone involved
20:50:48<joepie91|m>it's its own thing and people should be aware of that :)
20:54:56jasons (jasons) joins
20:56:22<fireonlive>A wholesale move would not go very well yeah
21:00:38BlueMaxima joins
21:03:14<fireonlive>matt blaze (some of you might know him) f.e. kept bumping into walls
21:04:04<fireonlive>especially with labeling posts, ultimately telling people to just block him when he wouldn’t label things such as monotone photography with a content warning
21:04:21<fireonlive>it’s a bit of a different world there than just twitter i suppose
21:06:54<joepie91|m>having seen a lot of these labelling-related conflicts go down from up close, I am skeptical that it was about 'monotone photography' tbh, but other than that, yeah, different culture
21:08:17<SootBector>content warning?
21:08:37<joepie91|m>(it's a bit of a pattern that people who are miffed about being asked to label anything that they personally wouldn't object to, start hyperbolizing it to something that to them seems equally absurd but that would never actually be asked, hence why I am skeptical about the topic mentioned)
21:09:00<SootBector>ah
21:09:23<joepie91|m>but yeah, CWs are the same thing, though I think I prefer the 'labelling' terminology actually, it's closer to how the feature is used
21:12:21DogsRNice joins
21:14:41<fireonlive>ah, looking in to it again i think it was just one person™ https://federate.social/@mattblaze/110255584114823369
21:14:51<fireonlive>i missed that back then
21:15:46atphoenix quits [Remote host closed the connection]
21:16:29atphoenix (atphoenix) joins
21:16:43<fireonlive>something about PMs not being private as well? idk https://federate.social/@mattblaze/111474140803874176
21:16:55<fireonlive>i haven't been on it much i guess :/
21:18:35<joepie91|m>having a quick look at the person in question, certainly getting some sketchy vibes from them, though I'd like to see the context for that request
21:19:02<joepie91|m>re: the PMs, that's likely referring to one of two things
21:20:00<joepie91|m>either a) the DMs are unencrypted (yes, they are, like on ~every other social network, and it's always very suspicious when people try to bring this up for mastodon and only mastodon specifically), or b) they are inlined in the rest of the message feed in the UI, making it non-obvious that they are private (this is a legitimate issue, but also one that nobody except Gargron can do anything about, and Gargron is uh... yeah)
21:20:23<joepie91|m>again I wouldn't mind seeing the context for the toot..
21:21:10<fireonlive>ahh, yeah the unencrypted thing is basically everywhere yeah but the inline thing is interesting
21:21:40<fireonlive>oh right, Gargron the creator
21:21:50<fireonlive>i guess he's not well liked after all then
21:22:02<joepie91|m>not really, no
21:22:39<fireonlive>seems the context is this one: https://federate.social/@mattblaze/111201660656244590
21:22:42<joepie91|m>there's a large amount of Mastodon users who are very frustrated by Gargron refusing to fix issues, which then requires the community to pick up the slack through procedures and conventions, which the community then gets shit for from new (especially ex-twitter) users because it's "not intuitive"
21:22:48<fireonlive>he's also said similar in october too: https://federate.social/@mattblaze/111201660656244590
21:23:01<joepie91|m>without ever asking "okay, but why is this not fixed"
21:23:20<fireonlive>ahh i see :/
21:23:51<fireonlive>sorta just 'has his vision' and doesn't want feedback kinda thing?
21:24:57<fireonlive>i did idly wonder why some of them had a '+glitch' patch/fork/? but i guess that's why
21:24:59<SootBector>tagging others in what you think is a PM, eek
21:25:00<joepie91|m>pretty much yeah
21:25:06<joepie91|m>yep that is exactly why
21:25:10<fireonlive>ahh
21:25:22<joepie91|m>yeah the tagging is likewise a legitimate issue that likewise isn't getting fixed upstream
21:26:19<fireonlive>oops
21:26:23<fireonlive>i linked the same post twice
21:26:39<fireonlive>the one the day before that PM one was https://federate.social/@mattblaze/111468802914900133
21:26:57<fireonlive>"Periodic reminder that the..."
21:27:28<joepie91|m>the thing is, though. I am looking at the replies to that post about private messages, and... people are agreeing?
21:27:29<fireonlive>and hmm yeah annoying upstream won't fix that
21:28:07<fireonlive>i wonder; does 'linking' to a profile i.e. https://example.com/@someone also mention them?
21:28:21<joepie91|m>like, I don't see people "jumping all over him to defend it" at all?
21:29:37<fireonlive>hmm yeah maybe one or two but a lot of agreement
21:29:44<fireonlive>i guess maybe he's one of those people
21:30:10<joepie91|m>like, I don't even see the fosstodon fossbros defending it
21:30:23<joepie91|m>(fosstodon is blocked in a lot of places for good reason)
21:30:38<fireonlive>https://federate.social/@ricketson@kolektiva.social/111471378328505901
21:30:49<fireonlive>ah interesting
21:31:12<fireonlive>defederation is fun too :)
21:31:21<fireonlive>(sometimes very needed)
21:31:43<joepie91|m>that's the november one though
21:31:53<joepie91|m>not the october one
21:32:01<joepie91|m>(that reply)
21:32:14<joepie91|m>the october one is the one I'm looking at
21:33:43<fireonlive>ahh
21:35:41<joepie91|m>yeah, I'm inclined to throw this one on the pile of "many-followers person moves over to mastodon and is unreasonably demanding and/or unreasonably easily angered by the slightest thing that is different from their previous experience", which shouldn't be a dedicated pile, but is
21:36:32<fireonlive>hmm sounds reasonable
21:36:33<joepie91|m>I recently learned that Twitter apparently aggressively filters out replies to high-follower accounts specifically
21:36:39<fireonlive>oh really?
21:36:42<fireonlive>interesting
21:36:47<joepie91|m>which presumably makes the experience divide bigger for popular accounts
21:37:10<joepie91|m>(and it already is pretty big, because fedi is very much not designed for "handful of people with a massive audience)
21:37:38<joepie91|m>there was a pretty good analogy a while ago about this sort of behaviour
21:38:34<joepie91|m>the way that a lot of twitter users, especially clout-chasing ones, treat mastodon: they hear of some nice quaint untouched village somewhere in the mountains and it sounds pretty cool, and they all go there on holiday en masse, and demand all the conveniences and infrastructure of a major hotel chain, from a bunch of villagers who never asked for any of this
21:39:05atphoenix quits [Remote host closed the connection]
21:39:33<joepie91|m>the details are a bit different here (major tech platform instead of major hotel chain, and volunteer-run grassroots community instead of quaint village) but the dynamics are awfully close
21:39:48atphoenix (atphoenix) joins
21:40:08<joepie91|m>like, if you want to holiday in the quaint village, that's fine, but you probably should expect some quirks and bumps along the way
21:40:39<fireonlive>hmm yeah i like that one
21:40:51<fireonlive>much the same with anything new and growing
21:42:13<joepie91|m>yep, especially when it is a community thing
21:43:18<joepie91|m>through that lens, I think a lot (although not all, but a lot) of complaints about mastodon and the fediverse in general boil down to some variant of "there was no 24/7 reception service at the village inn, this is unacceptable"
21:49:11<fireonlive>mm, i really need to use it more and get more familiar
21:49:29<fireonlive>got distracted by a train toilet DoS :) https://www.devever.net/~hl/traintoilet
21:55:43<joepie91|m>> Of course, there is a reason for the separation of the closing and locking functions, but not the opening and unlocking functions: it avoids a Denial of Service attack where someone can just press “close” and then jump out before the door closes.
21:55:50<joepie91|m>oh, is that why it has those bullshit controls
21:55:55jasons quits [Ping timeout: 272 seconds]
21:57:00<joepie91|m>neat trick though
21:57:06<fireonlive>i had wondered! but yeah turns out people are just assholes lol
21:57:12<joepie91|m>(but don't be an asshole and actually do that :p)
21:57:17<fireonlive>:p yeah
21:57:40<joepie91|m>what mostly frustrates me is that whereas older toilet designs could be closed either manually or with a button, with the new ones it's just the button crap
21:57:45<joepie91|m>and it takes forever
21:57:55<fireonlive>>_<
21:57:56<joepie91|m>which is the last thing I want when I urgently need to go to the toilet
21:58:05<fireonlive>indeed!
21:58:27<joepie91|m>I'm just standing there waiting for like 10 seconds for the door to sssslllloooowwwllllyyyy cccllloooossseee
21:59:43<fireonlive>liability thing i wonder
22:25:43<@JAA>What ... do ... you ... call ... a ... three- ... humped ... camel?
22:27:48<@JAA>Yeah, makes sense that it'd be to avoid crushing someone standing in the door or similar.
22:59:06jasons (jasons) joins
23:16:42Arcorann (Arcorann) joins
23:48:59<SootBector>anyone tried https://github.com/vladkens/twscrape for twitter ?
23:53:26<@JAA>Ugh yeah, that thing which pretends to produce snscrape-compatible data but actually doesn't.
23:55:37jasons quits [Ping timeout: 272 seconds]
23:56:03<SootBector>I'm not certain from your snscrape readme if it can or can't do a general search for a word/phrase ?
23:56:14<SootBector>it sounds like not
23:56:25<@JAA>It could in the past, but Elon broke it.
23:56:57<SootBector>thanks for the feature while it was possible
23:57:09<@JAA>I never found the time to implement the token-based stuff Nitter did, and now that's pretty moot, too.
23:58:10<joepie91|m>fireonlive: JAA: I mean, the slow door closing wouldn't be a problem if you weren't *required* to use the damn button
23:58:27<joepie91|m>and they still had a manual close-and-lock mechanism like on older trains
23:58:52<joepie91|m>then the door would only close slowly if you chose to use the button/motor
23:59:14<joepie91|m>well, more accurately: it would be a problem for way less people
23:59:25<@JAA>Yeah
23:59:51<joepie91|m>like, the feature for a button/motor obviously needs to be there, it's just that I see no reason for it to be the exclusive option :p