AAAAH sorry I misunderstood your point before. I thought users should not see files prior to their joining of that folder, but see files that come in after their joining.
But you mean, users should only see files they upload, while an admin or so sees all files.
https://github.com/drakkan/sftpgo
it can do what you ask, except I am not sure for the last one
can’t see / download files already present in the shared folder
that seems a bit complicated. Unless the solution stores user permissions per file.
try robfig/cron or gocron
they are much more simple and you can directly use the cron syntax.
There is a lot of legal troubles for manga piracy recently. Lots of manga and chapters got taken down. So this is probably the reason (but maybe not).
They claimed there will be no CSAM because of the given reasons.
I wanted to highlight that those reasons do not actually prevent it.
My tone might be harsh (the sarcasm at the end definitely is) because I see this as a marketing push for their crypto platform. "marketing" - as in they will be making money from users, so it is in their interest to tell lies or ignorant half-truths, to make more users come over.
Any normal platform tackles this problem with proper moderation. Platforms that make money, often hire moderators.
the protocol is text only, to embed media, you need to host it on the regular ( Centralized ) internet
except we already figured out how to encode images (or any file) as text when E-Mail was created. That is how images in E-Mails, attachment or embedded, are done. I can easily imagine a userJS script that will render them in the browser, but even if not you just copy the text and decode.
if a community is badly moderated, the user will never see it, it wont be recommended to him. the user can visit bad communities directly just like you can visit a bad website directly, but it’s not recommended to you so it’s safe to use.
Ah... so you're guaranteed to have a dark CSAM subculture on there at some point.
being p2p, seedit is not private, so it can’t really be used for illegal activity
As if that has ever stopped anybody. See all the people that got caught for sharing it on the clearnet. Or on Signal, Telegram or similar, where you have to enter your phone number, which is personally tied to you.
All in all - Great way to adress the concerns, by admitting they are in fact possible. "Hurray crypto" or whatever.
Sorry, I am just gonne dump you some links from my bookmarks that were related and interesting to read, cause I am traveling and have to get up in a minute, but I've been interested in this topic for a while. All of the links discuss at least some usecases. For some reason microsoft is really into tiny models and made big breakthroughs there.
https://reddit.com/r/LocalLLaMA/comments/1cdrw7p/what_are_the_potential_uses_of_small_less_than_3b/
https://github.com/microsoft/BitNet
https://www.microsoft.com/en-us/research/blog/phi-2-the-surprising-power-of-small-language-models/
https://news.microsoft.com/source/features/ai/the-phi-3-small-language-models-with-big-potential/
Not trying to argue with your preference, just trying to be informative:
The first model had shitty switches.
The newer model 100 is great and uses normal switches (you also can swap them).
They replaced/fixed any quality issues for both models, as far as I have followed in the forum/discord.
I also own both and I can not live without the palm keys haha so take my fanboyism with a grain of salt.
keyboardio has gread thumb clusters (and a palm key which you won't find anywhere else afaik. which is also super nice to use)
but it is H U G E compared to this, one more collumn on each half and one more row
I have no clue what I am looking at but it is absolutely mesmerizing.
I ran Linux with KDE on my phone for a while and it for sure needed EVEN MORE charging all the time even though most of the system is C, with a sprinkle of C++ and QT.
But that is probably due to other inefficiencies and lack of optimization (which is fine, make it work first, optimize later)
I just tested it on my instance. You can create a public share by setting the mode to "Write", which is accessible without logging in as a user (but with optional password).
It works, but one does not see any files, not even the ones you uploaded yourself. So for example if you updated the file and need to re-upload it, there is no way for you to delete the previous one.
You can also create a shared "virtual folder" that is seen by multiple users, and then you have fine grained control on a user basis (Users > burgermenu > edit > ACLs > Per directory permissions) there you can mix and match from a list of ~15 permissions. To upload anything to that virtual folder, you'll have to properly log in as a user.
Hope either one of the ways works for you. Cheers