Closed juanpc2018 closed 2 years ago
rdmuser1
commented
2 years ago https://twiiit.com which is listed at the bottom of the instances page does something like that. Personally I've switched all my redirects and rss to it and it works well so far.
It might be nice to have a more official option that doesn't rely on a third party though.
zedeus
commented
2 years ago libredirect which you linked to is a solution, as is twiiit and similar projects. This is way outside the scope of Nitter itself, and there's no one-size-fits-all here with regards to latency, uptime, regional blocking, etc.
juanpc2018
commented
2 years ago libredirect which you linked to is a solution, as is twiiit and similar projects. This is way outside the scope of Nitter itself, and there's no one-size-fits-all here with regards to latency, uptime, regional blocking, etc.
Not android, big problem for android users. i dont know about iphone, but i guess is the same problem.
i think all frontends should have an independent Publicity / Banner revenue, pay with Crypto. or pay with Trade option dont want publicity? pay to remove publicity.
similar to Bittorrent publicity network, or Tor websites. web3.0 .crypto websites i dont know,
income will ensure websites have enough motivation to be on-line, increase bandwith, and maybe create more instanses.
automatic random instance / load balancing, will ensure equal income for all servers.
ABC G-company has 98% profit, only 2% goes to content creators, or independent websites when monetized, not all are approved to be monetized = 100% profit. some are monetized but shadow banned. Etc... On-line publicity market is controlled by G-company, F-company, and M-company. all owned by the same mayor stock holders.
what i mean is: decentralize puiblicity, randomize frontends. equal share.
because the content is Not illegal, hosted in legal servers, approved by The On-Line Ministry of Truth, (1984) that can attract many small bussiness that find G-company too complex or too expensive.
right now online publicity is too complex, people want easy, easy video tutorial,- easy to follow specs,. select dates, hours, regions, views limit... calendar with a mouse clic, have an estimate at checkout, upload button, pay with crypto, get a link & password to see statistics, clicks, views. feedback. if 2 people or more want the same day, hour, add the option to start a bid, like e-bay bid, bid ends 1 hour before. people can retract bids, bids must pay imediatelly, to avoid false bids. etc....
Random instance avoids G-Algorithm, and shows New Worlds, people can explore New experiences... New cultures. for example: female japanese piano player, will never appear on my algorithm, but i find that interesting.
G-algorithm is designed to avoid exploring New cultures, probably becase Air Travel companies, Hotels, booking agencies, are all owned by the same stock holders.
Algorithms are designed or fine tuned for Circular Economy, One company increasing the profits of the other. companies that seem unrelated, owned by the same.
like a sound feedback, that eliminates all other frequencies, 1 frequency eats all. same, all small / medium independent companies will be eliminated in the future. like Demolition Man (1993) movie, all restaurants in the future are by T- Bell. if you do Not comply, you have to eat river rat.
juanpc2018
commented
2 years ago similar happens with: greatfon.com you can see ig accounts you would never see before. in each reload F5.
gramhir.com is the opposite, if you know the name of the account exactly, opens the account, and by-pass similar accounts page selection.
its a time waster when nitter.net website requires to manually search another instance... its even more frustrating when alternate instances have very weird long names impossible to remember.
should be: nitter1.net nitter2.net or: 1.nitter.net 2.nitter.net etc...
or Automatic load balancing, i dont have to remember instance names, does Not matter if have weird long names. or... roll the dice to pick a random instance [button] or drop down menu list to pick a new instance. semi-automatic. redirects to the same link.
https://github.com/zedeus/nitter/wiki/Instances
having to memorize 5000 login, passwords, webites is more than enough.
similar problem as odysee / lbry instances: https://codeberg.org/librarian/librarian
https://libredirect.github.io/