Notices by p (p@shitposter.club), page 3
-
Embed this notice
p (p@shitposter.club)'s status on Thursday, 14-Mar-2024 03:02:35 JST 
p
@graf @p @coolboymew This is really great shit. (My incoming music queue is a mile long at this point, it's a good problem to have.) -
Embed this notice
p (p@shitposter.club)'s status on Thursday, 14-Mar-2024 02:48:45 JST
p
@a7 *From* FSE? That box is dead, you shouldn't be getting anything from FSE until the new shit is racked up. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 17:32:18 JST
p
@mint @Drand @ashten Well, they allegedly blocked shpposter.club, dobbs.town, and cdrom.tokyo. If there is a reason to be upset with any of those instances, I do not know, but the Masto block brigade tends to not like SPC. Apparently SPC is #10, beating Pieville, Gab, cum.salon, etc.: https://fba.ryona.agency/scoreboard?blocked=50 -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 16:16:41 JST
p
@icedquinn -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 08:03:21 JST
p
@0 @mint @ashten Ah, okay. Just someone that thinks I have signed off on everything that ever passes through a computer I operate and I write this code because I hate some group or another rather than because I love fedi, then they block and make things up, and that reinforces it. Some people are so determined to become retarded that they'll shit on random people just to prove they can't control their bowels.
:dracula: They forgot I'm him. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 07:24:14 JST
p
@mint @ashten
> Who is DDoSing them?
Or is this, like...just a traffic spike getting confused for a DDoS, or maybe an opportunist attempting to "prove" that all of those people that were blocked are all evil hackers? (Or, maybe some Mastodong saw the thread and figured that if something bad happened, it'd get ascribed to the people that were arguing with OP.)
What did the OP say in it? I still don't know what was in there. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 07:15:26 JST
p
@pernia
> why do you hate ipv6?
I named the screenshots of the posts I made about IPv6 "everyone_please_stop_asking_me_why_i_hate_ipv6.png" and "ffs_please_please_stop_asking_me_about_ipv6.png". The reason I named them that was so that, hopefully, people would stop asking me about it, but here we are again.
The notation is ugly and error-prone (for humans as well as machines), we do not need 128 bits (they were allocated because some dicks in the 90s thought that literally every appliance needed an IP address, this was the actual argument), IPv6 has been trying really hard at relevance since the 90s and nobody really wants it, ISPs still aren't ready, private networks still aren't ready (this will have consequences), everything this guy says is correct ( https://apenwarr.ca/log/20170810 and https://tailscale.com/blog/two-internets-both-flakey/ ), and finally, the sales pitch (always delivered by people that refuse to address or acknowledge any of the shortcomings or practical realities), which alternates between utopianism and trying to scare people, is full of lies about how IPv6 solves *everything* (I have heard "adopt our protocol/language/OS/whitespace-conventions and your life will be beautiful forever" before and it is always a lie; in this case, it uncaps a limitation, which is good, but "corrects" some perceived ugliness with worse ugliness) and how IPv4 is going to go away (not in the lifetime of anyone that is here to read this) and how it doesn't matter if you can remember an IP address or not (let alone transcribe one over the phone) and how routing tables (don't even mention BGP) are not already a pain to debug and how their One True Solution is the only conceivable solution. I can rattle that off the top of my head because I have been asked a million times.
IPv6's worst feature has no technical solution, though, and that feature is it's hardline proponents. Very few people talk about IPv6 otherwise; I have only met one or two people on fedi that could discuss it without yelling.
The people pushing it start yelling at you if you say that you don't have a reason to care about IPv6 and will not touch it until you have to. I found this out because I don't have a reason to care about IPv6 and I won't touch it until (or unless) I have to, and I made remarks to that effect. Every time I say something in the vicinity of that, IPv6 partisans start yelling at me, exactly the same way that you expect from people who are in denial about how fundamentally stupid their pet issue is: they've come to perceive apathy as persecution, because gaining any amount of perspective would force them to conclude that it's nothing to get worked up about, and then they'd have no excuse to focus on their pet issue instead of the actual problems they are avoiding by yelling at a stranger on the internet about IPv6, Wayland, loli hentai, hearing a gamer word, not being allowed to say gamer words at their workplace, all of the articles of faith surrounding who goes into which bathroom, Israel and Palestine, Russia and Ukraine, the 'rona, the Holocaust, the Holodomor, whether Hitler did anything evil or everything evil, whether the USSR was real socialism, almost any religious schism. (All fun topics until you run into someone that Cares way too much to have any perspective or a sense of humor about any of it.) You say "I don't care much about that" and they treat it like an attack, because it has caused them pain: if you care and you're on their side then you're an ally and $thing is important, if you care and you hate it then you're an enemy but $thing's importance is still uncontested, but if you really don't care and you say it, then you have put a hairline fracture into the dam that keeps the flood away and have pushed them that much closer to having to cope with their divorce or weird relationship with a parent or shitty job or no job or prior convictions for sexual assault or whatever. So they start trying to fight you and if you get upset then the thing is important and you must have just been lying because you are one of Them, or if you don't then they'll start grasping, they'll proudly announce that you really *are* mad, then declare victory and retreat, anything to keep their thoughts from wandering in the vicinity of how much their life sucks and especially the deepest part of the forbidden zone, the question of how many of the negative results were their own fault and whether or not they might need to fix something.
Anyway, long way of saying I think IPv6 is ugly and I don't like it, but I don't have a reason to care yet and am thoroughly sick of shouty advocates for anything. IPv6 doesn't exist if you ignore it. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 07:13:25 JST
p
@mint @ashten
> they fucking pay for it.
When Cloudfed owns the internet, we'll all pay for it, one way or another.
> DDoS
Who is DDoSing them? -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 07:04:23 JST
p
@mint @ashten Since fedilist has been running for a little over three years, if I was planning something evil, surely I would have gotten around to it by now.
Since I can't see OP, just the subject line that has ended up in other people's posts (maybe woem.men blocks SPC), I guess I'll address it here with the hope that it somehow gets to that admin.
> fedi meta, scraper advisory for admins
It's not a scraper; it doesn't try to get any content, it uses only well-known API endpoints, and it only fetches the stuff that every Misskey instance fetches, for example. It clearly identifies itself in the user-agent and doesn't try to get around it if people reject requests from that UA. It even respects the `discoverable` flag on the admins' profiles. (And it has help text for same: http://demo.fedilist.com/p/discoverable .) There are actual scrapers around, and they are way less friendly and are way less open about what they are doing and why. (Hi, @Drand !) When fediverse.network went down, I wanted something like it, and no one made something like it, so I did. It's never been the highest-priority project, like I mostly add stuff to it when someone asks or when I have a question about something going on in the network.
The point of the project is that it is hopefully useful to admins and people curious about the network, as well as most of fedi. It saves me having to look up who admins are, whether something weird is going on with an instance, it shows the instance description without requiring a bunch of JavaScript, it lists the source code repositories for the instances that report them ( http://demo.fedilist.com/source-code ), it lists the instances where something unusual is going on ( http://demo.fedilist.com/hockeystick ), there are CSVs and RSS feeds for almost every page, you can see the newest instances ( http://demo.fedilist.com/instance/newest ), the front page has fedi-wide statistics, you can point an RSS reader at an instance's status changes page and see when it goes up or down; I use it to monitor instances I use ( http://demo.fedilist.com/instance/recent-changes?host=shitposter.club ) or run ( http://demo.fedilist.com/instance/recent-changes?host=freespeechextremist.com ) so that I can see if there's downtime or if it's my net connection. You can search for instances by name, description, whether they are on Tor or the clearnet, whether registrations are open or closed or invite-only or approval-only.
That has been useful. There are a lot of pieces of software and it can be difficult to figure out what's going on with an instance. If there's a lot of spam coming from it, but you can see that eight hours ago it just had three users and it has open registrations, then probably the admin is asleep and not malicious. We also used it to figure out where the activitypub-troll.cf peers got into the network (sorting the list of instances by peer count, it became obvious when some of them had 100k peers), and that is how we found out that it got Misskey worse than Mastodon, even, and we were able to ping the affected admins (at least the ones that didn't block us). The hockeystick page linked above was created as a response to that, so instances that are acting unusual (relative to their own previous behavior) are highlighted.
There's already fediverse.observer and it's more useful for people that are just joining, so they can find an instance, but the data that's useful to people that are already here is a little different, fediverse.space always looked cool.
The data is all there so that it's open and accessible to anyone using fedi, with the hope that it's useful to people. There's nothing devious going on, it's exactly what it says it is. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 02:50:37 JST
p
@mint @pernia @meowski -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 01:44:18 JST
p
Here's something: you have a blob of application/ld+json (:vomit:) and you want to know what you have.
Let's see if the spec says anything useful:
> She POSTs this message to her outbox. (Since it's an activity, her server knows it doesn't need to wrap it in a Create object).
> Feeling happy about things, she decides to post a public message to her followers.
I hate the goddamn ActivityPub documentation. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:33:55 JST
p
@romin @Moon @judgedread I already got him to do something; I don't remember what it was specifically but I remember he went out of his way to humor me and I don't wanna press my luck since I'm a temporary guest here. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:33:54 JST
p
@romin @Moon @judgedread Oh, right, he fixed the public visibility for my timeline so that people from FSE could check what was going on without having to have an SPC account. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:33:05 JST
p
@romin @judgedread @sjw Oh, my bloat does not do that. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:26:19 JST
p
@romin @judgedread
> I see I thought they removed it.
It might have been kept as an option specifically because @sjw and I begged. (Or at least I remember begging.)
> I understand EXCEPT bloatfe has these neat settings checkboxes where you could enable/disable it at will per session.
*Manually*? Like Olin Shivers before me (or concurrent with me; he's not that old), I resent doing anything that a machine could be doing. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:22:04 JST
p
@romin @judgedread There's no Early Cuyler so I will have to make do with Splatoon:
> just add the filename to the end of the post body before sending it
:squid1: Inconvenient.
> (although you wouldn't be able to click it) :l_sigh:
Aside from allowing filenames to speak for themselves, one of the non-shitposty benefits was that if I uploaded some PDFs, they'd have their filenames visible. This might solve that part, but not the part where the post is missing its big, beefy stack of filenames. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:19:43 JST
p
@romin @judgedread
> description is only shown as img alt text
Ah, right, the thing I was complaining about is that Pleroma can be configured to display the filenames before the attachments. (They made it an option; I would have forked if they'd just removed it instead of keeping it as an option. But they also added an option to uncap the filename length, that was even better!)
> you may want to edit the post template to display the attachment description as part of the post body,
Then it'd show the filenames *twice* on some instances. I use the same instance of bloat for SPC as for Baest. -
Embed this notice
p (p@shitposter.club)'s status on Tuesday, 12-Mar-2024 00:08:14 JST
p
@romin @judgedread Did not work for me, but I wouldn't put it past most web "frameworks" to do this in an order-dependent manner, so lemme try putting it before like r did.
diff --git a/mastodon/mastodon.go b/mastodon/mastodon.go
index 8e2fa04..bb979cd 100644
--- a/mastodon/mastodon.go
+++ b/mastodon/mastodon.go
@@ -73,6 +73,11 @@ func (c *Client) doAPI(ctx context.Context, method string, uri string, params in
if err != nil {
return err
}
+ err = mw.WriteField("description", filepath.Base(file))
+ if err != nil {
+ mw.Close()
+ return err
+ }
err = mw.Close()
if err != nil {
return err
@@ -99,6 +104,11 @@ func (c *Client) doAPI(ctx context.Context, method string, uri string, params in
if err != nil {
return err
}
+ err = mw.WriteField("description", filepath.Base(file.Filename))
+ if err != nil {
+ mw.Close()
+ return err
+ }
err = mw.Close()
if err != nil {
return err -
Embed this notice
p (p@shitposter.club)'s status on Monday, 11-Mar-2024 23:58:04 JST
p
@romin @judgedread Looks like all of the uploads go through `doAPI` and some of them set `file` and some of them do not; I can't think of a place where files get uploaded but are not attachments, so I wonder if `doAPI` is fine setting a description on, like, all of them. Guess there's one way to find out! -
Embed this notice
p (p@shitposter.club)'s status on Monday, 11-Mar-2024 23:41:28 JST
p
@dcc @judgedread @mint Maintaining FSE's COG is paramount.
All GNU social JP content and data are available under the