71
-6
17

I'm interested in automatically generating lengthy, coherent stories of 10,000+ words from a single prompt using an open source local large language model (LLM) on low-spec hardware like a laptop without GPU and with i5-8250U, 16GB DDR4-2400MHz. I came across the "Awesome-Story-Generation" repository which lists relevant papers describing promising methods like "Re3: Generating Longer Stories With Recursive Reprompting and Revision", announced in this Twitter thread from October 2022 and "DOC: Improving Long Story Coherence With Detailed Outline Control", announced in this Twitter thread from December 2022. However, these papers used GPT-3, and I was hoping to find similar techniques implemented with open source tools that I could run locally. If anyone has experience or knows of resources that could help me achieve long, coherent story generation with an open source LLM on low-spec hardware, I would greatly appreciate any advice or guidance.

38

Hey fellow Fediverse users,

I'm on the hunt for a platform that allows for a more personalized content experience. I'm looking for a server that sends metadata for posts to the client, enabling users to customize how they view content using their own algorithms. I'm particularly interested in platforms that offer a more personalized and relevant content experience beyond the standard recency-based sorting that many Fediverse platforms currently offer.

My ideal platform would be one where posts are fully tagged, and I could assign a weight to each tag to see more or less of something. Having multiple feeds with different weights so I can see a different feed when I'm in the mood for other content would be amazing.

Does anyone know of a platform that offers this level of customization? I've been searching, but I haven't found anything that meets my requirements. I'd love to hear from you if you know of a platform that fits the bill.

Thanks in advance for your help, and I look forward to hearing from you in the comments below.

[-] ChasingEnigma@lemmy.world 14 points 2 weeks ago

Booru-style Image Boards like rule34

[-] ChasingEnigma@lemmy.world 24 points 2 weeks ago

ArchiveOfOurOwn

97
97
submitted 2 months ago* (last edited 2 months ago) by ChasingEnigma@lemmy.world to c/selfhosted@lemmy.world

Version 0.25.0 has been released.

The release brings scene play and o-counter histories, improvements to the grid and list views, better sorting of results in the select components, improvements to the package manager views, improvements to the toast notifications, a whole heap of other minor features and improvements, and many bug fixes. Check out the changelog for details.

As usual, thank you to everyone submitting PRs, reporting issues, helping out with support, managing the other repos and contributing financially.

Please also check out the Roadmap project (https://github.com/orgs/stashapp/projects/5/views/1) for a view of upcoming features and improvements.

Release Notes

v0.25.0 - 2024-03-06

💥 Note: A number of settings and tasks are now only available when Advanced Mode is set to true in the settings, including the Auto Tag and Identify tasks.

✨ New Features

  • Added Scene play and o-counter history tracking, view and editing. (#4532)
  • Added Advanced settings flag. (#4378)
  • Added support for setting galleries in Image edit panel and Bulk Edit Image dialog. (#4573/#4608)
  • Added option to generate image thumbnails during generate. (#4602)
  • Added Clean Generated Files task. (#4607)
  • Added more options to Performer gender filter. (#4419)
  • Added image orientation filtering. (#4404)
  • Added filtering and sorting of Studios on subsidiary Studio count. (#4479)
  • Added image performer age filter. (#4601)

🎨 Improvements

  • Overhauled the list view for scenes, galleries and performers. (#4368)
  • Made grid card fit cards properly within their containers. (#4514)
  • Improved the presentation of the toast notifications. (#4584)
  • Improved Tag, Studio, Gallery and Movie select controls. (#4478/#4493/#4535/#4563)
  • Improve sorting of results when entering text in select fields. (#4528)
  • Add disambiguation to performer link and performer select values. (#4541)
  • Show upgradable packages only when checking for updates in the package managers. (#4599)
  • Include primary tag name in Scene Marker search and sort. (#4606)
  • Improved presentation of scene queue. (#4448)
  • Improved zip file move detection. (#4374)
  • Saving images will now name them based on the original filename. (#4616)
  • Improved scene tagger matching prioritisation. (#4618)
  • Added support for disabling mobile media-viewer's fullscreen auto-rotate. (#4416)
  • Defer loading edit panel data until needed. (#4564)
  • Performer stash-box draft now includes the Disambiguation field. (#4122)

🐛 Bug fixes

  • Fixed invalid share causing error during cleaning. (#4570)
  • Fixed stash ids being removed when tagging Studio using the Studio Tagger. (#4572)
  • Fixed Plugin manager failing to get any updates if any installed sources are not found. (#4591)
  • Fixed .forcegallery file not being honoured when re-scanning after adding the file. (#4627)
  • Fixed Gallery Image filtering. (#4535)
  • Fixed Studio overlay not being shown on Image cards, and Studio text not being shown on Gallery cards. (#4540)
  • Wrap grid card popovers. (#4539)
  • Fix merge scene not deleting generated files. (#4567)
  • Fixed auto tag from object not honouring the ignore autotag flag. (#4610)
  • Fixed moved files causing re-generation of phashes. (#4598)
  • Fixed Movie scene sorting in Movie view. (#4588)
  • Fixed baseURL not being applied to some links. (#4501)
  • Fixed country selector in bulk performer edit dialog. (#4565)
  • Fixed image clips not upscaling in lightbox. (#4569)
  • Fixed bmp files being treated as video files in the lightbox. (#4653)
  • Fixed performer penis length being truncated to integer. (#4630)
  • Fixed heatmap generating repeated segments where there is no action. (#4557)
  • Fixed media decode error not switching to next streaming format. (#4506)
  • Fixed image scraping not using proxy. (#4637)
  • Fixed broken favicon after logging in using Firefox. (#4498)
  • Moved tag hover popover to the right. (#4593)
  • Fixed weird 404 behaviour in plugin assets handler. (#4597)

Plugin API changes

  • Added Mousetrap and MousetrapPause to PluginApi.libraries. (#4489)
  • Added useToast to PluginApi.hooks. (#4546)
  • Exposed Studio, Performer, Tag and Gallery selects, and date, country and folder inputs in PluginApi.components. (#4546)
  • Made task_name parameter optional, added an optional description parameter and deprecated args for a generic map parameter args_map in runPluginTask. (#4603)
  • Added runPluginOperation to run synchronous plugin operations with a return value, without using the task manager. (#4603)
  • Added PluginApi.Event.addEventListener and stash:location event dispatching.
  • Relaxed plugin cyclic loop detection to allow up to ten loops. (#4625)
[-] ChasingEnigma@lemmy.world 8 points 2 months ago

I don’t want this to become a rant thread, but the devs have frequently told contributors “No one is forcing you to develop for Lemmy”. That’s but one example.

@ptz@dubvee.org on https://dubvee.org/comment/1671815

[-] ChasingEnigma@lemmy.world 26 points 2 months ago* (last edited 2 months ago)

Here are some suggestions for how to encourage more outside contributions:

  • Create an ARCHITECTURE.md document explaining the overall architecture and different components of Lemmy. This would help new contributors quickly familiarize themselves with the codebase.
  • Publish a public roadmap with milestones and release plans. This gets people excited about the project's direction and motivates them to contribute.
  • Nightly builds enable contributors to test upcoming changes, offer feedback, stay actively involved in the project's progress, iterate quickly on improvements, and foster a culture of continuous improvement.
  • Implement a bounty system for critical or challenging issues to incentivize contributions. Some people who don't want to contribute with a monthly subscription may prefer this kind of contribution.
  • Create project swag (stickers, t-shirts, etc.) and distribute it to active contributors as a token of appreciation.
  • Institute a "Lemmy contributor mentorship or apprenticeship" program where experienced developers formally take up 1-2 promising new contributors under their wing. This would be modeled after the Sith/Jedi master-apprentice relationship where knowledge and skills are passed down. Later when the apprentice has managed to develop a few issues by themselves they can take some apprentices.
    The concept of more experienced contributors working with newcomers to develop features in a FOSS (Free and Open Source Software) project is commonly referred to as "mentorship" or "pair programming." In pair programming, two programmers work together at one workstation, with one writing code while the other reviews each line of code as it is typed in. The roles can switch frequently, and this method is known to enhance knowledge sharing, code quality, and team bonding. Beyond pair programming, establish a structured mentorship program where experienced contributors can mentor newcomers on a one-on-one basis.
  • Live or recorded screencasts solving issues, similar to mentorships but instead of one-on-one it allows more people to feel engaged in the development process, and provide feedback in the case of live streams.
  • Host discussions about issues on Lemmy itself, as suggested in the blog post below. The voting and threads with nested comments make it easier to have productive conversations compared to GitHub. The community is here so you'll get more contributions right away in the form of ideas and feedback.
    Update from Lemmy after the Reddit blackout
    spoiler

    At the moment we are urgently working to solve major issues, such as optimizing slow database queries, ripping out the inefficient websocket API, and fixing a major security vulnerability (big thanks to deadcade). In addition we suddenly have to manage dozens of pull requests. To give us time to work on these priorities, it would be very beneficial if users could refrain from interacting with issue trackers when possible. Before opening an issue, make sure that it hasn’t been reported before. And when writing comments, make sure that they actually contribute to solving the issue at hand. Generally it is better to move discussions to Lemmy if possible. We are very thankful to everyone who contributes by writing code, hosting instances, moderating communities, and answering questions.

    At the same time, we are seeing lots of requests to implement major new features, such as migration between instances, or combining similar communities. As described above, we are completely overloaded with work, and definitely won’t have time to implement these in the near future. If there is a feature you want to see implemented, you will likely need to work on it yourself, or find someone who can.

Of course you have more experience working on a big project so take this with a grain of salt.

[-] ChasingEnigma@lemmy.world 7 points 2 months ago* (last edited 2 months ago)

Yeah keyword, tag or regex blocking would be nice. Something like this:

[-] ChasingEnigma@lemmy.world 7 points 2 months ago

Why in the world did you enclose the readme in a code fence, though? It would be so much better to let the markdown do its job. My eyes are burning.

I wanted to use a quote to differentiate it a bit from the post but Lemmy-ui only quotes the first line.

[-] ChasingEnigma@lemmy.world 13 points 2 months ago* (last edited 2 months ago)

I agree, but the post is pretty much a copy/paste from the comment where I learned about the project, so blame @ptz@dubvee.org

[-] ChasingEnigma@lemmy.world 11 points 2 months ago

Controversial was added on 0.19 release. This is the pull request.

[-] ChasingEnigma@lemmy.world 12 points 2 months ago

Love the milestones it's what I think Lemmy is missing most that makes me excited about other projects.

134
submitted 2 months ago* (last edited 2 months ago) by ChasingEnigma@lemmy.world to c/til@lemmy.world

Today I learned about Sublinks (here), an open-source project that aims to be a drop-in replacement for the backend of Lemmy, a federated link aggregator and microblogging platform. Sublinks is designed to be initially API-compatible with Lemmy, allowing existing Lemmy clients, such as Lemmy-UI, to integrate seamlessly.

The project is written in Java, which may introduce some overhead but is chosen for its maintainability and familiarity among a wider pool of developers. The Sublinks team prioritizes a more inclusive and less toxic development environment, and the project has already attracted more developers than Lemmy.

While Sublinks is starting with 1:1 compatibility, future plans include implementing additional features that the Lemmy developers have not pursued. This could lead to a divergence in functionality between the two platforms as Sublinks evolves beyond its initial compatibility phase.


README

GitHub stars GitHub tag (latest SemVer) gradle workflow GitHub issues License

Sublinks

A decentralized, censorship-resistant, and privacy-preserving social network.

About

Sublinks, crafted using Java Spring Boot, stands as a state-of-the-art link aggregation and microblogging platform, reminiscent yet advanced compared to Lemmy & Kbin. It features a Lemmy compatible API, allowing for seamless integration and migration for existing Lemmy users. Unique to Sublinks are its enhanced moderation tools, tailored to provide a safe and manageable online community space. Embracing the fediverse, it supports the ActivityPub protocol, enabling interoperability with a wide range of social platforms. Sublinks is not just a platform; it's a community-centric ecosystem, prioritizing user experience, content authenticity, and networked social interaction.

Features

  • Open source, MIT License.
  • Self hostable, easy to deploy.
  • Clean, mobile-friendly interface.
    • Only a minimum of a username and password is required to sign up!
    • User avatar support.
    • Live-updating Comment threads.
    • Full vote scores (+/-) like old Reddit.
    • Themes, including light, dark, and solarized.
    • Emojis with autocomplete support. Start typing :
    • User tagging using @, Community tagging using !.
    • Integrated image uploading in both posts and comments.
    • A post can consist of a title and any combination of self text, a URL, or nothing else.
    • Notifications, on comment replies and when you're tagged.
      • Notifications can be sent via email.
      • Private messaging support.
    • i18n / internationalization support.
    • RSS / Atom feeds for All, Subscribed, Inbox, User, and Community.
  • Cross-posting support.
    • A similar post search when creating new posts. Great for question / answer communities.
  • Moderation abilities.
    • Public Moderation Logs.
    • Can sticky posts to the top of communities.
    • Both site admins, and community moderators, who can appoint other moderators.
    • Can lock, remove, and restore posts and comments.
    • Can ban and unban users from communities and the site.
    • Can transfer site and communities to others.
  • Can fully erase your data, replacing all posts and comments.
  • NSFW post / community support.
  • High performance.

Contact

Contributing

Support / Donate

Sublinks is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

[-] ChasingEnigma@lemmy.world 18 points 2 months ago* (last edited 2 months ago)

That already came in the latest 0.19 release.

This is the issue: Add option to open links in a new tab

[-] ChasingEnigma@lemmy.world 18 points 2 months ago* (last edited 2 months ago)

Right now I'm not particularly excited about any upcoming features.

I wish there was some feature in the works to let me see less memes and US politics without having to block or subscribe to a bunch of communities. I thought scaled sorting would solve this issue, I was really looking forward to it, but it didn't quite live up to my expectations. I thought it would be like the "top" sort but with more diversity, but it ended up feeling more like the "new" sort with most posts having just a single vote.

The last release had some great additions. I wish there was a roadmap for Lemmy so I could anticipate future releases and features like I do with other projects.

It would also be great to have nightly builds for testing new features before they're officially released on most instances.

103
view more: next ›

ChasingEnigma

joined 7 months ago