#pureresearch — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pureresearch, aggregated by home.social.
-
Last time I looked in any detail, there's 14 #Threads profiles that are cloned over here onto #Mastodon
You can reply here, but the reply does not propagate back over to the original post on Threads
Likewise you will not see any Replies to the Threads posts back over here
It's some bizarre smoke-and-mirrors thing that #Zuckerberg and #Gargron are running
Search at "Search or paste URL" for threads dot net and look at Profiles
You can Follow them here (I have 14 on one List) but they will not see any replies here unless they come over to Mastodon to look at the cloned posts
See my top two pinned posts
That's all I know ATM...
-
Interesting to note that, although I do see your posts in the cloned copies of #Threads that now appear on #Mastodon, I do *not* see any of the replies that people on Threads made to your post, migrated over here to Mastodon
So there is no "see how this looks in the #Fediverse"
That's some kind of weird, unexplained PR game #Zuckerberg and #Gargron are playing
Replies to posts for the very few Threads profiles (currently 14 at last count) that do show up on Mastodon do *not* propagate over here with the original post
And my reply to your Threads post here on Mastodon will *not* propagate back over to Threads
In fact, I'll bet that unless you actually check on your cloned post here on Mastodon you will *never* even see my reply
-
Test reply from Mastodon back to Threads
. . .
And one hour later and this reply has *not* propagated back to the original post on Threads
-
So I do see your Threads.net profile as it's listed *from* Threads when I search for Threads.net here on Mastodon -- that's new -- there were only the original nine -- now there seem to be fourteen
And I do see this post both over here on #Mastodon and over there on #Threads
Let's see if my reply to you on Mastodon propagates back over to your original post on Threads
So far, in the past, this propagation of a Mastodon reply back over to the Threads original post has *not* ever happened
Ready?
Go!
[time passes]
And no joy
Because I can't (and will never) log in on Threads I can't see any posts because the newest is 1 day old
"Log in to see more replies"
Nope nope nope
-
Just yesterday the following exchange happened on the snarfed/bridgy-fed #Github,
Here: https://github.com/snarfed/bridgy-fed/issues/878
Me: "I am not an instance admin. I can only block those domains which return a #Fediverse-compatible domain name from my search.
I will also note that "bsky.brid.gy" does not return any response from the Server search page at FediDB, here: https://fedidb.org/network"
Ryan Barrett, in response: "...if Mastodon only lets you do it after you've found an existing user on that domain, then you're right, you can't block it as a user yet. If so, that's definitely an unfortunate surprise.
He continues: "The Mastodon docs don't explain this very much ... but you might be right. If so...ugh"
"that's definitely an unfortunate surprise"
"if so...ugh"
No, I *am* right
I block instances every day on Mastodon
The #BridgyFed developer himself doesn't even understand how #Mastodon #DomainBlocks work
But that's the solution we mere mortals are supposed to use?
cc @pulkomandy
-
Just yesterday the following exchange happened on the snarfed/bridgy-fed #Github,
Here: https://github.com/snarfed/bridgy-fed/issues/878
Me: "I am not an instance admin. I can only block those domains which return a #Fediverse-compatible domain name from my search.
I will also note that "bsky.brid.gy" does not return any response from the Server search page at FediDB, here: https://fedidb.org/network"
Ryan Barrett, in response: "...if Mastodon only lets you do it after you've found an existing user on that domain, then you're right, you can't block it as a user yet. If so, that's definitely an unfortunate surprise.
He continues: "The Mastodon docs don't explain this very much ... but you might be right. If so...ugh"
"that's definitely an unfortunate surprise"
"if so...ugh"
No, I *am* right
I block instances every day on Mastodon
The #BridgyFed developer himself doesn't even understand how #Mastodon #DomainBlocks work
But that's the solution we mere mortals are supposed to use?
cc @pulkomandy
-
Just yesterday the following exchange happened on the snarfed/bridgy-fed #Github,
Here: https://github.com/snarfed/bridgy-fed/issues/878
Me: "I am not an instance admin. I can only block those domains which return a #Fediverse-compatible domain name from my search.
I will also note that "bsky.brid.gy" does not return any response from the Server search page at FediDB, here: https://fedidb.org/network"
Ryan Barrett, in response: "...if Mastodon only lets you do it after you've found an existing user on that domain, then you're right, you can't block it as a user yet. If so, that's definitely an unfortunate surprise.
He continues: "The Mastodon docs don't explain this very much ... but you might be right. If so...ugh"
"that's definitely an unfortunate surprise"
"if so...ugh"
No, I *am* right
I block instances every day on Mastodon
The #BridgyFed developer himself doesn't even understand how #Mastodon #DomainBlocks work
But that's the solution we mere mortals are supposed to use?
cc @pulkomandy
-
Just yesterday the following exchange happened on the snarfed/bridgy-fed #Github,
Here: https://github.com/snarfed/bridgy-fed/issues/878
Me: "I am not an instance admin. I can only block those domains which return a #Fediverse-compatible domain name from my search.
I will also note that "bsky.brid.gy" does not return any response from the Server search page at FediDB, here: https://fedidb.org/network"
Ryan Barrett, in response: "...if Mastodon only lets you do it after you've found an existing user on that domain, then you're right, you can't block it as a user yet. If so, that's definitely an unfortunate surprise.
He continues: "The Mastodon docs don't explain this very much ... but you might be right. If so...ugh"
"that's definitely an unfortunate surprise"
"if so...ugh"
No, I *am* right
I block instances every day on Mastodon
The #BridgyFed developer himself doesn't even understand how #Mastodon #DomainBlocks work
But that's the solution we mere mortals are supposed to use?
cc @pulkomandy
-
Just yesterday the following exchange happened on the snarfed/bridgy-fed #Github,
Here: https://github.com/snarfed/bridgy-fed/issues/878
Me: "I am not an instance admin. I can only block those domains which return a #Fediverse-compatible domain name from my search.
I will also note that "bsky.brid.gy" does not return any response from the Server search page at FediDB, here: https://fedidb.org/network"
Ryan Barrett, in response: "...if Mastodon only lets you do it after you've found an existing user on that domain, then you're right, you can't block it as a user yet. If so, that's definitely an unfortunate surprise.
He continues: "The Mastodon docs don't explain this very much ... but you might be right. If so...ugh"
"that's definitely an unfortunate surprise"
"if so...ugh"
No, I *am* right
I block instances every day on Mastodon
The #BridgyFed developer himself doesn't even understand how #Mastodon #DomainBlocks work
But that's the solution we mere mortals are supposed to use?
cc @pulkomandy
-
Interesting Discussion going on the #Bluesky #Github right now:
(I won't doxx anyone Over Here; see link if you want)
A: "Which advantages does this [Bluesky] have about the web-standard ActivityPub? #1782
Which advantages does this have about the web-standard ActivityPub?"
B: [link to the #ATProtocol page https://atproto.com/guides/faq#why-not-use-activitypub]
"Why not use ActivityPub?
Account portability is the major reason why we chose to build a separate [ATProtocol] protocol. ActivityPub is a federated social networking technology popularized by Mastodon"
A: "These are no valid reasons.
When I follow someone, I don't care wether he/she/they can easily port there account.
How the username is made up doesn't matter. You can easily convert between subdomain and @-notation... "More here: https://github.com/bluesky-social/atproto/discussions/1782
-
OK
"As far as I know, they intend to keep maintaining and developing Firefish, and a new stable version will finally soon be released"
Looking at the timestamp/date of your post, and the formal statement (linked in thread, and now for completeness below) by Kainoa, and I find your statement a little... unsupported -- at least by anything I've seen
Have you had out-of-band communication with Kainoa?
Last I heard and from what I've read Naskya is *not* a programmer, but only a caretaker
Who's going to be working on code to get to "a new stable version will finally soon be released"?
For completeness, here: https://git.joinfirefish.org/firefish/firefish/-/issues/10847
-
"and we're especially sad about all the users who's data is now gone due to both major instances going down"
At this point, anyone who has not pulled down their entire archive and stopped using Firefish dot Social a couple weeks ago at the latest is simply not paying any attention
Sorry, but there it is...
-
Yeah, now I'm getting a blank stare even for "View Source" at firefish dot social
Last couple times I checked, at least it was able to push out some html even when the site itself didn't render anything visible
Wow... what a long, strange trip *that's* been...
______@_______:~$ ping firefish.social
PING firefish.social (162.247.131.14) 56(84) bytes of data.
^C--- firefish.social ping statistics ---
18 packets transmitted, 0 received, 100% packet loss, time 17385ms"She's dead, Jim..."
* * * * *
BREAKING UPDATE 02/03/24:Firefish is -- for all purposes -- gone:
"If Firefish is going to come back, Kainoa won't have a hand in it. They quietly handed over the keys to the repo to a maintainer... who has publicly stated they aren't a programmer and are just looking after commits..."
Here: https://git.joinfirefish.org/firefish/firefish/-/issues/10847
#Firefish #DownHard #ShesDeadJim #Iceshrimp #Sharkey #Catodon #Misskey
#PureResearch -
It's a cloned post from the true account on Threads that is cross-posted back over here onto Mastodon
No one that I've read has made it clear exactly why Threads and Gargron/Mastodon are doing this little cross-posting experiment
Your reply here on Mastodon does *not* propagate back over to the real, original profile on Threads
All that said, 0xjessel posted yesterday about
"we created a new endpoint that now allows 3p apps/websites to use a dynamic URL to prefill text into our threads composer. this will enable developers to build social plugins for Threads!the route is `/intent/post?text={...}`, with the text param being the URL-encoded string you want to prefill."
Here: https://www.threads.net/@0xjessel/post/C2isZ9eP-yB
In the post here you're replying to, the poster doesn't seem to have got it right
It's one big long garbage string that I've tried to dissect with no success
Remember: what you can see of Threads posts over here on Mastodon are simply a mirage, at best
-
Interesting to note that, of the nine #Threads accounts currently being cloned over here on #Mastodon only one account *also* has a native Mastodon profile
That profile has now #Blocked me
The Threads clone posts are still visible over here; have to do a little research to see if that Mastodon Block keeps me from seeing newer Threads posts over here...
Interesting...
* * * * *
Update: I don't think so. Profile's most recent post is one day old and I see it both on Threads and cloned over here on Mastodon as being one day old -
Interesting to note that, on Mastodon, the displayed post shows "Preview not available. Click to open"
(Firefox browser tab on Ubuntu Linux)
On clicking, the original post opens a player with the URL
scontent dot cdninstagram dot com
So I'm not sure exactly what's "federated" here, except that a clone of your original post on #Threads displays back over here on #Mastodon
Looks like the voice content is still coming from Instagram
Finally, I'm betting that this reply on Mastodon will *not* propagate back over to your original post on Threads
Here: https://www.threads.net/@shubhankar_91/post/C2dOrK5P-b4
-
OK the weather's gone back boring: merely cold and rainy
Back to Pure Research(tm)
This appeared last night:
"Noticed that @threads.sys popped up when I was seeing there's been anything new with Threads from a Mastodon admin POV. Wonder if this account is like the initial system account created on new #ActivityPub servers"
From what I can find @threads.sys does exist on Mastodon; it's brand new; it does *not* seem to exist back on #Threads itself: ("Sorry, this page isn't available The link you followed may be broken, or the page may have been removed")
So what is it?
Seems to be a new Threads endpoint on Mastodon, but who owns it?
I've added it to my Threads List (which now has 10 threads accounts) ; remains to be seen if there's any activity
* * * *
More recent update: looks like my Follow request has *not* been accepted, which means the account has *not* been added to my Threads List, now at 9Interesting...