One reason why squashing moths is a bad idea is that they can stain the surface they are on, especially if it's drywall. Scrubbing the stain after the matter usually makes the stain worse.
Instead of squashing moths a preferred method it to use an electric fly swatter and zap them in flight.
When moths are on the wall they have a tendency to fall/jump downwards. With this knowledge one takes the swatter while being live (active) and slowly travel upwards until one barely touches the moth. In the best case the moth will jump down and get instantly zapped. In the case it flies away, the racket is in the position to quickly flick the wrist and zap it in mid flight.
@barefootstache O...M...G
Why the fudge would you write this stuff man... Such a clever person and "LifeHack" about moths...
And no need advocate killing moths or using electric fly swatters... just makes it worse.
What a waste of your talent and knowledge dude... though I accept may you might need to go through this phase before you go to greater things,., 🚀 but just oh man
Can I give you something better to do? Y/N/M ?
Can I pay you to do something else?
(honestly / genuinely)
Example =============
☑️ Make the Mastodon backup of posts (JSON file from export) into another format to show posts AND it's picture in offline viewer / browser (currently Mastodon export is not human readable or connecting the pictures offline)
⬆️ Really would help people I'll 100% credit and shout your name since you like adding / modding / fixing things like in OSM
"Can I give you something better to do? Y/N/M ?
Can I pay you to do something else?
(honestly / genuinely)"
Depending on what you have exactly in mind?
"Make the Mastodon backup of posts (JSON file from export) into another format to show posts AND it's picture in offline viewer / browser (currently Mastodon export is not human readable or connecting the pictures offline)"
Are you just looking for an offline clone? And/or how complex are you imagining the whole app?
@barefootstache Yes or very similar. Something that takes my JSON backup and gives out something more human readable .
The minimum is to see the basic post and picture (together) like I can now... (paginated ideally not AJAX style infinite scroll)
Or saving each post as a file that I can open (like a saved email or Wodpress export) with picture inside (not downloading from web). Name for each file could be from CW title or first line of post or first 10 hashtags.
Not looking for a big app - more to convert JSON to something useful and then as many bells and whistles to tweak on top.
@freeschool something like a twitter card?
@barefootstache I was also thinking more as simple HTML output with picture... so I can load in any browser new and old.
I didn't know what Twitter Card is before I looked it up now - seems it's a way of presenting tweets and perhaps loading details from a website post to a tweet post.
Interesting probably more for loading Wordpress to Toots but just as basic output the pictures at the top and the text next below it (perhaps thumbnail for pictures or only if above certain size).
There were similar attempts to do the same for Mastodon. From the brief look of some projects, they didn't get that far.
Before discussing the initial result and eventual purpose/goal of the project, we need to search the web if other attempts were made or even exist.
Thus I purpose that you search the web and see if you can find any software that can process or read "Activity Stream 2.0" (the underlying schema of the JSON).
If none can be found or the quality does not align with your vision, then I will write up a first draft of an action plan.
From what I have (not-)found so far, if we make a tool for Activity Stream in general, each actor (social media platform and more) can theme the output to their liking.
@barefootstache
MORE links and ideas
█Mastodon Migration script to new account (just favourites and reblogs, not posts and media!)
https://github.com/MirceaKitsune/mastodon_migrate
█Bulk upload posts on Mastodon through another service (but the CSV import idea is the main point here)
https://help.socialbu.com/article/412-how-to-bulk-upload-posts-on-mastodon
@barefootstache Was only showing what I had come across and hoping you'd see doing it as a project the best way you can from all efforts. CSV wasn't my end option or end of thoughts in any way as the answer
I still agree like you said nobody has finished on it and is still probably the best to do it best way you think how from all of that (which was your step 1 in checking out existing [incomplete] efforts).
@freeschool true that and thanks :)
How familiar are you with git?
@barefootstache I'm not familiar at all.
@barefootstache Someone sent me a link to this but is command line and someone out of my skill level:
" jq is written in C and has no runtime dependencies, so it should be possible to build it for nearly any platform. Prebuilt binaries are available for Linux, macOS and Windows. "
I am familiar with jq and started writing a review on my daily blogging challenge on how to use that tool to help filter through all the toots.
The tool runs into the same issue as many other one's I have found, is that they are trying to process the whole file at once which can very resources intensive and potentially crash the system.
Any JSON file larger than a couple of MB would suffice to crash one's system. That is why in such situations one needs to use either the web or techniques from big data.
@barefootstache Ok. Just saw your draft page and what I sent almost at same time includes a lot of what I said so Good stuff. Below not needed.
Yes. Even with my knowledge I could guess thousands of message + GB's of pictures are going to be hard to present and probably per post and per file would be best way to go / more manageable for a micro-blog level.
My outbox.json is ~8mb
https://bovine.social/mastodon/
comes close but makes posts all one infinite scroll which is a bit unusable for posts lower down and heavy for browser the more you go down 100's of post (even heavier if it was loading pictures remotely on the fly or locally from backup dir)
so a file-based output per post seems the way or paginated summary of say 10 per page
So 9000 posts would be 900 paginated pages if each pagination had 10 posts so each page isn't too long.
@freeschool converting JSON to CSV: there exist plenty of online and terminal tools for that