I use the ChatGPT feature from desktop Firefox with no problems. Maybe it specifically denies Chrome, in which case I bet you could change the user agent string and get it to work.
DrNeurohax
joined 2 years ago
I use AliExpress for electrical parts (except anything with memory), 3D printer parts, and small crap I don't mind waiting for, but never anything I would be angry about if it never arrived. Also, nothing I consume or wear or need for safety, and I'm wary of anything that's supposed to be plugged into the wall for long periods of time unattended.
I wouldn't say I've been surprised, but my expectations are low. It's all cheap stuff, but as long as you're not needing the stuff you buy, it's fine. Dollar store quality with the scent of plastic and cigarettes.
That being said, beware of scams. The one that seems acceptable to them is to list one cheap part for the listing, along with variations of the full device. That way it looks like the lowest price in search results, but when you click it, the selected variation is the cheap part. Like, you'll search for "pliers set" and see a listing for $1, compared to others around $15. When you select it, the product page will have a carrying case for $1 and the various pliers for twice as much as the competition. What's better is that the case will be selected automatically, not the thing in the picture you clicked on or the picture you see first in the product pages' gallery.
There are also scam stores that pop up with super low prices compared to others on the site can disappear overnight and the cancellation/refund process is a super pain. Contact customer service once and just submit a claim with your CC company. Their refund process will try to keep telling you to wait for another week, and that includes the reps you get on chat. If you're suspicious and still order, always follow the shipping info. They will estimate a reasonable delivery date, you'll get a shipping notification, but it will sit in limbo. The shipping folks are separate from the scammers, so if you see the package actually move towards a shipping center, you're in the clear. If it says they received shipping information for over a week, you got screwed.
Ignore flash drives/SSDs, batteries, and assume any flashlights are 1/100th the brightness claimed (literally). Oh, and watch shipping costs. Something with free shipping can be 10x the price of the product if you add a second one to your cart.
coughcough tablets coughcough
Oh new Google tablet was just released? Um, you go first...
I totally agree on the first point, and might have a response in this thread stating much the same.
On the federation/syncing, I think it might need a more unique approach. Communities already have the problem of multiple posts linking the same article across several instances and communities, which don't sync comments. Making sure the complete wiki for a given community is resilient to instances defederating, shutting down, or vandalizing should be top priority, IMO. I don't know what the solution is, but I think we should be open to it looking different from the basic Lemmy sync setup.
For example, the wiki/extracted posts don't really need to sync as quickly as thread comments. Also, there should be some form of versioning in case of a credentials bug, hack, or intentional mass deletion or vandalism. We could aggregate points of conflict between instances/communities in a topic's main thread/stream/article and assign some for of weighting alongside the choice to continue reading from a particular wiki, which are return to the original thread/stream/article.
So, in the Biden-lizard example, the primary Biden entry that's synced everywhere could have a "Controversy" section with generally agreed on, real issues (like age, which is true for almost all US politicians) and fringe disagreements. Each fringe entry in the list would link to the page synced between instances that subscribe to those beliefs, but that page would not be a part of the larger synced Biden pages' contents. That keeps the lizard lovers' content off the larger, community-focused instances.
I guess I'm worried about conspiracy theories pulling users of the 'realistic' path, while increasing load on dissenting instances. I don't think Biden's a lizardman, so I shouldn't have to host the 12 hour long documentary on it. (We all know he's a reincarnated demon-angel hybrid. Oh, so now you don't agree? Fine, I'll host my 36 part finger puppet reenactment of the situation myself!)
Anyhow, I'm kinda babbling. These are just some general ideas off the cuff I wanted to get out there. I'm not a mod or an admin, so I'm hoping to get the conversation restarted among those with the ability to enact some of these changes. Reddit is still a knowledgebase of useful past discussions, and while new content is great, the more we can pull into the fediverse, the better.
Yup, but this is to prevent me from getting lazy and putting off creating the post until "later". (Where later = never) It also reduced things like tag typos and incomplete entries.
There are lots of details to be ironed out if we go the wiki way, which is why I think the tagged route would be the best start. Start getting the data and develop the larger structure over time. Once we need the data to populate the wikis/dbs/whatever, any mod can filter the posts pretty easily.
Other problems I see happening - conflicts between mods on entries, keep or throw out entries when an instance defederates (the c/politics folks might not want the entries on Biden being a lizardman from Nova Scotia, but c/iliketohitmyheadwithbricks does), bad blood if some mods want tighter control over wiki content, syncing when federating impact if larger media elements added, multiple wikis covering multiple topics while there are multiple instances covering multiple topics (multiplicative duplication due to the multiple hierarchies of equal importance), and I'm sure plenty more.
It would seem strange to users not keeping up with all the Lemmy/kbin meta to see a post that asks and then answers it's own question.
I'm more concerned about folks wanting to filter out these posts more than worried about confusion, though.
Yeah. Sounds like a good idea for a browser add on.
It places a button by the post's title.
Click that and it asks you to click the relevant replies.
It prompts for any additional tags (autotags RDX and subreddit name)
When you're done it fills in the title, body, tags of a new Lemmy thread and sends the archive request to whatever service they set.
I'm thinking more in terms of syncing and storage. It all depends on how it's implemented. Does each community have a wiki that's synced with individual users' wikis? A separate wiki per instance? How to handle edit conflicts, etc.
You're right that just making a wiki isn't too tough, but in the case of decentralized, editable, moderated content, it's probably different enough to warrant an approach significantly different from a traditional, single site/many edit centralized version.
(We could always temporarily have a centralized wiki and roadmap out the transition later, too.)
Yeah, I mean the ot.....
PLAY POLYBIUS. ALL MUST PLAY. CONQUER POLYBIUS. YOU ARE COMMANDED TO ENGAGE POLYBIUS.
... anyway, yeah, no idea.
I looked into this before with a similar deal by a 3rd party seller on Amazon. The enterprise drives (I was looking at those EXOS drives, too) must be sold by the manufacturer certified reseller or you run the chance of getting zero warranty. That being said, I've seen plenty of conflicting stories by people that bought them and needed to submit an RMA. I'd say it was a 60/40 split of honoring the warranty to not honoring it.
Long story short, it's a gamble. They're likely good drives, but you're rolling the dice if something goes wrong with them.
I just tried it again on desktop and it worked, but the reason was that I downloaded an extension a while ago and forgot about it. When I disabled the extension, it stopped working.
There used to be a way to enable installing any extension on mobile FFx Dev, but I'm not sure if that still works. The desktop extension just changes the user agent string, so that might be another route to enabling it.