@renatolond Hey, after I had to rebuild my Mastodon instance, the crossposter hasn’t been working for me. So I need to try from another browser to re-authenticate my accounts? Or is there a better approach?
Also, great work on the crossposter!
@terry that’s what I’m thinking too, I just have no idea how it’ll affect my timeline/others timelines if I do such a thing.
So if you have you Twitter archive. Wouldn’t it technically be possible to migrate those posts to Mastodon, but into the past? Effectively creating the statuses with their original created timestamp?
@grmpyprogrammer @ramsey 😂 that’s fair enough. My version of this is that I curse like a sailor, which is apparently frowned upon in some professional settings. Hasn’t stopped me yet though!
@grmpyprogrammer @ramsey why not both?
It’s kinda refreshing opening Mastodon, and not having 500+ new posts to catch up on. I’m sure I’ll get there eventually as I build up my follows. But it’s definitely relaxing
Petting your dog is all fun and games until she whips her head up and head butts you in the nose. Ow
I was going to keep a clean delineation between photos and regular posts made here. But I guess I should pay the #Dog tax
@paul TweetBot is the only thing that made Twitter usable for me. I volunteer as tribute as a beta tester for the Mastodon build
Getting into #mastodon have been an interestingly reinvigorating experience. I’m already thinking about setting up a #pixelfed instance this weekend so that anyone who follows me can choose if they want to seee my photos or not.
It’s also made me want to both update my website and start technical writing again, oddly enough. That one seems harder than setting up a whole other Fediverse app though.
@elazar What features does it have or help with out of curiosity?
There’s a lot more to the #fediverse than I originally knew. I can only guess there’s even more to find. But for now, https://fediverse.party/ is a pretty neat reference point.
@adam whaaat? Why not? It’s not like we’re both incredibly busy professionals who like to actually enjoy their downtime not dealing with work-like problems.
Oh wait lol
@pamelafox have you tried using https://asciinema.org/?
@adam Oddly same though a mix of DO and AWS. Attendes at @longhorn started sharing their Mastodon handles and I just rush jobbed it. Admittedly it’s pretty easy, but after having to manually restore from kernel panicking my original droplet I might move to AWS fully. Need to reduce my current bill by like $200/month though first.
And yea, thought the same thing since I want/wanted to join the .social TLD trend. Guess you could nginx route all domains to same instance?
@adam that’s the same thought I had recently. Technically went with the domain I picked for example to be a place for the Skrasek clan. But technical upkeep plus teaching everyone how to use this feels like I’m just creating headaches for myself.
That sweet sweet self ownership though
@mglaman I’d personally lean towards a new major release, as dropping support for a framework version feels like a breaking change.
Plus you could document in the README that for Laravel 8 and above to use v3, while older versions stay with v2
After a lot of pain, I'm finally back in action and on v4.0.1. And now I am going to sleep. Not being able to sleep and sickness is a pain in the ass
Since this cross-posts to Twitter, word of warning. DigitalOcean's one-click Mastodon setup is still on Ubuntu 18 and like v3.1.x.
I had to upgrade Node to 14 during the process was the main thing. Other than that, and a weird webpack compile issue, smooth sailing.
Screw it; let's tempt fate and do an Ubuntu upgrade tonight. Something something leeroy jenkins?
This did not go well, and I've just spent the last four hours doing manual data recovery from a broken Droplet to a new droplet. That was a painful experience, and I've learned my lesson.
Thanks, DigitalOcean, for pointing me in the right direction. Also, have more money and do automatic backups for me kthx
After some trial and error and a bump to v4.0.1, my @Mastodon instance is back up again.
I gotta say, the upgrade process could be a bit.. better or better documented. Having to parse through multiple versions in Github to read the various upgrade steps was painful. Admittedly I'm not sure what the best solution/improvement would be
