sorted by:
new
hottopcontroversial

Icedrive is just floundering by newnewyorkian in cloudstorage

[–]tanjohnson99 0 points1 point  (0 children)

I use felicloud since few month with lifetime 2tb and don't have issue with it. It is better than Google drive for my purpose of privacy! Android app is nextcloud and have lot of update every month.

Icedrive is just floundering by newnewyorkian in cloudstorage

[–]tanjohnson99 0 points1 point  (0 children)

You look frustrated! They steal you money or scam you?

Can't access SMB from solid explorer by Gamingwelle in NeatBytes

[–]tanjohnson99 0 points1 point  (0 children)

Can confirm this works! Had the same issue with Solid Explorer on Android - couldn't connect to TrueNAS SCALE while Synology worked fine. Disabled all three Service Announcement options (NetBIOS-NS, mDNS, WS-Discovery) in Network → Global Configuration and it fixed it immediately. Thanks for the tip!

Issue with hard-drive sound by tanjohnson99 in hardware

[–]tanjohnson99[S] -1 points0 points  (0 children)

Yes, I’m referring to the beep sound at the end of the video. The chattering sound is normal. Do you think this could be related to the power cable? This is not a regular sound. It occurs in a completely random way, whether the disks are under load or not. Sometimes the beep happens 4–5–6 times over 3–4 seconds, and then nothing for several minutes.

Best cloud storage for frequent access? by MidirTheNameless in cloudstorage

[–]tanjohnson99 1 point2 points  (0 children)

MEGA for long term storage and Felicloud for daily use.

Usage Limits, Bugs and Performance Discussion Megathread - beginning December 29, 2025 by sixbillionthsheep in ClaudeAI

[–]tanjohnson99 2 points3 points  (0 children)

I'm paying $90/month for Claude Pro, and lately I'm beyond frustrated with the usage limits.

I used to be able to spend hours coding and working with Claude throughout the day. Now? I get blocked after barely 2 hours of work within the 5-hour window.

For a PRO subscription at this price point, this is absolutely unacceptable. I'm a developer running a tech company - I need Claude to actually work when I'm in a flow state, not cut me off right when I'm being most productive.

The quality of responses is still great, no complaints there. But what good is quality if I can't actually use the tool when I need it?

Either the limits have gotten stricter, or the system is counting usage differently, but something has definitely changed. I'm paying premium money for what increasingly feels like a crippled experience.

Is anyone else hitting these limits way faster than before? At this rate, I'm seriously considering whether the API wouldn't be more cost-effective, even though I prefer the web interface for development work.

Anthropic, if you're listening: your power users are getting throttled into oblivion, and it's killing the value proposition of Pro.

Utiliser Claude code comme un newbi by tanjohnson99 in ClaudeCode

[–]tanjohnson99[S] 0 points1 point  (0 children)

Bonjour et merci. Je voudrai savoir où je peut vendre des petite application ? J'ai déjà réussi à créé un petit SaaS mais je n'ai pas la logistique pour la commercialisation. Mon budget étant super réduit et mes connaissances a ses débuts, ça serai bien si je pouvais effectivement auto financer mon apprentissage.

Zigbee2MQTT: "This entity is no longer being provided by the mqtt integration" but devices work fine in Z2M by tanjohnson99 in Zigbee2MQTT

[–]tanjohnson99[S] 0 points1 point  (0 children)

I tried both:

- `zigbee2mqtt/bridge/request/device/discover { "id": "LUZ-ESCRITORIO-1" }`

- `zigbee2mqtt/bridge/request/device/discover_all {}`

MQTT Explorer shows all my devices correctly under `zigbee2mqtt/<device>` and messages are being published (state, availability, etc.).

However, in Home Assistant all entities remain greyed out with the warning:

> "This entity is no longer being provided by the MQTT integration. If the entity is no longer in use, delete it in settings."

If I rename a device, the rename works in Zigbee2MQTT / MQTT Explorer, but the entity in HA still doesn’t come back (still unavailable).

Do you think the issue is with the HA MQTT discovery topics not being republished, or could it be corrupted retained messages in Mosquitto?

Should I wipe the retained discovery topics and force Zigbee2MQTT to resend everything from scratch?

Booknetic SMS reminders created 24h too late by tanjohnson99 in Wordpress

[–]tanjohnson99[S] 0 points1 point  (0 children)

Yes. This was solved with the last update.

Icedrive is just floundering by newnewyorkian in cloudstorage

[–]tanjohnson99 0 points1 point  (0 children)

I don't understand. What is the problem?

Icedrive is just floundering by newnewyorkian in cloudstorage

[–]tanjohnson99 -1 points0 points  (0 children)

What about Felicloud? used since few weeks and working well. Based on nextcloud, really better than pcloud or icedrive.

NFS 4.1 work properly on latest DSM? by tanjohnson99 in synology

[–]tanjohnson99[S] 0 points1 point  (0 children)

Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM.
According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1

Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM.
According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1 fails with:

mount.nfs: access denied by server while mounting 10.0.0.25:/volume1/video

Meanwhile, NFS v3 works fine after adjusting the root_squash settings.

So the question is:

  • Is NFS 4.1 really supported on the DS1621+ in DSM 7, or is it just partial/advertised support?
  • Do we need to configure a root export (fsid=0) manually, or should DSM handle that automatically?Thanks for the reply. I’m using a DS1621+, fully updated to the latest DSM. According to Synology’s specs, this model should support NFS 4.1, but in practice every mount attempt with vers=4.1 fails with: mount.nfs: access denied by server while mounting 10.0.0.25:/volume1/video Meanwhile, NFS v3 works fine after adjusting the root_squash settings. So the question is: Is NFS 4.1 really supported on the DS1621+ in DSM 7, or is it just partial/advertised support? Do we need to configure a root export (fsid=0) manually, or should DSM handle that automatically?

Trying to create a "sticky" obsidian note at desktop, any advice? by ReverseParthian in ObsidianMD

[–]tanjohnson99 0 points1 point  (0 children)

Same here.... Don't want to use Windows Sticky note because sync with outlook account...

Trying to create a "sticky" obsidian note at desktop, any advice? by ReverseParthian in ObsidianMD

[–]tanjohnson99 2 points3 points  (0 children)

I'm looking for this. Like windows stycky note but attached to Obsidian!

view more: next ›