pexavc

joined 1 year ago
[โ€“] [email protected] 17 points 1 year ago (4 children)

My saves are getting monopolized by your memes ๐Ÿ˜‚

[โ€“] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

I've been attempting to build systems to make this "robustness" redundant across all my works, but I always feel there's something more that I missed. I can't tell if this task is simply never-ending or I just lack the knowledge of covering all the dots from the get-go or both.

[โ€“] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

how is that possible, clouds are even harder to dodge

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Other samples:

Android: https://github.com/nipunru/nsfw-detector-android

Flutter (BSD-3): https://github.com/ahsanalidev/flutter_nsfw

Keras MIT https://github.com/bhky/opennsfw2

I feel it's a good idea for those building native clients for Lemmy implement projects like these to run offline inferences on feed content for the time-being. To cover content that are not marked NSFW and should be.

What does everyone think, about enforcing further censorship, especially in open-source clients, on the client side as long as it pertains to this type of content?

Edit:

There's also this, but it takes a bit more effort to implement properly. And provides a hash that can be used for reporting needs. https://github.com/AsuharietYgvar/AppleNeuralHash2ONNX .

Python package MIT: https://pypi.org/project/opennsfw-standalone/

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

I'd like to share the TestFlight in this community with a possible listing on other resources for Lemmy federated clients that are being actively supported.

Testflight: https://testflight.apple.com/join/owwIagmV

Feel free to use the https://lemmy.world/c/loom community to post concerns, suggestions, bugs, and I will tend to them promptly!

macOS clients are always released via Github as notarized archives. Or, you could build it locally on your own.

Known Issues:

  • Scrolling stutter
  • Registration is not functional
  • macOS (intel) optimizations
    • I do not have an M-chip, so may be missing more macOS related bugs that need to be fixed

List of some major features are below:

cross-posted from: https://lemmy.world/post/3804045

v1.1.0b is in Review. Will be available by end of day.

1.0.4b was skipped. Since lots of changes were made in Granite, decided to mark v1.1.0 to denote.

Loom: https://github.com/neatia/Loom

LemmyKit: https://github.com/pexavc/LemmyKit

Granite: https://github.com/pexavc/Granite

Testflight: https://testflight.apple.com/join/owwIagmV

Looms
Image Create "Looms" of any group of communities from any instance. Merging their content into a singular feed.
Explore
Image Visit linked instances when connected to a lemmy server. View small snippets of each and their ping response time.
Travelling Modals
Image Writing modals can travel with your viewing context. Allowing you to browse content in any stack prior to publishing.
Bookmark Syncing
Image All your saved posts and comments can be switched between accounts in a dedicated component.
Sharing
Image Share posts or comments as images. With the intention of supporting QR codes and Engravings in the future.
Search
Image Either search all, a specific subcategory with sort support. View expanded contents within the view, interacting with content as normal.
Profile
Image Dynamic threads, despite viewing context. Swipe to reply to comments or tap the more button, to modify, remove, block, etc.
Image Deleting and restoring with toast reactions.
Image Switch accounts, view their profiles, and their scores.
Embedded Webview
Image Custom JS insertion supported, customizing how webpages are viewed via direct user input is a possibility.
Light Mode
Image Light mode and Dark mode supported. Refer to the color group in Assets to define preferences.
 

cross-posted from: https://lemmy.world/post/2566125

Repo: https://github.com/neatia/Loom

Beta testflight for iOS https://testflight.apple.com/join/owwIagmV

Base macOS build: https://github.com/neatia/Lemur/releases

I have yet to test this on M-Series Macs, as I still use Intel. Will still be able to provide fixes once I can source potential bugs (but most likely there shouldn't be any special to M~)

 

Over the years I feel brainwashed by the thoughts of others with no willpower to affirm my own beliefs.

Simply, to me blockchain/crypto is this idea of P2P communication where the intermediate technology that "handshakes" our connection isn't essentially governed by a centralized entity. But, "handshaking" in this world costs and gas is often times used as the processing/energy to enact this exchange.

Now, for what can be exchanged, it can be quantities of an item. Or information stored within an item. Kind of like Pass by value vs. Pass by reference, in a weird way? Or cryptocurrencies vs. smart contracts?

Now, my own belief is, comparing this system with torrenting, seeding and other technologies that existed long ago. What makes "blockchain/crypto" so valuable that cannot be solved with the technology invented prior to it. To me, it seems like there is extra charge and latency and thus just more negative values overall, when the final overall goal should be this idea of exchanging information. We still need ISPs, we still need physical wires to complete the "end-to-end" connection with a peer. So isn't everything still fundamentally centralized?

What is it actually improving? And is my way of thinking accurate? Why can't there be a normal P2P project handling exchange of information and/or modern fiat in the same way (Something like Paypal, but transactions have no middleman)?

 

I wanted to ask a technical questions, maybe high level, on why sites may have bad search and what the bottlenecks might be in almost never updating such in years. Was there something in the original development of the stack that is affecting progressive updates around the feature, how should one approach "Search" then in this case? Or is it simply a management issue.