Hi, I keep reading about this thing called a "NAS" and I don't have in my social network a bunch of reasonable geeks to figure out if this is something for me or if it is overkill and I can get by with less -- trying to be frugal and all.

The Situation

At the moment, I have a Raspberry Pi 3 (that a colleague gifted me) which runs Jellyfin, mostly for music. I'd use it for watching series and movies, but given how slow it is at transferring files and the fact that it has a 1GB (maybe 2GB) RAM... I was afraid to break it. On top of that, its storage is a years-old external hard drive.

I use Jellyfin mostly to have music on my iPhone. I can access it when I'm out and about on Tailscale. I hope to find a solution for my photos as well.

I'd also occasionally use the pi to experiment with some self-hosted open-source apps.

I constantly find myself wanting to upgrade because I want to also backup my important photos (with face recognition if possible) and documents "offline" (i.e. in my local network) to something more stable than an aging hard drive. They're all in the cloud, but a second backup option could be great.

What I understand from reading about NAS's is that I basically have one, it's just not... reliable?

The Question

I understand there is definitely a buy-in cost for buying an actual NAS, I'd like to know how much... so that I can make an informed decision on if and when I would buy it. What is an entry-level NAS and how much will it cost? What could it NOT do that an RPi could, and vice-versa? Am I missing an in-between or even an alternative solution for my use case? Is it overkill and should I just upgrade the pi? What are my options?

Thanks in advance for reading my post!

Looking ahead, the commodification and degradation of the Internet is continuing to take away digital resources that we have come to depend upon over the last 20 years. Whether it’s email or Amazon or YouTube, the decline of all our favorites has been well documented.

But we don’t want to live without these sites and services. Tildes itself is an attempt to preserve one such resource but in a better and more stable way. What other parts of the Internet deserve similar treatment?

Whether it’s open source eBay or community banking or nonprofit versions of Facebook… what would you choose and how would you go about preserving its character and making it workable in the long-term?

I want to start reading more, and I'd also like to start avoiding screens before I sleep, so I'd like to get an e-ink device that I can use for reading.

I've never owned or looked into ereaders before so I'm not entirely sure what the general capabilities are in this space, but heres a list of things that I consider important:

• Absolutely essential:
  • I need to be able to put my own files (epubs, pdfs, etc) on the device to read without being forced to go through some marketplace installed on the device (if anything I'd prefer there to not be a marketplace on the device at all, or a removable one, as I would never use it). Files don't need to be added remotely, as long as I can connect it to my (Linux) computer with a USB and mount the storage or pop out the SD/microSD to do that then that's sufficient.
  • I need to actually own the device, none of the techno-feudalist bullshit like what plagues the smartphone landscape. I want to be able to remove non-essential components (e.g. marketplace) and it'd be nice if I could also tinker and install third party software freely. If possible I'd prefer a device that's mostly or completely open and FOSS by design, but I'm aware that might be asking too much. As an alternative I would also be willing to hack the device to get it in an open, FOSS state if the process isn't too complicated and it's well documented, it'd be preferable if it was that way by design but as long as I can get there one way or another I'll be content.
• Would very much like to have:
  • In addition to regular books, it'd be nice if I could also read manga. These tend to be zip/rar files containing a series of images, so I'd assume support for reading things formatted in that way is probably less widespread if it exists at all on dedicated ereader devices.
  • Some kind of lighting so the device is usable in the dark. I don't know how this would compare to the blue light from screens (if anyone knows, please share) but I'll certainly want to use it for more than just before I sleep.
  • Some kind of system to add notes as I read might be nice, I was never good at studying and note taking in school so I don't know how much mileage I'd get out of it but in theory it'd definitely be a boon to organize information as I read or add notes to myself to look into things later or whatever.
• Would be nice to have, can live without:
  • The ability to load music onto the device and plug in headphones to listen to music while I read. Bluetooth for audio devices isn't really something I care about, but might be desireable in case I get bluetooth headphones in the future (unlikely). Unimportant if it has built in speakers or not, as long as I can plug in headphones.

Hey! I’ve been trying lately to get rid of big platforms from my life. One part of it is that I usually buy ebooks/audiobooks from apple, Amazon or google, however I’m then also forced to use their reading app, which is a vendor lock-in I’m not comfortable with.

I know there are plenty of ebook readers out there, but I’m trying to find

1. A store where I can buy ebooks that can be opened in a ebook reader of my choice.
2. A way to then sync my progress between phone and laptop. I have nextcloud setup, so if I can make use of that then it’s perfect.

Anyone here got any tips?

I tried out Sync for Lemmy. Loved it, but I was not a fan of the tracking for ads and the price to get rid of that being $20. Anyone tried the free open source Lemmy apps? I used to use RedReader for Reddit, so I don't mind it being a bit worse than something like Sync.

Hi everyone! Today I am releasing Backtick API, an unofficial Tildes API. I originally wrote it to power Backtick but quickly realized that it could be useful for other clients and projects that require Tildes data. The project is open-sourced, both because I would love community contributions and because I want to make the project as transparent as possible.

Q: Does it require or store any user credentials?

No. All the endpoints that are implemented scrape publicly available data that do not require any user credentials.

Q: Will this overload Tildes?

To prevent Backtick API from being a nuisance to Tildes, the code caches calls to Tildes for a short period of time. Depending on usage, it should reduce the number of calls to Tildes (vs a client querying Tildes directly).

Q: How can I use it?

A hosted version of the code is available through RapidAPI here: https://rapidapi.com/asnewman/api/backtick-api

Q: Are there any limitations?

To prevent the project from being abused and becoming a financial burden on myself, I'm using RapidAPI to manage usage. There is a generous free tier and a reasonably priced paid tier which will be used to cover server costs. In addition, I will be donating a portion of the paid plan revenue (my goal is 50% but will depend on load and subscription count) directly to Tildes via Github Sponsors. It's really important to me to keep this project and Tildes as sustainable as possible. I really would love to provide everything for free, but unfortunately, there are countless examples where that doesn't work out down the road.

Of course, if you do not want to use the hosted version, you are welcome to deploy the code yourself!

Q: Isn't scraping prone to breaking?

Yes! Users beware! Obviously, I will try my best to fix things if the Tildes code changes in a way that breaks Backtick API, but it's definitely a possibility.

Q: Why not just work on and contribute to creating an official Tildes API?

An official Tildes API will always be better than something like this and I look forward to when/if it gets implemented. That being said, I'm choosing the route that would be the quickest to continue the development of the Backtick mobile app. In addition, it's also the choice that is most fun for me. To work on a Tildes API, if the powers that be even want to have one, would require lots of coordination and codebase learning, something that will take a lot of time. I highly commend anyone who chooses to take on that task, but I do too much of that kind of work for my real job 😂

Please report any issues or feature requests through Github, this post, or the Backtick Discord server. Finally, I just want to thank everyone in the community for all the great conversations I've had, for providing helpful feedback for Backtick, and for creating a place on the internet that I very much enjoy being a part of 😊

Hello!

Some of you may know that I have been developing an iOS client for Tildes.

I’ve seen other devs like @wababa and @talklittle also working on awesome apps, and have seen some discussion there around collaborating on some of the core parts (scraping the website, etc.).

I’ve also been in touch with @efraimbart, who is working on the awesome Everything protocol project.

I’m sure there are other devs out there that I haven’t seen, and this post is a call-out for all of you.

Until an API is available, any similar project will face the same initial blocker: needing to scrape the website for data.

Is there any interest from the community on collaborating on that part? For example, developing a public library that encapsulates all of the interactions with Tildes and any client can talk to with a consistent API. Or, even better, collaborating on an official API for Tildes (which is, of course, itself an open-source project).

To that end, I’ve released some of the code I use to accomplish this in Surfboard. Maybe it can help someone build an iOS client, or inspire some of us to build a more generic solution :D. It’s far from perfect or complete, and isn’t even an actual package you can just import and use at this time, but at the very least it documents many of the endpoints and interactions.

Have a great weekend :)