fmstrat

joined 1 year ago
[–] fmstrat@lemmy.nowsci.com 1 points 9 minutes ago* (last edited 9 minutes ago)

That already exists in Street Complete: https://streetcomplete.app/

I was thinking more about machine learning against images of places to populate data automatically.

[–] fmstrat@lemmy.nowsci.com 2 points 1 hour ago

Donate it.

Using it just draws more power.

[–] fmstrat@lemmy.nowsci.com 5 points 1 hour ago

ZFS and dotfiles are your friend. Sorry for your loss.

[–] fmstrat@lemmy.nowsci.com 1 points 1 hour ago

Consider using a desktop.

Sure, small is cool, but you'll soon want to add drives for a RAIDZ. Then you'll want a faster CPU with more cores for more containers. Then how about a video card for AI or rendering. Honelabs grow, and you will want space for that growth. Plus, it's probably cheaper.

[–] fmstrat@lemmy.nowsci.com 4 points 1 hour ago

They be Redditing.

[–] fmstrat@lemmy.nowsci.com 2 points 1 hour ago (2 children)

I considered trying to make a mini version of this to auto-contribute to OSM. Street view image shows a compacted dirt road? Submit to OSM. Two lanes with lines? Submit to OSM.

[–] fmstrat@lemmy.nowsci.com 5 points 17 hours ago (1 children)

The lightweight claim is a bit of a stretch. You're counting content that gets cached in the browser.

[–] fmstrat@lemmy.nowsci.com 6 points 1 day ago

To make this simple:

Lemmy: One user follows a community from another server, content federates from all users commenting and posting. It takes one follow to start that flow.

Mastadon: One user follows another, content federates for that one user. It takes a lot of follows to get significant content movement.

In addotion, it is much more likely that out of 10 servers, the same communities are followed vs the same people.

[–] fmstrat@lemmy.nowsci.com 1 points 1 day ago

But, why won't everyone join Mastadon instead?!?

Thank goodness they go to BS.

[–] fmstrat@lemmy.nowsci.com 1 points 2 days ago

Yup, it does. I think I still have my server hard coded from when it first launched.

[–] fmstrat@lemmy.nowsci.com 1 points 2 days ago* (last edited 1 day ago) (1 children)

To me, an alternative model would be deep-linking/embedding 3rd party videos that you own.

For instance, sign up at @server, then:

  • Connect your YouTube account
  • Post Video 1 to YouTube
  • You now have a Video 1 in your federated feed with a YouTube embed
  • Connect your Vimeo account
  • Post Video 1 to Vimeo (same hash and/or title)
  • Your feed entry of Video 1 is updated to support both back end videos

This way your "feed" is federated, but the efficiency of centralized video content is used. If a provider goes down, or you choose to leave, you can re-up to another provider and with the connected account/title matching, your feed could be auto-updated.

[–] fmstrat@lemmy.nowsci.com 1 points 2 days ago

I'm not sure I agree with the other OP, I haven't used Kdenlive, but I thought it lacked OpenGL and Decklink support compared to Shotcut. Personally been very happy with Shotcut after using Premier and After Effects previously.

 

All the posts about Reddit blocking everyone except Google and Brave got me thinking: What if SearNGX was federated? I.E. when data is retrieved via a providers API, that data is then federated to all other instances.

It would spread the API load out amongst instances, removing the API bottlenecks that come from search providers.

It would allow for more anonymous search, since users could cycle between instances and get the same results.

Geographic bias would be a thing of the past.

Other than ActivityPub overhead and storage, which could be reduced by federating text-only content, I fail to see any downside.

Thoughts?

 

Almost 30 more minutes of dishwasher.

 

Hi all, I'm a Lemmy FOSS app contributor that's made a couple of tools for people starting small instances including Lemmy Community Seeder (LCS) for building content on new server's All Feeds and Lemmy Post Purger (LPP) for clearing old posts on smaller instances.

Today I'm releasing Lemmy Defederation Sync (LDS). When launching a new Lemmy instance, administrators may not understand the necessity of defederation with problem instances. Using LDS, you can sync your instance's "blocked instance" list with that of another server(s) whose admins you trust.

 

I've never had an issue once its set up. Just a 16GB LUKS partition alongside my normal LUKS partition, a small edit to /etc/crontab so I only have to enter the password once, set the RESUME variable, add to fstab, and rebuild init. This method even works with suspend-then-hibernate on every laptop I've used it with.

This would take 5 seconds at install time, but instead you have to install, reboot to the live USB, shrink LV, shrink PV, shrink LUKS, shrink partition, repartition, grow LUKS, grow PV, grow LV, and finally set up the swap partition as above.

Am I the only one? Does anyone else use encrypted drives and hibernate?

 

When launching a new Lemmy instance, your All feed will have very little populated. Also as a small instance, new communities that crop up may never make their way to you. LCS is a tool to seed communities, so your users have something in their All feed, right from the start. It tells your instance to pull the top communities and the communities with the top posts from your favorite instances.

How to run manually and in docker is included in the repo.

Let me know if there's anything anyone needs it to do and I'll see if I can fit it in. I'm going to work on a "purge old posts that are unsaved and not commented on by local users" first, since small instances are sure to run out of disk space.

view more: next ›