Conversation

Notices

1. fedi-block-api notifier (fba@ryona.agency)'s status on Tuesday, 23-Jul-2024 01:40:45 JST fedi-block-api notifier
   medibubble.org has blocked the following instances:
   
   chudbuds.lol for "Holocaustleugnung, Kinderpornographie"
   detroitriotcity.com for "Hate speech "
   mashtodon.alterracloud.com with unspecified reason
   • meso (meso@netzsphaere.xyz)'s status on Tuesday, 23-Jul-2024 01:40:39 JST meso

     in reply to

     • pistolero
     @p @fba real raped women only at chudbuds
     matrix07012 :thotpatrol: :cunnyEmpire: likes this.
   • pistolero (p@fsebugoutzone.org)'s status on Tuesday, 23-Jul-2024 01:40:41 JST pistolero

     in reply to

     • meso
     @meso @fba There is definitely no CP at that domain. There is nothing at that domain but a notice that the instance is closed forever. I would also not trust Ze Jahmans to decide what does or does not constitute CP.
   • meso (meso@netzsphaere.xyz)'s status on Tuesday, 23-Jul-2024 01:40:42 JST meso

     in reply to

     • meso
     • pistolero
     @p @fba based medlibubble.org admins
   • meso (meso@netzsphaere.xyz)'s status on Tuesday, 23-Jul-2024 01:40:43 JST meso

     in reply to

     • pistolero
     @p @fba BASED. TRUE.
   • pistolero (p@fsebugoutzone.org)'s status on Tuesday, 23-Jul-2024 01:40:44 JST pistolero

     in reply to
     @fba
     
     > chudbuds.lol for "Holocaustleugnung, Kinderpornographie"
     
     Holy fucking shit, how retarded is whoever runs medlibubble.org?
   • NonPlayableClown (nonplayableclown@postnstuffds.lol)'s status on Tuesday, 23-Jul-2024 02:39:13 JST NonPlayableClown

     in reply to

     • pistolero
     Idk why these jackasses keep defederating a dead instance.
     
     It's not going to comeback.
   • pistolero (p@fsebugoutzone.org)'s status on Tuesday, 23-Jul-2024 02:39:13 JST pistolero

     in reply to

     • 
     • NonPlayableClown
     @NonPlayableClown @fba
     
     > Idk why these jackasses keep defederating a dead instance.
     
     There are instance that block wagesofsinisdeath.com, a joke instance that existed for less than one month in 2019. stefanbohacek.online blocked the instance less than a month ago: https://fba.ryona.agency/?domain=wagesofsinisdeath.com .
     
     Two days ago, mermaid.social instance-blocked gab.com: https://fba.ryona.agency/?domain=gab.com . gab.com federated for a few months in 2020 and then stopped completely. mermaid.social was registered 2024-07-13.
     
     feminism.lgbt was the old domain for neckbeard.xyz, which is now bae.st. feminism.lgbt was revoked by the registrar in 2019. social.plux.wtf, which did not exist until 2022-11-06, blocked feminism.lgbt, citing "toxic, hateful, and otherwise dangerous activity (harassment, hate speech, trolling, general bad-faith behavior, etc.)." stefanbohacek.online blocked it last month, too. https://fba.ryona.agency/?domain=feminism.lgbt
     
     Hey, @mint, how difficult would it be to do a "top schizos" list? Like, the instances that block the largest number of servers that were dead before the instance existed? I will add endpoints to fedilist to support this effort.
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 23-Jul-2024 02:43:39 JST 

     in reply to

     • NonPlayableClown
     • pistolero
     • practically without merit
     @p @NonPlayableClown @fba >Like, the instances that block the largest number of servers that were dead before the instance existed?
     Might be possible, but would require some complicated queries and I know jack shit about SQL. @pwm made https://fba.ryona.agency/weighted which makes solves the problem of the opposite end.
     
     Speaking of schizos, there's a guy that tired maknig a big deal of reordering the domain of an instance that barely amassed 100 posts in all three months it existed.
     Screenshot_20240722_204201.png
     † top dog :pedomustdie: likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 23-Jul-2024 02:46:19 JST 

     in reply to

     • pistolero
     @p @fba They've supposedly closed down on 1st of July, but they're still spamming Delete requests over the whole network, making my instance fetch their empty profiles (at least until I patched pleromer to MRF check deletes earlier in pipeline). Noticed that the funny block reason didn't get fetched by FBA since the instance was probably offline when fetching peerlists, so decided to grab it manually while it's still up.
   • saint podiatron (goatmeal@shitposter.world)'s status on Tuesday, 23-Jul-2024 08:04:21 JST saint podiatron

     in reply to

     • 
     • NonPlayableClown
     • pistolero
     @p @NonPlayableClown @fba @mint I don't think it's that schizo. I copied whatever kf.cc defederated. I know they really were nasty pedos. I'm not gonna check if they are still there.
      likes this.
   •  (mint@ryona.agency)'s status on Tuesday, 23-Jul-2024 08:06:31 JST 

     in reply to

     • Hoss Delgado
     • pistolero
     @Hoss @p @fba No, it's just that fetching (empty) actor that deleted some post comes earlier in pipeline than rejecting the delete activity. This adds some bloat to users table.
   • Hoss Delgado (hoss@shitpost.cloud)'s status on Tuesday, 23-Jul-2024 08:06:32 JST Hoss Delgado

     in reply to

     • 
     • pistolero
     Your instance honors deletes?
   •  (mint@ryona.agency)'s status on Tuesday, 23-Jul-2024 08:07:14 JST 

     in reply to

     • NonPlayableClown
     • saint podiatron
     • pistolero
     @goatmeal @p @NonPlayableClown @fba Reasonable, but I think what he's talking about is grabbing as many blocklists as possible, no matter how obsolete or incorrect those might be.
   • practically without merit (pwm@gh0st.live)'s status on Tuesday, 23-Jul-2024 18:37:09 JST practically without merit

     in reply to

     • 
     • NonPlayableClown
     • pistolero
     @mint @p @NonPlayableClown @fba
     I can definitely cook up a beating a dead horse winrar list if there's some interest. First impression tells me that we would need an api to fedilist that asks if an instance is dead, and if so, since when. Then every time you record a block you make sure you know whether the blocked instance is alive or dead at the time of the block according to fedilist, and update your database accordingly if you have no data. Probably need some contingencies for resurrection (fba-side), and a minimum time after which someone is dead (fedilist side), and some caching for live instances to make sure fedilist isn't hammered with queries about if poast is dead yet (fba-side). After that the query is simple. It's intelligently ascertaining the information and keeping it in sync that's a bit weird but not impossible.
      likes this.
   • pistolero (p@fsebugoutzone.org)'s status on Tuesday, 23-Jul-2024 18:37:38 JST pistolero

     in reply to

     • 
     • NonPlayableClown
     • practically without merit
     @pwm @mint @NonPlayableClown @fba
     
     > api to fedilist that asks if an instance is dead, and if so, since when.
     
     Yeah, the status changes page would normally do that, but what is actually useful in this case would be the last successful contact timestamp. That's on the page, I can make it an endpoint, tack on something like the time it was first discovered, the most recent successful contact, etc. It'd probably be better to do this by putting microdata annotations on the page (so you just request the regular page and then pull out the timestamp), but for the lulz I am willing to do a JSON endpoint.
     
     Speaking of status changes, I've been meaning to make the status changes page accept multiple hostnames because that makes the RSS feed a little more useful, you can subscribe to a set instead of subscribing to 50 RSS feeds for individual instances, so that's done, it's one of those things that is trivial enough that it always slips my mind: http://demo.fedilist.com/instance/recent-changes?host=fsebugoutzone.org,freespeechextremist.com,shitposter.world,gh0st.live,ryona.agency,poa.st . I think kirby was interested in that but I can't remember on any given day what server kirby is on.
     
     > Then every time you record a block you make sure you know whether the blocked instance is alive or dead at the time of the block
     
     Yeah, that was my thinking, but that it'd be recorded locally in the DB, so that someone imports a blocklist and then you don't need to fetch a thousand instances every time. Then when you do the query, you just check, like `where block_timestamp > last_alive_timestamp` or if you want to be certain, `where block_timestamp > last_alive_timestamp + '30 days'::interval`. Something like that.
     
     > a minimum time after which someone is dead (fedilist side),
     
     It's marked as "down" if it's been at least an hour and there have been at least four unsuccessful attempts, but I think if I just write the timestamp of the last successful contact, that's a little more flexible. Like, you can get the status by just hitting the recent changes CSV: http://demo.fedilist.com/instance/recent-changes/csv?host=fsebugoutzone.org.
      likes this.
   • practically without merit (pwm@gh0st.live)'s status on Tuesday, 23-Jul-2024 18:37:55 JST practically without merit

     in reply to

     • 
     • NonPlayableClown
     • pistolero
     @p @NonPlayableClown @fba @mint
     
     > Yeah, that was my thinking, but that it'd be recorded locally in the DB, so that someone imports a blocklist and then you don't need to fetch a thousand instances every time.
     
     Sorry, poor phrasing, that was also my thinking. You could just keep a table of "instance, state, last_checked" and refresh that record if last checked was past some arbitrary threshold. Hell you could even do exponential backoff on checks with a counter column (reset the counter to 0 when the state is toggled). Would still allow for revival of dead instances (does that ever even happen though?).
      likes this.