#slurp — Public Fediverse posts

A mysterious buying spree is unsettling Europe’s booksellers
Independent retailers are receiving vast orders for obscure titles, fuelling suspicions that tech companies are using them to train AI.
Last May Tomás Kenny of famous Galway book retailer Kennys received what he describes as a “bananas” online order for 5,000 books. But it was less the scale of the order that caught his eye and more its eclectic selection.
https://www.irishtimes.com/world/europe/2026/08/10/a-mysterious-buying-spree-is-unsettling-europes-booksellers/
#ai #slurp #bookstodon

This might be crazy but... I don't need my old exploded host's fediverse export to restore my past posts and media...

It was bridged via #bridgyFed so #slurp can fetch *that* and then import to my #selfHosted #goToSocial

Never thought that moving one's own posts from a #Mastodon-archive to #GoToSocial would be possible - except boosts and likes of course. With #slurp by #Vyr Cossant (https://codeberg.org/vyr/slurp) this was finally possible and yet this change's impact isn't as big as expected... 😀

Also @box464 tutorial was a great orientation: https://box464.com/posts/gotosocial-slurp/ 👍🏻🙏

Wer jetzt noch #Google für #Suche nutzt, der hilft mit, dass das #WWW (das viele Menschen für das #Internet halten) in der Form stirbt, wie wir es kennen:
https://www.heise.de/meinung/Google-Suche-Le-Web-c-est-moi-11302565.html

Es gibt nun keine Ausrede mehr: wechsel ab sofort auf Alternativen.

Ich nutze aktuell beispielsweise https://duckduckgo.com/ als auch https://www.startpage.com/ und das schon seit mindestens 15 Jahren.

#GoogleSearch #enshittification #AI #KI #slurp

Finally I got SLURP to work. I nice tool where you can import your old Mastodon posts to GoToSocial, and backdate them to there original post date. However, there is a lot limitations so only around 1/3 posts were imported.

Mastodon should develop something like that too, so it is possible to keep your old posts when you move your profile. BlueSky and GoToSocial can, so why not Mastodon?

#Slurp #mastodonmigration #gotosocial #mastoadmin #fediverse

´Lut @arthurr bonne route et bonne poule #Miam #Slurp
👋🏼☕️🫖👋🏼

#Slurp https://codeberg.org/vyr/slurp schlürft sogar die alten Mastodon-Toots (mit Bildern!) aus dem Masto-Archiv in das neue frische #GotoSocial hinein. Was ja grundsätzlich gar nicht geht, wie sie bei Mastodon immer sagen 😀

Der valide Punkt der Masto-Leute ist natürlich: Es sind im Grunde neue Posts auf der neuen Instanz, die zurückdatiert werden. Weil ja nunmal die URLs der alten Posts auf der alten Instanz nicht "magisch" im ganzen Fediverse umgebogen werden können. #FediAdmin

I just switched from #mastodon to #gotosocial

Instead of being on the massive mastodon.social, I am now hosting my own social media instance on a VPS in Quebec, Candada. #selfhosted

I transfered followers and followings, but I think I lost a few during the process.

A few days ago, I used the third party tool #slurp to move my pixelfed posts.

But this time with Mastodon, Slurp was giving EOF errors and I abandonned the idea transfering my posts. They wouldn't get comments, likes, etc anyway.

EDIT: I'll probably delete my mastodon.social account soon. I'll give it a few days to make sure everything works properly,

Right, the @chirp #GoToSocial account has been migrated here. Thanks to the #slurp software, most posts have also been migrated (except non-public ones and replies). Manual pinning was also required but that's ok.

You shall get future news about the #noGooMe #SearXNG instance running on #OpenBSD from here as of now. Spoiler alert: there will be some really soon ;)

Migration Status Update 📈
Die alte Mastodon-Historie ist angekommen! 🚚 Per slurp wurden 380 Posts sauber nach GoToSocial migriert - Fotos, Text, Timeline-Integration funktioniert tadellos.

Das Föderation-Wachstum läuft weiter auf Hochtouren: 2.750+ bekannte Instanzen in nur vier Tagen, Dank GTS-HolMirDas und seinen 102 RSS-Feeds. 🌐

Performance bleibt atemberaubend: Der komplette Social Media Stack läuft mit 426 MB RAM:

• 419 MB GoToSocial ⚡
• 4 MB FediFetcher 🔄
• 4 MB GTS-HolMirDas 📡

Zum Vergleich: Mastodon allein frisst (bei mir) 4-5 GB. Das ist Faktor 10-12 Unterschied! 🤯

Import + Live Content-Discovery + Thread-Vervollständigung = alles parallel ohne Performance-Impact. Moderne Software-Architektur macht's möglich.

GoToSocial ist definitiv production-ready. Die Migration war die richtige Entscheidung! ✅

#GoToSocial #Migration #Performance #SelfHosting #Fediverse #ContentDiscovery #ResourceEfficiency #slurp #OpenSource

@wardi I recommend @gotosocial with @phanpy as the frontend/client, and you can actually migrate your posts (and other stuff) from your current instance to a GTS one using #slurp :gotosocial: 💚

#slurp druch #satty ersetzt. Sehr schick!
Leider nicht im "normalen" #openSUSE Repository zu finden.
Hier aber:
https://download.opensuse.org/repositories/home:/mantarimay:/sway/standard/

#windowtiling #niri #hyprland #sway #wayland #tumbleweed #linux

@syll @GazouilleurFou Ouiiiiii il en reste ! Il y a le gros bol 👀 C'est vrai #slurp #yummi 👻

I've made the migration of @maou to my #gts instance and used #slurp (a tool from @vyr - https://github.com/VyrCossont/slurp) to try to not loose all the nice toots that have been posted in past years.

522 of 2908 toots have been migrated :ablobcateyesflip:
For what I understood, only a subset of posts can be migrated: top-level public posts that doesn't include other accounts.
It makes sense, but I have the feeling to loose a part of @maou's history :maou_rsquare:

Also, it seems 906 of 1180 followers have been informed of the move; I'm not sure how the moving information works but I've the feeling there's always some followers lost in this kind of operation. Or may be, it just takes a long time to contact all servers and I have to wait few days...? :ablobcatcoffee:

#gotosocialmigration #gotosocial

Doing some tests with my testing #GoToSocial instance.

I've created an account for which follow request must be approved manually.
After ~20 minutes I finally found that the approval/rejection of request is not available from #gts user settings panel, but through the client (at least I can manage it in Tusky) :ablobcatwave:

It's mostly 9.00pm and my brain is not able to manage a simple thing like this, time to go to bed: I'll manage my #slurp migration tests another day...

Gonna #slurp up my old posts at some point tonight. Sorry if it spams. I don't think it does.

Ref: https://github.com/VyrCossont/slurp

#nsfw la delicatezza della #succosità #femminie... #slurp

After contemplating for a while on whether to set up an own #Pixelfed instance or not, just go with a separate "photos only" account on my GtS instance ... I stumbled upon this blog post from @box464 about how to #slurp all your photos from Pixelfed to GtS.

https://box464.com/posts/gotosocial-slurp/

This seemed to me like it's the best idea as I never liked this separation of bubbles and having to boost my Pixelfed posts for my followers here to see them.

So, I've used my already setup local Pixelfed instance to import everything from my old Instagram account and then slurped that to here. After that, I've then slurped everything from my pixelfed.social account to here as well. Everything under one roof - I like it.

Also, as mentioned in that blog post, there's @impressia (for iOS) which can give a Pixelfed-like experience with basically any Mastodon-like account.

#ownyourdata #mastodonmerge #profilemerge

@feoh we'll still have backdating accessible by API as well, in case people want to customize their import process past whatever the built-in feature allows. power users might want to include a note in the post text, or remove references to dead accounts, or import from Misskey, Tumblr, Bluesky, or some other setup that doesn't make sense to support in GTS itself.

#slurp

@feoh that was the intent. i built this for myself first, so i could fully migrate off my old self-hosted Mastodon Glitch instance.

next step is to integrate the import feature into GTS itself. i don't have a timeline on that — i've been absolutely underwater at my day job — but slurp proved that quiet import is useful for many people, and it'd be much more accessible as part of GTS with a web UI.

we can also add a few refinements: one thing people have suggested is keeping track of the post's original URL, maybe displaying it on public web pages, maybe adding it to the scope of GTS search.

#slurp

when exporting an archive of your Fedi posts, slurp will no longer give up if a replied-to post is missing, or if an attachment or emoji can't be downloaded.

thanks to reporter scgtrp on GitHub for the suggestion.

#slurp

@Valon_Blue I suggest #GoToSocial for the same reasons mentioned by the other reply to your post and because you can try your hand at migrating your actual posts from Mastodon to GTS using #slurp. this functionality will be implemented natively anyways, if you're not inclined to tinkering in the CLI.

as for frontends, I also recommend @phanpy

I've successfuly moved my Pixelfed content over to a new account thanks to #Slurp and #GoToSocial. But, I can't migrate my account followers because of this Pixelfed bug. Specifically, I am getting `Invalid account lookup response` returned from Pixelfed after submitting the migration request.

It's only a slight annoyance as I only had a few followers. But it's stuff like this that makes me twitch when someone says "you can just move your account".

https://github.com/pixelfed/pixelfed/issues/4858

"Error: [GET /api/v1/custom_emojis][401] customEmojisGetUnauthorized"

... an error I've never seen before in my life, and nobody else has either!!! YAY!!! has anyone used #slurp for fedi post migration and knows what the heck this is

Hi folks. I'm thinking about going back to self-hosting on my own hardware (likely with GoToSocial this time), but I don't want to leave all my posts behind again. Has anyone migrated from Mastodon to GoToSocial and used something like Slurp to import old content?

Any gotchas I should be aware of?

#AskFedi #ContentMigration #GoToSocial #Mastodon #Slurp

@are0h @vyr taking from how I'm using it, #slurp can be used to import whatever the native Migration feature doesn't, if you want to do that.