Conversation

Notices

1. Embed this notice
   ?Smoking cigs in Room 641a ??|?? (phenomx6@fedi.pawlicker.com)'s status on Monday, 07-Nov-2022 12:51:57 JST ?Smoking cigs in Room 641a ??|??
   I was writing paper...on the PC...and it was like BELEEPEBELEEPLBPEBLEPBLEBPLEBPLEBLPEBLPEBLPEBLPEBLP and then like.....half my paper was gone.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 12:51:56 JST 寮

     in reply to
     @PhenomX6 Any Fedi instance: "we need your username, password, and email address (some instances don't require verification though)".
     Shitter: "we need your username, password, email address, phone number, country, 2FA doxxing material, gender, and soon we'll require you to see your government (digital) ID too"
     
     So yes, Fedi has far less friction on sign up than Shitter.
   • Embed this notice
     ?Smoking cigs in Room 641a ??|?? (phenomx6@fedi.pawlicker.com)'s status on Monday, 07-Nov-2022 12:52:30 JST ?Smoking cigs in Room 641a ??|??

     in reply to

     • 寮
     @ryo fedi: lol you can host a instance in your basement
     寮 likes this.
   • Embed this notice
     Jamie J (slightlyflightyone@mastodon.sergal.org)'s status on Monday, 07-Nov-2022 12:58:47 JST Jamie J

     in reply to

     • 寮

     @ryo @PhenomX6 Twitter’s new scheme seems to hinge heavily around getting you to give them all your banking and payment processing information and shadowbanning you if you do not pay $8 a month

     all while they lay off the vast majority of their security staff…

     this might not go well for people who choose to remain with the platform

     寮 likes this.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 13:00:44 JST 寮

     in reply to

     • Jamie J
     @slightlyflightyone @PhenomX6 It all depends on people's actions in the end.
     For example, when Microshaft bought up Skype, everyone fled to Discucked and they never looked back ever again, and Skype is now just a dead wasteland.
     On the other hand, that same Microshaft bought up Github, and even to this day the Github peasants are just simping no matter how horrible it'll get.
     arcanicanis likes this.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 13:05:26 JST 寮

     in reply to

     • Jamie J
     @slightlyflightyone @PhenomX6 Simple, Elon is destroying Shitter from within, we can both agree on that one.
     But if the users are so addicted to it, even though they're all running away from it, they might cuck over and pay up just to be allowed on the platform.
     Alternatively, they might make it a one way street, and just dump Shitter forever as Fedi is just a superior thing.
     
     All depends on what the Shitter refugees will do next.
   • Embed this notice
     Jamie J (slightlyflightyone@mastodon.sergal.org)'s status on Monday, 07-Nov-2022 13:05:27 JST Jamie J

     in reply to

     • 寮

     @ryo @PhenomX6 I don’t think I understand how your reply relates to my own

   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 13:08:07 JST 寮

     in reply to

     • neo
     • Jamie J
     @neo @PhenomX6 @slightlyflightyone Any selfhosted non-Gitlab server if probably better than Github.
     Hell, Gitea is even working on federation to some extend that allows users from other instances to submit issues, so you can actually have a single user Gitea instance, and still have other people submitting issues and bug fix requests and whatnot.
   • Embed this notice
     neo (neo@pl.comfysnug.space)'s status on Monday, 07-Nov-2022 13:08:08 JST neo

     in reply to

     • 寮
     • Jamie J
     @ryo
     github doesn't appear to have any viable yet equally cucked alternatives like discord presented themselves as
     
     @PhenomX6 @slightlyflightyone
   • Embed this notice
     Jamie J (slightlyflightyone@mastodon.sergal.org)'s status on Monday, 07-Nov-2022 13:08:32 JST Jamie J

     in reply to

     • 寮

     @ryo @PhenomX6 Oh! I see

     I wasn’t saying it would go poorly for them because they might choose not to pay

     I meant that it would go poorly for them because they would be heavily pressured into paying and thereby not only end up parting ways with their money, but also giving their payment processing information to a company that just laid off almost its entire security team

     寮 likes this.
   • Embed this notice
     Milo (milo@social.anthro.cc)'s status on Monday, 07-Nov-2022 13:09:00 JST Milo

     in reply to

     • 寮
     Fedi Instance: *Email Address may be optional!
     寮 likes this.
   • Embed this notice
     Coyote (coyote@social.singing.dog)'s status on Monday, 07-Nov-2022 13:29:20 JST Coyote

     in reply to

     • 寮
     @PhenomX6 @ryo Now I'm wondering if ActivityPub works on bare IPs. I want to see @GigaChad@203.0.113.123 posting about the total destruction of TLDs and DNSes off his home IP.
     寮 and arcanicanis like this.
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Monday, 07-Nov-2022 13:33:10 JST arcanicanis

     in reply to

     • 寮
     • Coyote
     You absolutely could. As long as it's a URL that any standard HTTP client can resolve, and if server implementations don't explicitly filter it, it can be done. You'd just be tying the identity to strictly that IP and be screwed if there's ever an IP change.
     寮 likes this.
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Monday, 07-Nov-2022 14:01:13 JST arcanicanis

     in reply to

     • 寮
     • Coyote
     It wouldn't matter much about the clients, since the servers decide what it'll accept through federation.
     On the topic of URIs as identifiers instead of cryptographic signatures: that's where some of the ideas brought up in 'BlueSky' project was aiming at, and was trying to invent an entirely new protocol versus implementing some concepts atop ActivityPub ( https://atproto.com/docs ).
     For example, there's nothing in the ActivityPub spec that says anything about the @user@host ID concept, that's just something tacked on from WebFinger. I'm sure someone could devise supplementary extensions to make that work, and some of that has been part of recent discussions in the recent fediverse hackathon (http://hackiverse.com/)
   • Embed this notice
     Coyote (coyote@social.singing.dog)'s status on Monday, 07-Nov-2022 14:01:14 JST Coyote

     in reply to

     • 寮
     • arcanicanis

     @arcanicanis @PhenomX6 @ryo

     if server implementations don’t explicitly filter it, it can be done.

     I guess that’s a better question: are there any ActivityPub clients that tolerate bare IPs? IIRC email also supports bare IPs, but no one is willing to take mail without a domain, so the ability is moot. I would have expected to find someone posting from an IP, but I haven’t seen it yet. I might have to try it myself.

     As for having the ID tied to a specific IP, I’ve seen enough dirty migrations that I think a sizable amount of people just don’t care. It’s sad that ActivityPub chose URIs as a means of identification instead of something more location agnostic like public/private key signing.

     寮 likes this.
   • Embed this notice
     arcanicanis (arcanicanis@were.social)'s status on Monday, 07-Nov-2022 14:03:16 JST arcanicanis

     in reply to

     • 寮
     • Coyote
     It wouldn't matter much about the clients, since the servers decide what it'll accept through federation.
     On the topic of URIs as identifiers instead of cryptographic signatures: that's where some of the ideas brought up in 'BlueSky' project was aiming at, and was trying to invent an entirely new protocol versus implementing some concepts atop ActivityPub ( https://atproto.com/docs ).
     For example, there's nothing in the ActivityPub spec that says anything about the @user@host ID concept, that's just something tacked on from WebFinger. I'm sure someone could devise supplementary extensions to make that work, and some of that has been part of recent discussions in the recent fediverse hackathon (http://hackiverse.org/)
     寮 likes this.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 14:27:41 JST 寮

     in reply to

     • Coyote
     @Coyote @PhenomX6 In theory it should work.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Monday, 07-Nov-2022 14:29:07 JST 寮

     in reply to

     • arcanicanis
     • Coyote
     @arcanicanis @PhenomX6 @Coyote That's why you buy up a static IP if you want to go down that route.
   • Embed this notice
     neo (neo@pl.comfysnug.space)'s status on Monday, 07-Nov-2022 14:29:32 JST neo

     in reply to

     • 寮
     • Jamie J
     @ryo
     that would be cool, i'd use it
     
     @PhenomX6 @slightlyflightyone
     寮 likes this.
   • Embed this notice
     Flaky (flaky@the9thcircle.club)'s status on Tuesday, 08-Nov-2022 13:25:11 JST Flaky

     in reply to

     • 寮
     • Jamie J

     @slightlyflightyone@mastodon.sergal.org @ryo@social.076.ne.jp @PhenomX6@fedi.pawlicker.com I wanted to use Patreon but went against it after hearing about the security team they also laid off.

     寮 likes this.
   • Embed this notice
     寮 (ryo@social.076.ne.jp)'s status on Tuesday, 08-Nov-2022 13:26:55 JST 寮

     in reply to

     • Flaky
     • Jamie J
     @flaky @PhenomX6 @slightlyflightyone Patreon is well known for deplatforming people they don't like.
     You'd be better off hosting your own BTC Pay server configured to accept Monero in addition to Bitcoin to be honest.
     Alongside simply putting wallet addresses and/or QR codes of your crypto wallets, it's the only truely censorship resistant way of getting funds.