I'm watching the anxiety level around .gov web resources grow after the election (for good reason) and am reminded of the #DataRefuge and #EDGI web monitoring work that started in 2016.
In theory the End-Of-Term #WebArchiving project pulls in lots of resources that could be at risk. https://eotarchive.org/ But it can be challenging to verify and get a sense of how good coverage is, e.g. for GIS data.
It feels like it could potentially be made easier?
In today's blog post, I introduce the `grep()` function in R, a key tool for searching patterns in text data.
It allows case-sensitive searches by default but can perform case-insensitive searches with the `ignore.case` argument.
This flexibility is essential for text mining, data cleaning, and analysis. I outline the basic syntax, usage examples, and common mistakes.
Post: https://www.spsanderson.com/steveondata/posts/2024-09-04/
#R #RStats #RProgramming #Programming #Coding #textdata #stringr #grep
The best email you can get from any company is “you haven’t logged into our app for a while, so we are going to delete your info unless you do in the next X days.”
Now that is an indicator of a company that has their shit together.
It shows they are auditing activity.
It shows they don’t want to hoard data.
It shows they are making an effort.
Ironically, it makes me want to sign in and use their stuff more.
@timbray @alanc @josephholsten A good autoconf replacement would have the actual executable script "configure" file be immutable and data driven, so the big complex logic is known to be non-malicious just by matching upstream hash & local behavior is in human-comprehensible data.
It would support only collection of building-user's preferences, dep search, and compile/link checks using selected tools - not executing arbitrary code at config time.
So there are all kinds of folks trying to figure out where the Space-X rocket came down, based on telemetry and other data.
It would be wild if they turned up MH370 while looking.
Like I said before, all of that is non-standard functions that the vast majority of the fediverse doesn't even support.
I think you might be confusing ease and possibility. Few people even when moving instances within the fediverse are going to have that option (save for those moving between two instances of the same platform).
It's not whether there's some convenient tool to move your posts or other data.
It's about whether after the move you can still get the same updates and talk to the same people.
Think of it in terms of the oldest surviving federated network: changing email accounts.
Before SMTP (the federated email protocol), you had to have accounts on every server with people you wanted to talk to. After you only had to have one account, but could readily move about the network to other servers if you got fed up with your server's bullshit or another offered better services.
(And for the record, public bridges with no opt-out methods exist for email as well)
@HistoPol @jamie @oliphant @snarfed.org @luca @PCOWandre @chronohart @snarfed
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.